The short version
The receptionist will never invent a price, a timeline or a licensing answer in your name. Anything it is not certain about goes to you instead of to the caller. Everything below is how that is enforced rather than merely intended.
How it is enforced
Tenant isolation. Business context is bound server-side. Caller- and model-supplied business identifiers are not trusted, and every tenant record is scoped by business ID with automated isolation tests.
Authenticated tools. Voice tool calls and post-call webhooks are authenticated with secrets or signatures before anything is written.
Never-say guardrails. No legal, medical, licensing, disposal, pricing, timeline or safety advice. Those calls escalate instead.
Controlled retention. Audio is retained up to 30 days and transcripts around 90, following the configured business policy. Caller objections are handled.
Booking identity checks. Reference-protected cancel and reschedule flows, tested against attempts to move somebody else's booking.
180-scenario corpus. Adversarial, compliance, robustness, failure, identity and safety scenarios run against the agent, not just happy-path bookings.
What this page is not
This describes the current controlled-beta posture. It is not a security certification, an audit report or a service-level commitment. Questions can be sent to hello@ctnode.com.