Receptionist#

The receptionist can answer from operator-provided facts and capture a caller's message for delivery to the operator. Keep the knowledge set narrow and factual; the assistant should not invent business policy or make commitments.

Before you start#

A working local or live runtime.
A chosen greeting and escalation policy.
Consent to store the information callers may disclose.

Configure the experience#

Add the facts callers are allowed to receive, such as hours, location and service boundaries.
Write a short greeting that identifies the business and the automated assistant where required.
Configure the operator notification destination.
Define which caller details a captured message should request.
Set retention periods for transcripts, messages and operational records.
Restart the runtime after changing environment-backed settings.

Do not add passwords, internal procedures or confidential client data to the knowledge set. Review local call-consent, disclosure and messaging rules before handling real callers.

Verify#

Place a test call that asks one known and one unknown question, then leave a message. Confirm that the known fact is answered accurately, the unknown answer is declined or escalated, the message appears once in the dashboard, and the operator receives the expected notification.

If it does not work#

Symptom	Check	Recovery
A known fact is answered wrongly	Whether the knowledge entry is actually loaded, not just saved	Re-place the test call after confirming the entry appears in the dashboard
An unknown question is answered confidently	The escalation setting for unknown answers	Declining is the configured behaviour; if it is answering instead, the setting did not take effect
The message appears twice	Whether the caller left one message across a reconnect	Preserve both call identifiers before deleting either
No operator notification arrives	The notification channel independently of the call	A completed call with no notification is a notification fault, not a call fault