Ground the conversation
Recall relevant preferences and prior statements so the agent does not force the caller to repeat everything.
recall → conversational contextMemory for voice agents
Callers think aloud, change their minds, and refer to old conversations. ContextDB helps a voice agent remember all of it without treating every remembered sentence as permission to book, refund, or update.
The problem
A voice model needs context to sound coherent. The booking system needs a stricter standard. Use ordinary recall for the conversation and action recall before the tool call.
Where it fits
Recall relevant preferences and prior statements so the agent does not force the caller to repeat everything.
recall → conversational contextCheck the specific booking, refund, reschedule, or escalation against source, confidence, confirmation, and policy.
recall_for_action → act | ask | abstainStore which evidence and policy supported the result so an operator can review the action without replaying a full prompt.
decision → evidence + policy + reasonAction map
| Step | Memory mode | Why |
|---|---|---|
| Answer a general question | recall |
Relevant context can help, while the response remains conversational. |
| Book or reschedule | recall_for_action |
The call creates a commitment in another system. |
| Issue a refund | recall_for_action |
The action changes money or account state. |
| Escalate to a person | Host policy | Missing or conflicting evidence should fail closed. |
Questions
No. Keep transcripts and recordings in their appropriate systems. ContextDB stores action-relevant memories, their provenance, and the decisions made from them.
No. Your voice-agent host receives the decision and must enforce it before calling booking, billing, CRM, or scheduling tools.
Yes. Ordinary recall and action recall serve different jobs. Tentative context may help the conversation while remaining blocked from action.
Store one confirmed preference and one tentative wish, then inspect the result.