The users are standing in a field or on a substation access road. Their phone is mid-range, the connection is intermittent, and they need an answer now, spoken, in their language. Every assumption a normal chat product makes is wrong here.
Designing for the bad case first
Voice-first, text-optional
The primary interface is a call. Text is the fallback, not the other way round, because literacy and keyboard layout are both barriers.
Cache the knowledge, not the conversation
Seasonal advisory packs sync when there is signal and answer locally when there isn't. Only genuinely novel questions need the network.
Degrade to SMS, never to nothing
If the call cannot hold, the answer arrives as a message. The interaction completes even when the connection doesn't.
Repeat usage is the only honest metric for this category. Novelty gets you one call. Three and a half calls a week means it became part of how the work gets done.