What Did Auntie Need Me to Do in That Twi-English Voice Note?

The real request can begin halfway through a mixed Twi-English voice note, so replaying it is often a language-boundary problem rather than an attention problem. A conversation tool needs to follow the whole thought, including the switch into Twi where urgency, obligation, or the actual ask may sit.

The note starts with family news. Someone has arrived. Someone else has travelled. Then Auntie says, “Mepa wo kyɛw, sɛ wo nya time a…” and slips into English about a receipt, a payment, or a name that must match.

You catch the English pieces on the first listen. You hear “receipt” and “tomorrow.” On the second, you notice the Twi before them was doing the important work: please, when you have time, can you check this for me. The message was never unclear. Its meaning was spread across both languages.

The sentence that changes the task

Code-switching can move faster than a listener expects. A speaker may use English for the item, Twi for the relationship, then English again for the deadline. The shift can sound ordinary because it is ordinary. Yet it can hide the moment when a casual update becomes a request.

That matters when you are listening from Accra, London, Toronto, or anywhere else Auntie’s note arrives between work, school pickup, and a crowded train home. Replaying the audio costs little time. Missing the request can cost more: a delayed reply, the wrong name on a document, or a family member waiting for an answer they thought had already been given.

The useful question is not, “Which language was this message in?” The useful question is, “What did Auntie need me to do, and where did she say it?”

Nkomo is designed for the mix people actually speak. You can talk or type in Twi, Ghanaian English, or both in the same thought. Hold to speak, listen to the reply, and interrupt when you have remembered the detail that changes the answer.

Apollo 13 had the right parts, in the wrong shape

In April 1970, the Apollo 13 crew faced a rising carbon dioxide problem after the mission’s oxygen tank explosion. The lunar module had round receptacles for lithium hydroxide canisters. The command module had square canisters. The crew had supplies, but the parts could not connect as they were.

At Mission Control in Houston, NASA engineers worked out an adapter using materials available to the astronauts. The fix had to work with the objects already aboard the spacecraft. The crew used it, and Apollo 13 returned safely to Earth.

Jim Lovell and Jeffrey Kluger document the episode in Lost Moon, their account of the mission. The famous detail is the square canister and the round hole. The deeper lesson is about interpretation: having every necessary piece does not help until someone can make the pieces work together.

Mixed-language voice notes have a smaller version of that problem. You may recognise every English word and every Twi phrase, yet miss the instruction when the connection between them is unclear. A helpful conversation should hold the whole message together instead of making you separate it into neat language boxes.

Keep the sensitive parts in your hands

Family requests often carry details you would rather not scatter across apps: a balance, a receipt name, a phone number, a medical update, or a question about money sent home. Before using any AI with that material, it helps to know what leaves your device and what stays on it.

Nkomo makes that choice explicit. You can set cloud consent to never, ask each time, or this session. You control on-device history too. Turn it off and it is purged immediately. If you want a copy of your data, export it in one tap. If you want your account gone, delete it in one tap.

Those controls do not make a voice note less personal. They let you decide how to handle it before you ask for help understanding or replying to it. For more on the stakes of sensitive language and data, read What Happens to Your Sensitive Twi Message After It Leaves the Screen?.

Reply to the request, not the fragments

Before you answer Auntie, listen once for the story and once for the action. On the second pass, pull out three things: who needs something, what they need, and when they need it. If any part remains uncertain, reply with the narrow question that resolves it.

“Is the receipt meant to use your full name, Auntie?” is better than sending a confident answer to the wrong problem.

Apollo 13’s engineers did not need new equipment. They needed a workable connection between what was already there. The same discipline helps with a mixed Twi-English note: keep the context together, find the request, then respond to the part that needs you.