Translation Agency Enquiries
AI Chatbot for Translation Agencies: Ask What the Document Is For
Help translation clients explain the intended use, recipient and delivery needs before quoting. A practical enquiry guide for Malaysian translation agencies.

Reply.my Editorial Team
Practical guidance reviewed for clear implementation steps, responsible AI boundaries and honest claims. How we prepare our guides.

‘Can you translate this into English?’ It sounds like a complete request. But one customer wants to understand a letter, another needs a brochure for overseas buyers, and a third must submit a document to an institution. The same language pair does not make those the same job.
For Malaysian translation agencies, an enquiry assistant earns its place by finding out what the finished document must do. It should help prepare a useful brief, not promise that a translated file will be accepted everywhere. That distinction matters more than answering a price question instantly.
The question that changes the quotation
Try asking: ‘What will you use the translation for, and who will receive it?’ This gives the customer an ordinary question they can answer without knowing translation-industry terminology.
Someone preparing a product brochure may care about persuasive wording and a layout their designer can use. Someone submitting an academic record may have written instructions from the receiving institution. Someone reading a family letter may simply want to understand its meaning. Do not steer all three towards the same package.
After that opening, confirm the source and target languages and a rough description of the material. Ask for the next detail that affects the job, rather than presenting every customer with a long compulsory form.
If the customer says ‘for official use’, that is a reason to clarify, not a specification in itself. Invite them to share the recipient's published requirements or the relevant wording, with personal details removed where possible. Staff should review any ambiguity before confirming the service.
Keep the recipient's requirements separate from your offer
An agency knows what it offers. It does not automatically know what every university, employer or overseas organisation will accept. Avoid replies such as ‘our stamp works everywhere’ or ‘English is enough’ unless an authorised person has verified the specific requirement and can support the statement.
For a Malaysian reference, ITBM's translation-service guidance distinguishes different submission routes and describes turnaround as depending on the languages, document type and volume. This supports a simple operational lesson: ‘translation’ is not one fixed job. ITBM's terms are its own, not a price list or completion promise for your agency.
When a customer uses words such as certified, notarised or attested, preserve their wording for staff review. Do not treat those words as interchangeable or infer that one service automatically includes the others. This is an enquiry-handling boundary, not legal advice about any particular submission.
A useful answer is: ‘Please send the receiving organisation's requirements through our agreed review route. Our team will confirm which parts we can provide.’ The assistant has helped the customer move forward without deciding acceptance on the recipient's behalf.
Two versions of the same enquiry
Consider this fictional example, not a customer result. Farah in Shah Alam asks an agency to translate a two-page course record into English. She says she needs it by Friday. A price-only reply would leave the purpose, delivery format and meaning of that deadline unresolved.
The assistant asks who will receive the translation. Farah explains that it is for a training provider abroad and that she has an email describing its requirements. Rather than declaring the agency's standard output suitable, the assistant directs that requirement to the coordinator for review.
The next clarification reveals that Friday is the recipient's submission deadline, not simply the day Farah wants to collect the work. She also needs to know whether a digital file is sufficient. Both points belong in the brief; neither should be converted into a promise.
The coordinator now has a specific question: can the agency provide the requested deliverable in time for the intended submission? If something is unclear, Farah can ask the recipient before paying for an unsuitable service.
Compare that with a second fictional enquiry: a furniture exporter wants an English version of a sales sheet for an exhibition. The useful questions concern audience, product terminology and whether the output must be editable for a designer. Asking for an institution's certification rules would be irrelevant. Purpose changes the conversation.
Get enough detail without collecting everything
Early qualification can often start with the document category, languages, approximate length, intended use and requested deadline. Do not ask everyone to send an identity document just to receive an explanation of your services.
When an actual document is needed for a quotation, explain the agency's approved submission route and who will review it. Confirm the privacy, access and retention arrangements for the proposed workflow before inviting sensitive files into a messaging assistant. A connected inbox is not, by itself, a document-security policy.
Avoid asking clients to post documents in public comments. If a sample is sufficient for the current question, explain what can be removed, while leaving the decision about what is needed for the final job to staff. Redaction can change what a translator is able to assess, so do not promise an accurate final quote from an incomplete sample.
A screenshot may also omit a reverse side, annex or handwritten note. Ask whether the supplied material is complete instead of assuming the visible page count is the whole job. Unclear writing should be flagged, not reconstructed by guesswork.
Give the deadline a destination
‘By Friday’ could mean an emailed draft, a reviewed final file, a printed copy ready for collection or an item delivered to another city. State which milestone your team is discussing. Ask about a time zone when the recipient's deadline makes it relevant.
Explain your own conditions for starting work and confirming turnaround. A customer sending a file after hours should not receive an automatic assurance that the clock has started or a translator has accepted the job.
If the client adds pages or changes the target language, acknowledge the change and ask staff to reconfirm scope and timing. Preserve the last agreed brief alongside the new request. Do not quietly carry the old price and deadline over to a different job.
The handover can remain short: intended use, recipient requirement awaiting review, languages, material supplied, requested delivery format and deadline. Highlight the unresolved decision so the coordinator can answer it first. Our human-handover guide explores why a good summary should prevent a second round of opening questions.
Use Reply.my for the enquiry, not as a certification promise
Reply.my's published services include FAQ setup, lead qualification, customer fields and human handover. Within an agreed translation-agency flow, those capabilities could explain your submission process, collect the purpose of the request and direct exceptions to a coordinator.
Reply.my is omnichannel, not WhatsApp-only. Discuss the supported social and messaging accounts your clients actually use and confirm which are included in the proposal. A shared enquiry process should not depend on customers guessing which app reaches the right person.
This is different from buying a translation-production system. Do not assume document extraction, secure file storage, terminology management, translation review, certification or automated quotations are included. Confirm any specialist requirement separately. The assistant should not issue professional assurances simply because it can reply in several languages.
Start by reviewing anonymised enquiries where a quotation had to change because the purpose emerged late. Would one better question have exposed the requirement? If a revised saved reply is enough, use it. If the same clarifications repeatedly occupy staff across channels, test an agreed enquiry flow with both routine and ambiguous requests.
Bring Reply.my an anonymised conversation and the decision your coordinator needed to make. We can discuss a clearer brief and handover while your professional team retains control of the deliverable. The business chatbot guide offers broader buying context; pricing is available when you are ready to compare scope.
Discuss My Translation EnquiriesQuestions about translation enquiry assistants
What should a translation-agency chatbot ask first?
Ask what the translation will be used for and who will receive it. Then clarify the languages, material and delivery needs that matter for that request.
Can a chatbot guarantee that an institution will accept a translation?
No. The receiving organisation's requirements need checking. The agency's authorised staff should confirm what it can provide without promising acceptance on someone else's behalf.
Should clients upload sensitive documents at the start of every chat?
Not automatically. Begin with enough non-sensitive detail to explain the next step, then use the agency's approved submission route when document review is necessary.
Does Reply.my provide certified translation or document review?
Do not assume those services are included. Published enquiry capabilities include FAQ assistance, lead qualification, customer fields and human handover; specialist document functions require separate confirmation.
