The Extension Officer a Farmer’s Voice Note Needs, Before It Enters an Unowned Queue

Every unclear farmer question needs a named human owner who can respond by the next working day. A voice advisory pilot is only safe when that person, their handoff process, and their response time are agreed before farmers begin sending notes.

In April 1970, Apollo 13 had a rising carbon dioxide problem after an explosion damaged the spacecraft on its way to the Moon. The crew had lithium hydroxide canisters, but the command module cartridges and lunar module fittings did not match. Engineers at Mission Control in Houston had to work with the materials available to the astronauts and send back instructions for a makeshift adapter.

The account in Jim Lovell and Jeffrey Kluger’s Lost Moon, later adapted as Apollo 13, makes the important point clear: the crew could not solve every problem alone from inside the spacecraft. People on the ground had to take responsibility for the unanswered parts, work through them, and get a usable answer back.

A voice note can be an escalation, not a failure

A farmer may ask about cocoa leaf spots, an unfamiliar product name, spraying after rain, or symptoms that do not match any reviewed advice. AgriVoice should not fill that gap with a confident-sounding guess. It should say that the question needs human review, capture the details needed to investigate it, and route it to the extension officer the partner has named.

That response protects the farmer and preserves trust. Silence feels like abandonment. A polished answer that turns out to be wrong can cause more harm. A clear handoff tells the farmer what happened and what comes next.

This matters most for chemical questions. Three AgriVoice content blocks remain held because dosage, re-entry intervals, and pre-harvest intervals have not been verified. Keeping them unavailable is a safety decision. The responsible next move is to route the question to an accountable person, as explored in What Happens When a Cocoa Pesticide Question Has No Reviewed Answer?.

Start the partner conversation with one name

Before recruiting farmers, ask the cocoa-sector partner one practical question: who owns an unclear question once the system has escalated it?

A useful answer includes a real person or a clearly named role, plus a backup. “Our extension team” leaves too much open. A farmer’s note needs somewhere specific to go when the primary officer is in the field, away from signal, or unavailable.

The partner should also agree on the next working day as the target for an initial response. That first response does not always need to contain a full agronomy recommendation. It can confirm that the case is being reviewed, ask for a photo or location detail, or set a realistic expectation for follow-up. What matters is that the farmer does not disappear into an unowned queue.

Keep the escalation record small enough to use:

• The farmer’s question and preferred contact number.
• The date and time the question arrived.
• The reason it was escalated.
• The named owner and backup owner.
• The response sent and when it was sent.
• Whether the case exposed a missing reviewed content block.

This record is also how a pilot partner learns what to fix. If ten questions about the same leaf symptom reach the officer, the team may need a reviewed answer block. If several farmers use words the system cannot recognize, the speech evaluation set needs those examples. If escalation cases wait too long, the issue may be staffing or routing rather than language technology.

Make the handoff safe before making it fast

A two-week pilot with 20 to 50 farmers should measure successful answers and correct escalations together. The goal is not to make every message automatic. The goal is to help farmers receive useful, safe guidance through a route they can understand.

For AgriVoice, the escalation path needs a cocoa-sector partner that owns recruitment and identifies the extension officer who receives cases. The partner should test the full loop before farmer exposure: send a deliberately unclear question, confirm the system flags it, verify the officer receives it, and check that a response can return through the same channel.

Test the difficult cases first. Use a pesticide question with a missing detail. Use a code-switched Twi and English voice note. Use a question outside the approved content. Use a message where the audio is too unclear to trust. Each should produce a safe response and a traceable owner, rather than a made-up answer.

The response time also needs a practical definition. “By the next working day” should mean the first human acknowledgement or useful response, not an internal assignment nobody can see. The pilot scorecard can then track median escalation response time alongside comprehension, repeat use, latency, and safety.

The partner checklist that prevents an abandoned queue

Bring this checklist to the first operational meeting:

• Name the primary extension officer for escalations and one backup.
• Agree how each person receives new cases and confirms receipt.
• Set the next-working-day response target.
• Decide what information the system should capture before handoff.
• Define which questions require an immediate hold rather than automated advice.
• Rehearse one escalation from a farmer voice note to a human reply.
• Review unresolved cases at least once during the pilot.

Apollo 13 did not depend on every person having every answer. It depended on the right people taking responsibility for the questions the crew could not resolve alone. A cocoa voice service needs the same discipline: when the answer is unclear, the farmer should know who has it next.