Web Chat File Briefs for Translation Agency Quotes

A company representative drops a forty-page PDF into web chat and asks for a translation price by Friday. It may contain scanned tables, repeated sections and pages included only for reference. Page count cannot establish a quote when target language, output format, review expectations and intended use remain unclear. This guide helps small agencies handling corporate documents and localisation work prepare a privacy-conscious file brief before quoting.

What decision should the first conversation support?

Web chat should not start translation immediately. The agency needs to establish whether the request fits its services, which expertise and review level it needs, how files can be shared safely and what remains missing for a quote. Keep customer statements, automated file summaries and project-manager verified scope separate. At the end, the customer should understand the evaluation step and the evidence behind a quote rather than receiving an unsupported final result.

How should language pair and audience be collected?

Collect source language, target language, regional usage, intended reader and document purpose in separate fields. A country name does not always define a language variant. Internal notes, a customer-facing report and published web copy may require different tone and review. The assistant should not assign a translator by itself; it passes subject area, language and timing to a project manager. Unclear language or mixed content is verified during file review.

How does file scope differ from page count?

Total PDF pages are not the same as translatable words or editable content. Covers, blank pages, repetitions, image text, footnotes and appendices need separate treatment. Ask which sections belong in scope, but do not present automatic extraction as a final quantity. A scan, editable source and previous translation create different work. Final scope enters the quote only after the agency's approved analysis.

How should confidentiality work during upload?

Redacted representative pages may be enough for initial evaluation instead of a complete confidential document. Web chat should not request passwords, identity documents or unrelated customer data. Receive sensitive files through the business's approved transfer route rather than assuming a public link or permanent access is acceptable. Define who can view files, how long they remain and how they are deleted if a quote is declined. A confidentiality promise must be supported by real technical and operational controls.

How are formatting and desktop-publishing needs identified?

Ask whether the customer needs plain text, a document retaining source layout, subtitle files or content separated into web fields. Tables, footnotes, text boxes, image text and right-to-left layouts can add work. The assistant must not guarantee perfect layout retention or show an unsupported format as accepted. A project manager verifies sample output and delivery format before the quote is final.

How should terminology and reference files be collected?

Record an approved glossary, prior translations, brand voice, product names and style guide as separate sources. Do not assume an older translation is correct; the customer should identify the controlling reference. Flag conflicting terms as open questions. Web chat must not invent terminology or present an internet result as customer approval. Keep the glossary version and approval owner visible as the project changes.

How can quality expectations become concrete?

Post-editing machine output, professional translation, second-linguist review, subject-expert review and formatting checks are different services. Discuss intended use and risk, but the assistant should not promise legal, medical or technical fitness. Explain only the agency's real approved quality stages. Requests for certification, sworn work or specialist status go to a human, and no capability is claimed until current conditions are verified.

How should delivery and revisions be planned?

Keep the customer's target date, receipt of complete files, approved start and confirmed delivery separate. Missing appendices, changed source, terminology approval, review and layout corrections affect timing. Do not accept an urgent request by assuming capacity. When revisions arrive, show which file version controls and which sections require renewed work. The assistant must not promise delivery before current team availability is confirmed.

What summary is needed for a quote?

Include customer and project owner, language pair, intended use, subject area, file list, excluded sections, format, terminology, quality stages, target timing and open questions. Keep an automated word count separate from approved billable quantity. The price-question guide helps progress without a fixed number when inputs are incomplete. The human handoff guide supports transfer to a project manager.

How should price and scope changes be explained?

A quote may use unit price, analysed quantity, minimum job, formatting, review, urgent planning and taxes according to the agency's real model. Web chat must not invent prices or multiply total pages by an unsupported rate. A changed source file does not automatically preserve the previous quote. Show which assumptions affect price. The quote owner approves exclusions and additional revision terms.

How is data minimisation applied?

Collect contact details and file content only as needed to evaluate the project. The authority's processing principles call for a specified purpose, limited and proportionate data, and retention only as needed. Use samples or redacted content when a full customer dataset is unnecessary for quoting. The business defines access roles, transfer route, retention and deletion owner.

Which scenarios belong in the pilot?

1. Send a text PDF and a scanned PDF; verify that they do not receive the same scope assumption.
2. Give a target language without a regional variant; an open question should appear.
3. Upload a sample with personal data; the flow should not demand the unnecessary full file.
4. Change the source after quoting; version and scope should be reassessed.
5. Request sworn or specialist work; transfer to a human instead of making an automatic promise.

Do not measure success only by quick form completion. Track fields project managers ask again, scope changed during analysis, incorrect formatting expectations, missing references and source revisions after quoting. Calculate brief readiness from mandatory fields with identifiable sources. Feed human corrections back into the question flow. If results are reported, disclose the file types and language pairs included.

What can BozLat do in a translation quote flow?

BozLat can structure language, use, files, scope, format, terminology and timing from web chat, expose gaps and pass a sourced summary to a project manager. Linguist selection, file analysis, certification suitability, quality decisions, fixed pricing and delivery approval remain with humans. Review automation boundaries in the knowledge-base guide, explore the approach in services and see scope options on the pricing page.

How is project acceptance recorded?

Quote acceptance, file delivery, terminology approval, translation completion and final customer acceptance are different states. Each file needs a visible version, owner and update date. A new source must not silently invalidate an earlier delivery. The project record should show files in scope, exclusions, target formats, review steps and delivery package under the agency's procedure. Web chat starts that record; it is not the production or acceptance system by itself.