A dosage question should receive a human escalation until a Ghanaian agronomist has cleared the exact product, amount, re-entry interval, and pre-harvest interval. A fluent Twi reply that guesses any of those details can put a cocoa farmer at risk.
In 1960, Frances Oldham Kelsey was reviewing an application at the U.S. Food and Drug Administration in Washington, D.C. for thalidomide. The manufacturer wanted the drug approved in the United States. Kelsey kept asking for more safety evidence, including clarification around reports of nerve damage. The approval did not move forward while the evidence remained incomplete.
That decision mattered profoundly. Thalidomide was later linked to severe birth defects in other countries. Kelsey did not have a safer substitute waiting in her desk drawer. She had an unresolved safety question, and she treated that question as a reason to pause.
A cocoa farmer holding a measuring cup before spraying faces a smaller scene with the same safety logic. The product name may sound familiar. The request may be urgent. The voice note may be clear: “How much should I add?” But a helpful-sounding answer cannot fill a gap in verified instructions.
The measuring cup turns uncertainty into action
A farmer does not ask a dosage question as an abstract research exercise. The chemical may already be on the farm. Water may be in the sprayer. A measuring cup may be in hand. A spoken reply can become an immediate mixing decision.
That is why dosage advice needs more than a matching product name. The answer must cover the exact preparation and use conditions that the approved instruction requires. It also needs the safety details that protect the person applying it and the people returning to the field afterward.
For AgriVoice, three chemical content blocks remain unavailable because they lack verified dosage information, re-entry intervals, and pre-harvest intervals. The system’s refusal is deliberate. It is safer to tell a farmer that an extension officer must review the question than to deliver a polished answer built from incomplete details.
The farmer should not be left in an unowned queue, either. A safe escalation needs a named extension officer and a clear path for follow-up. That operational responsibility matters as much as the wording of the initial reply. The Extension Officer a Farmer’s Voice Note Needs, Before It Enters an Unowned Queue explains why.
A product name does not supply the missing instruction
A product label, a neighbour’s recommendation, or an old habit can create false confidence. None of them confirms that the advice applies to the product in the farmer’s hand, the crop stage, or the safety requirements that should accompany its use.
AgriVoice is designed so the language model selects from reviewed advice blocks. It does not write agronomy instructions from scratch. That boundary is especially important for pesticides. A system can recognize the topic of a Twi voice note and still lack the evidence needed to answer safely.
The missing information is concrete:
- The verified dosage or mixing instruction.
- The re-entry interval, so people know when it is safe to return to a treated field.
- The pre-harvest interval, so cocoa is not handled or harvested too soon after treatment.
Leaving out any one of these can change what a farmer does next. A response that mentions only an amount can sound complete while withholding the part that protects workers and the crop.
Escalation is a useful answer on spray day
A good escalation should be direct. It should acknowledge the question, explain that the chemical instruction needs expert review, and route the farmer to the person responsible for answering it. It should not pretend that delay is convenient.
For a farmer, “I need to check the exact product and safety interval with the extension officer” is more useful than a confident estimate. It preserves the decision point. It prevents the system from converting uncertainty into a number that may be wrong.
That approach also creates a record of what needs review. If similar questions arrive repeatedly, the partner and agronomist can see where approved content is missing. They can then decide whether to add a reviewed block, improve the escalation process, or keep the topic unavailable.
The standard is simple: the system should answer when it has reviewed, speakable advice. It should escalate when it does not.
The pause is part of the product
Kelsey’s decision at the FDA was not a failure to process an application. It was an exercise of care while the safety case remained unresolved. The same principle belongs in a voice workflow that may influence how someone handles agricultural chemicals.
AgriVoice is preparing for a two-week pilot with Asante-Twi-speaking cocoa farmers, not a public-scale launch. Before farmers receive chemical guidance, a Ghanaian agronomist must clear the relevant content. The pilot’s safety scorecard allows zero unsafe pesticide answers.
That requirement can feel slow when a voice note arrives at the moment someone wants to spray. Yet the alternative places the burden of uncertainty on the farmer. The right next action is to keep the held chemical blocks unavailable, assign the escalation to a named extension officer, and release an instruction only after expert review confirms every safety detail.
Comments
No comments yet.