Hear a browser sample of AI call intake
Illustrative sample / not a client deployment
The recording and interactive sample are demonstrations, not customer calls or proof of a client result. The interactive sample sends microphone audio to Retell AI. Read the notice and use fictional details only.
Or watch the recorded sample
Having trouble with the embed? Open the recorded sample on YouTube
What a scoped implementation would include
- Confirm the phone routeThe carrier, phone system, call-forwarding rules, coverage, and disable path are checked for the specific business before any number changes.
- Disclose that it is AIThe approved opening identifies the assistant as AI and explains what the caller can ask for.
- Collect approved intake detailsFor example, the caller's name, callback number, requested service, and location. The business decides which fields and answers are in scope.
- Hand exceptions to a personUrgent, unclear, or out-of-scope requests go to a person. The business sets the escalation route and callback commitment before launch.
Limits for this draft
- No emergency response or dispatch. A voice agent is not a substitute for emergency services or a person who can take the call.
- No quotes, diagnoses, bookings, or promises. Those are out of scope unless separately configured and verified in a written agreement.
- No assumed phone integration. Provider, routing, notification destination, and operating costs are agreed before go-live.
- Human fallback is required. The person, route, response time, and failure behavior need to be agreed before launch.
- Privacy settings need verification. Recording, transcription, retention, and model-use settings are checked with the provider before live calls.
Want to scope your call flow?
Send your phone provider, call types, service area, and preferred human fallback route. Scope, price, timing, and support terms are confirmed before any live setup.