Disclosed by default
Any future voice or chat assistant would identify itself as automated at the start of a conversation, not after being asked.
This page describes the policy and handoff requirements for a future AI receptionist build. The IronWake site assistant is live and model-backed; client AI Receptionist deployments still require a separately scoped provider build per client.
Any future voice or chat assistant would identify itself as automated at the start of a conversation, not after being asked.
A caller or visitor could ask for a person at any point, and that request would be honoured rather than deflected.
Any quoted price or availability would come from real current data, never generated from a model prompt.
A future implementation must identify automation, provide a human handoff, and preserve an auditable escalation record. These are requirements, not current service behaviour.
The IronWake website assistant (Ask IronWake) is live, model-backed, and scoped to IronWake business questions. A phone, voice, or DM receptionist is NOT connected to this site.
No telephony, voice, messaging, or model provider is configured for client receptionist deployments. A real client deployment would require an approved provider account, a scoped model credential, a phone or messaging route, escalation coverage, and verified callback evidence before it could be described as live.
Provider terms, usage limits, recording and transcription disclosure, escalation ownership, data retention, and acceptance tests must be agreed for each client before implementation or publication.
Lite tier implementation fee:
Lite covers the agreed architecture. Standard and Pro add depth, integrations, and verified provider setup. Domain, hosting, AI compute, phone numbers, messaging, and calendar provider costs are billed directly by their providers and are never marked up by IronWake.