A switch from English to Twi after “but” often marks the point where the speaker moves from an update to the concern they truly need heard. Listen to the whole turn, including the language change, before replying or making a decision.
At 9:14 on a Sunday evening, Esi stood in her Croydon kitchen with a spoon hovering over a pot of rice. Her phone played her auntie’s voice note for the second time.
“Auntie is resting now. The nurse said they have checked her,” the message began in English. Then came a pause, small enough to miss. “But, Esi, me suro sɛ yɛnntumi nni asɛm yi ho dwuma ntɛm.”
The words after “but” were in Twi. The update had been manageable. The fear had arrived in the language that carried it best: she was worried the family might fail to act quickly enough.
Esi’s cousin had already suggested sending money immediately. Her brother was waiting for an answer before bed. If Esi treated the first English sentence as the whole message, they could send the wrong amount to the wrong person, or make a rushed promise while Auntie’s situation was still unclear.
She held the phone closer. The rice started catching at the bottom of the pot.
“But” can change what the message is asking for
Code-switching is often practical. English may carry a job title, a medical term, a travel detail, or a name from a form. Twi may carry worry, caution, affection, frustration, or the part that feels too important to flatten.
That does not mean every English-to-Twi switch has one fixed meaning. Context matters. So does tone. A voice note that begins, “Everything is fine, but…” asks for more attention than the first phrase earned.
In Esi’s note, the English gave her information: Auntie had been checked. The Twi clause changed the task. Her auntie was asking the family to slow down, clarify what was needed, and avoid guessing.
The useful question is often simple: what changed after “but”? Did the speaker move from reporting to warning? From facts to feeling? From what happened to what must happen next?
That is why replaying only the English details can leave the real message behind.
Let the reply follow the speaker’s mix
Esi opened Nkomo and spoke her question the way it came to her: “She said Auntie has been checked, but ‘me suro sɛ yɛnntumi nni asɛm yi ho dwuma ntɛm.’ What should I ask before we send anything?”
She did not have to separate her concern into a clean English version first. She could keep the English details and the Twi worry in the same conversation.
That matters when a family voice note needs a reply quickly. A stiff, fully English answer can sound distant. A fully Twi reply can leave out the exact detail everyone needs to confirm. The most useful response may mix both:
“Okay, I hear you. Before we send money, please tell us exactly what Auntie needs tonight and who we should speak to.”
The point is clarity, not performance. You are trying to make the next step harder to misunderstand.
For another look at how meaning can shift inside one mixed-language turn, read What Happens When English Leads Into a Twi Clause?.
Sensitive family questions deserve control
A voice note about health, money, immigration, or a difficult relationship can carry more than language. It can carry details you do not want sitting in a chat history without your say.
Nkomo lets you choose whether cloud use is never allowed, asked about each time, or allowed for the current session. Its history stays on your device under your control. Turn history off, and it is purged immediately. You can also export your data or delete your account in one tap.
Those controls do not make a hard family decision easy. They give you a clearer boundary while you work through it.
Esi listened once more, then sent one short voice note back. “Auntie, yɛte ase. Please tell us what is needed now before anyone sends anything.”
The rice was still salvageable. More importantly, the family had stopped guessing.
Comments
No comments yet.