What Happens When a Call Disconnects During a Twi Greeting?

A completed call should mean the outcome your campaign defines, not merely that the telephony session ended. A 12-second disconnect during a Twi greeting needs its own lifecycle record, review path, and billing context before anyone treats it as a successful contact.

At 4:43 p.m., Nana sat at a desk in Kumasi with a paper cup of tea going cold beside her keyboard. She was reviewing a test run for a Twi-speaking campaign agent. One row caught her eye: “completed,” 12 seconds.

She opened the trace. The agent had started its greeting in Twi. The customer had disconnected halfway through the first sentence.

The campaign team had planned to use completed-call totals in their end-of-week report. If this record stayed in the success column, short disconnects could inflate the team’s view of contact quality and obscure a poor first impression. If paid calling were later enabled, the same loose definition could also make billable minutes harder to explain.

A call ending is only one event in the story

Telephony systems produce events quickly: an attempt begins, a provider connects, audio starts, a caller hangs up, a webhook arrives. “Completed” can be technically accurate as a final session status while being commercially misleading.

That distinction matters most in outbound work. A finished session does not show that a person heard the offer, answered a question, agreed to a follow-up, or even made it past the greeting.

Nana’s 12-second record needed more than one label. She needed to know:

• Did the call connect to a person or voicemail?
• Did the agent begin speaking?
• How much of the Twi greeting played before the disconnect?
• Was there consent recorded for the call?
• Was an opt-out phrase detected before the session ended?
• Should this call count toward reach, engagement, billing, or none of those?

A dashboard can answer the wrong question perfectly. “How many calls completed?” is easy to calculate. “How many people received enough of the greeting to make an informed response?” requires a definition that matches the campaign’s real goal.

Define success before the first call is placed

Nana paused the report and wrote three separate definitions for the campaign. A successful connection meant the call reached a live person. A successful introduction meant the greeting had played to its defined point. A successful campaign outcome meant the person completed the intended next step.

None of those definitions should silently borrow the word “completed” from the telephony provider.

For a Twi or mixed Twi-English voice agent, the introduction deserves close review. Recognition and synthesis quality affect what happens in the first seconds, when a recipient decides whether to stay on the line. Asenda Talk is built around native Twi speech recognition and synthesis fine-tuned in-house. Teams evaluating it should test the exact greeting, pronunciation, voice choice, and conversational handoff their callers will hear, rather than relying on a generic language claim. The same review applies when a customer switches languages mid-call, a scenario explored in What Happens When a Customer Switches From English to Twi Mid-Call?.

A useful campaign review separates operational states from outcome states. “Disconnected during greeting” can be a clear operational state. It should not automatically become a positive outcome.

Trace the record from consent to disconnect

Asenda Talk’s lifecycle webhook pipeline is designed to track call truth across the session. That gives an operator a record to inspect when a label looks too broad, including the events surrounding connection, runtime activity, and termination.

Consent, opt-out handling, and an audit trail should sit beside that lifecycle view. They are part of responsible calling, and they also change how a reviewer interprets a short call. A disconnect may be a technical drop. It may be a recipient refusing contact. It may follow an opt-out request that requires suppression across every route. Those are different events with different next actions.

Disputed Call Review: Why Consent and Lifecycle Records Matter examines why a bare call result cannot settle those questions.

At the point Nana reviewed the record, she had one safe action: remove it from the campaign’s success total until the team agreed on its classification. She did not need to rewrite history or guess why the recipient hung up. She needed the trace, the agreed rules, and a report that showed uncertainty honestly.

Keep billing and production decisions separate from a test result

A short call can still consume metered time. That is why call-truth records should connect to billing review without turning every technical completion into evidence of value delivered.

Asenda Talk has metered per-minute billing with an operator-controlled real-money gate. The platform remains in active early access. Production outbound calling is also gated behind an explicit telephony-provider decision that has not been made live. Teams can use this stage to define success states, inspect webhook records, test language behavior, and decide which outcomes deserve a chargeback or campaign credit before real-money calling is enabled.

The next morning, Nana’s revised report showed the 12-second session under “disconnected during greeting,” with no success credit attached. The completed status remained in the lifecycle history, where it belonged. The campaign result did not pretend the greeting had landed.