An assistant needs to carry the English setup into the Twi that follows because the Twi sentence often explains, limits, or corrects the instruction that came before it. Treating each language switch as a fresh request can produce an answer that sounds fluent yet misses the actual task.
At 6:40 p.m., Esi is standing outside a pharmacy in Kumasi with a folded prescription in one hand and her phone in the other. Her younger brother has sent a voice note: “I’m going to pick up the medicine for Auntie, but check the name on the receipt first. Sɛ ɛnyɛ ne din a, mma me nntua ka no.”
The English setup tells Esi this concerns a medicine receipt. The Twi changes the instruction: if the receipt does not carry Auntie’s name, do not let him pay.
That condition is the whole point. If an assistant hears only the final Twi sentence and replies with a broad translation about payment, Esi could miss the link between the name on the receipt and the money leaving her brother’s account. The pharmacy queue is moving. Her brother is already at the counter. If he pays for the wrong receipt, the proof Auntie needs may be gone by the time they sort it out.
The setup often carries the real subject
Code-switching is rarely random. A person may begin in English because they are naming a document, a workplace task, or a message they received. Then they switch to Twi for the part that carries urgency, emphasis, caution, or family context.
“Send the balance after you confirm the receipt, na hwɛ sɛ Auntie din no wɔ so” has one job. The English gives the action and object. The Twi adds the check that decides whether the action should happen.
An assistant that separates the languages may deliver two partial interpretations:
- Send the balance.
- Check whether Auntie’s name is there.
A useful answer joins them: confirm Auntie’s name appears on the receipt before sending the balance.
That is why the sentence before the switch matters. The clue can be a person, a deadline, an amount, or the reason the speaker is asking at all. Without it, the next sentence may sound complete while pointing to the wrong thing.
A language switch can carry the condition
In Esi’s voice note, the English phrase “check the name on the receipt first” establishes what is under review. The Twi phrase narrows the decision. It is not extra colour. It tells her what to do if the check fails.
That pattern appears in everyday conversation:
“Tell Kofi I saw the message, but sɛ ɔfrɛ bio a, ka kyerɛ no sɛ mewɔ meeting mu.”
The first part establishes Kofi and the message. The Twi gives the response for a future call. A reply that translates only the final phrase could lose who should receive the message, or why.
The same thing happens when someone starts with an English work term and shifts to Twi to explain the risk. “The manager changed the schedule, enti mesrɛ wo, mma wɔnnhyia anɔpa no” may need the whole turn to make sense. The schedule is the subject. The Twi carries the instruction shaped by that change.
For a closer look at how a key Twi detail can change the action, read What Happens When the Important Instruction Arrives in Twi?.
Context has to survive speech, interruption, and follow-up
A natural conversation does not arrive in neat, single-language blocks. Someone may hold to speak, pause to remember a detail, switch languages midway through the explanation, then interrupt the reply because they remembered the one condition that matters.
That is the kind of exchange Nkomo is built for: typed or spoken Twi and Ghanaian English, including the ordinary mixing people use with family, friends, and work contacts. The goal is to follow the conversation as one meaning, rather than force a speaker to choose one language for the whole turn.
There is a practical limit worth keeping in view. An assistant should show uncertainty when the audio is unclear or an instruction has more than one possible reading. A confident guess can be more dangerous than a visible error, especially when money, medicine, or a time-sensitive family request is involved. Nkomo shows errors instead of swallowing them, so a broken or unclear step is something you can see and address.
Esi needs that clarity in the moment. She asks for a plain restatement: “So he should pay only if Auntie’s name is on the receipt, right?” The answer should confirm the condition and keep the earlier English context attached to it.
Her brother sends a photo of the receipt before paying. Auntie’s name is there. The queue moves, the medicine is collected, and Esi can put her phone back in her bag knowing the instruction did not get split in two halfway through the voice note.
Listen for the thread, not only the language
When a Twi explanation follows an English setup, look for the thread connecting them. Ask what the earlier sentence introduced, then ask whether the switched sentence adds a condition, a correction, a reason, or the final action.
That small habit helps when you are checking a voice note yourself. It also gives you a better test for any assistant: can it explain the full instruction back in one clear sentence, including what must happen before the next step?
The answer should leave Esi with the rule she can act on: check the receipt name first, then send the balance only when it matches.
Comments
No comments yet.