A french reply, spoken in english: dictating in a foreign language

The design studio's client is in Lyon, reads the account mail in French, and our account manager reads it too, but would never send one. Reading a second language and writing it are different skills; the reading came in after years of exposure, the writing asks for grammar production that exposure alone never installs. So the reply gets typed in the studio's own language, or worse, taken from a machine translation and sent without a second look. That is where the problem belongs: not in understanding, but in composing, and it is why dictating in a foreign language beats translating. The engine is doing the composing turn for you, and the composing turn is exactly the skill you never built; the more the client list leans French, the more that division of labor is worth.

Check the cost of the machine-translated reply. It is grammatically fine, and that is exactly the problem. Fine grammar built from a word-for-word transfer reads like translated text: correct, flat, and slightly deferred, the way a hotel lobby is nice and belongs to nobody. What the client hears is not your decision, it is the translator's decision about your tone. When the person on the other side is the client you talk to weekly, that small displacement is enough to change the temperature of the whole account. The irony is that fine grammar makes the displacement worse: a flat but flawless sentence has no tell, so the client feels a distance they cannot name, while a dictated sentence with one imperfect agreement reads as effort, and effort is warmth.

Dictation changes the trade. You do not need to write French; you need to say it. You will miss genders and agreements, the engine will hear an accented pronunciation and write French anyway, and you will correct it as you go. The part you actually own, the content, the sequencing, the warmth, is the part you save. The grammar is fixable in review, the tone is not, and that exchange is the whole argument for speaking the draft instead of generating it. One caveat: keep the correction pass honest, because the review is where most people give up; if a reply needs a full rewrite, it is a sign the French was beyond the day, and a shorter sentence in the same language beats a perfect one in the wrong register.

Draft the intent in your own language first, but draft it as a script, not a polished paragraph. Say out loud what you want the reader to take away in three locked sentences: the answer, the state of things, the next step. Translate in your head, or let a tool suggest, but keep it as intent. After several French-speaking clients, you will notice the intent draft is shorter than the final reply, which is correct; the English version is the map, the French version is the road, and the map does not need to name every curve. The three locked sentences also protect you from the classic trap of second-language writing, which is expanding a thought because the grammar feels available; the intent draft says what matters, and expansion happens only when it truly serves the client.

The discipline of intent-first matters because it separates the known from the unknown. You know what you mean; you do not know the third-person subjunctive. Ship the unknown to the transcription pass, where the engine will write it by ear, and keep the known in your own control. Practitioners who skip this step find themselves translating word-by-word, which is exactly the machine behavior they are trying to avoid, and the reply comes out sounding like a translated hotel again. Keep the intent note in the language you think in, because switching the note itself into French costs the clarity you need it for, and the whole point of the map is that it is plainer than the road.

Write the intent down in two or three plain English lines, then read them once and close the note. The reply should never be composed by staring at the English draft and converting; it should be composed from what the intent meant. If you want a warmer opening than the plan says, the warmth comes when you speak it, not when you translate it. The intent draft is there to stop you forgetting, and once you have spoken the first sentence, forget it. A warning for the first month: the intent note will tempt you to write the French translation beneath each line; resist it, because the note becomes a translation job the moment both languages sit there, and translation jobs end in translated sentences.

Now speak the French draft aloud, and do not stop for the hard parts. You will stumble on a gender, hesitate on a tense, and produce complete sentences anyway, which is what the transcription needs. Say it in short bursts, five to seven words, and let the engine transcribe while you are still thinking in the language. Then read the transcript and mark what is wrong, with a focus on two things: the picture of what the client will hear, and the word-level corrections. Warmth in the forced moment also needs the bursts: a five-word French burst in the client's own tempo is easier on the engine and easier on your accent, so the stumble and the transcription both land better.

Correction order matters. First fix the meaning errors: a word that changed the sense, a date, a name, a quantity. Then fix the grammar that a native will notice: agreement, the past tense of the verbs you mis-hear, the prepositions. Leave the minor foreignness alone; a slightly accented sentence reads warmer than a perfectly flat one, and French speakers will hear your effort rather than your gaps. One more pass, the listening pass: read it aloud again and notice if the rhythm matches the intent. The listening pass also catches the word you mis-say, when a common word is heard as a rarer one, which is how a friendly note becomes a formal one without you noticing, since the engine writes what it heard, not what you meant.

The playback pass is where tone is decided. If your dictation tool offers text-to-speech of the finished draft, use it as a radio check on the client's side: does this sentence sound like a manager, a partner, or a letter from an office program? If it sounds like the third, say the sentence again, simpler, with a common word instead of a precise one. Precision is what translation adds for free; warmth is what speaking adds for free, and you only keep what the ear can find. If there is no playback option, read the draft aloud once at the pace you would use on a call, and ask the single question: would I say this sentence to the client in person; a yes keeps it, a no rewrites it.

One client asked about a delay in a shared project. The tool's version read: "We regret to inform you that the proposed timeline must be subject to revision." Grammatical, formal, and completely unhelpful, because the sentence arrived like a press release. The dictated draft said, in effect, the plan has shifted by two weeks, and we want your view on the new dates before we confirm. The second says the manager is in the room; the first says somebody in an office made a decision. The split is the lesson: the machine version is a statement about the schedule, the spoken version is a person asking for an opinion, and the second is the one that gets a reply by Thursday.

The second case: a pricing follow-up. Translation produced: "Please find attached our cost estimate for your consideration." The spoken version opened with "here is the breakdown you asked about" and closed with a single date. Identical content, different temperature, and the client replied with the yes before the week was out. Neither version was wrong; one of them was a conversation the client had with a person. Worth noting the mechanics: both versions took the same five minutes to produce, so the difference was never effort; it was which voice the words were composed in, and the client answered the voice that sounded like a colleague instead of a department.

And the third case, the apology. Translation: "We apologize for the inconvenience caused." Spoken: "sorry for the late reply, the note was buried under the weekend." The client wrote back with a joke about buried notes, and the account, after three years, got its first friendly Thursday-morning message. The verdict of the comparison is not that translation is useless, it is that translation is a dictionary and the reply is a handshake, and the handshake is what makes the work continue. The three examples are not a rejection of the tool either; they are a division of labor, where the machine handles the words it knows well and the speaker handles the sentences the machine cannot feel.

Keep a phrase bank, and build it from the dialect of your own inbox rather than a textbook. Every time you send a French reply that works, copy its skeleton into a note: the opening, the two sentence patterns you used, the closing. After a month you will have maybe thirty lines, and those thirty lines are the phrases your clients actually hear from you, not the phrases a language app thinks French people use. Copy the phrases the moment the reply works, while the sentence is still warm in the mouth, because a bank built a week later is a bank built from memory, and memory edits the warmth out.

The phrase bank has a second use: rehearsal. Before a difficult call or a delicate reply, read the bank aloud in French to warm the mouth and the ear, especially the phrases for delay, for price, and for no. Speech is physical, and the muscle memory of saying the safe lines first makes the risky ones easier when the moment arrives. The bank is not a dictionary you look up, it is a track you run before the race. Rehearsal works because the risky words ride a track that is already running: the delay phrase is never said for the first time in front of the client who is waiting for it.

Use the bank to defend against over-formality. One habit worth banking is a medium-register opening, neither the machine's polite distance nor a slang tone you cannot hold. The exact sentence differs per client, so bank three: one formal, one neutral, one warm. Then the specialist rule: for each client you know best, the one whose voice you have heard, bank the phrase that matches their own way of closing, and you will write letters that feel like conversations across the desk. The bank also protects against a common failure: re-using a formal phrase in a warm account because it is the only wording you can produce under pressure, and the bank gives the warm register a ready sentence.