# AI Bilingual Client Onboarding: English, Hindi, Urdu

You can discuss a project in Hindi or Urdu while delivering in English, but onboarding should not leave two different agreements in circulation. Create one approved facts sheet and use it to draft matching welcome instructions, access requests and a kickoff agenda.

## Your brief

1. Prepare a canonical facts sheet: approved deliverables, contacts by role, required assets, milestone dates and decision owners. Use role labels instead of unnecessary personal details.

   ____________________

2. Specify the working language and the delivery language. Keep brand names and software identifiers unchanged unless an approved local form exists.

   ____________________

3. Define how the client approves translations, resolves a difference between versions and shares access securely. This communication pack does not replace an executed agreement.

   ____________________

## Prompt

From this approved facts sheet [facts], draft a bilingual onboarding pack in English and [Hindi/Urdu]. Include a welcome note, asset checklist, secure access request and kickoff agenda. Keep dates, scope and responsibilities identical. Preserve brand names. Add a mismatch table for phrases needing human approval. Do not request passwords by email or turn this pack into a new contract.

## Illustrative example

Illustrative facts: the client supplies approved product photos by 5 November, and review happens at 15:00 Asia/Karachi. Both versions retain that exact date and time zone. If the source says ‘next Friday,’ the draft asks for a calendar date instead of guessing. The access note requests an authorized invitation, not a shared password.

## Acceptance checks

- [ ] Do all language versions preserve names, numbers, dates, time zones and the same responsibility owner?
- [ ] Has a person reviewed ambiguous terms and right-to-left layout in the final Urdu file?
- [ ] Are access requests secure and is the onboarding pack clearly separate from contractual changes?

Avoid using a more confident translation as a substitute for clarity. If one version says ‘draft due’ and the other says ‘final delivery,’ the mismatch must be resolved before either version is sent.

---

Brainbaby · https://brainbaby.ai/blog/ai-bilingual-client-onboarding

CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/