No business knowledge base contains every possible answer. A caller may ask about a new service, request an exception or need information from a system that is temporarily unavailable. A useful voice agent handles that gap honestly and still offers a clear next step.
Identify why the answer is missing
There are several different situations. The agent may not understand the question, the approved knowledge may not contain the answer, or the request may require an action outside its permissions. A connected tool can also fail.
These situations need different responses. If the question is unclear, ask one focused clarification. If the information is missing, say so. If the decision belongs to a person, route it to that person’s process rather than searching for a way to bypass the boundary.
Golub Voice instructions should describe these paths explicitly. “Always answer the caller” is a poor rule if it encourages a plausible invention.
A useful fallback has three parts
Explain the limit, offer an available next step and confirm the actual outcome. For example:
“I don’t have an approved price for that service. I can take your question for the team. What contact details would you like them to use?”
After collecting the details, the agent should say the request was recorded only if that happened. It should say a message was sent only if delivery was confirmed. Avoid inventing a callback deadline to make the conversation feel complete.
Do not make callers repeat themselves
Carry the relevant context into the handoff where the supported workflow permits it. A useful brief includes the question, the information already provided and what remains unresolved. Ask only for missing details; do not restart the entire enquiry when the first answer is unavailable.
If no person can take the call, explain the actual fallback. An unavailable transfer should not lead to an endless loop or a claim that someone is joining.
Turn gaps into better knowledge
Review recurring unanswered questions. Add an approved answer when the topic belongs in scope, clarify confusing instructions or improve the connected workflow. Some questions should continue to need human judgment, even if they occur frequently.
Test an unknown price, an unclear request, a policy exception and an unavailable tool. Success is a truthful, useful outcome—not an answer at any cost.
Explore Golub Voice to prepare an assistant that knows how to ask, answer and hand off. Use our knowledge preparation guide to reduce avoidable gaps while keeping uncertainty handling explicit.