Know What Happens to a Call—and Who Stays in Control
See what AnswerCheap can capture, which outside services do the work, where a person takes over, and what your team should test before launch.
This overview is product guidance, not legal advice or a compliance certification. Review your own recording notices, consent flow, and customer terms before going live.
- Checkable call data
- Recording choice
- Human fallback
- Real-call testing
A saved setup is step one
Settings savedYour questions or connection are on file; no real call has proved the path yet.
Connection heardThe connected service has exchanged at least one event with AnswerCheap.
Real path testedA real event, call, or billing sync has completed the path.
Call activity
Phone numbers, timestamps, call status, duration, spam signals, and routing events help show what happened and power usage reporting.
Optional call content
Recordings, transcripts, and summaries are used only when you enable the related call features.
Lead and appointment details
Names, callback numbers, reasons for calling, requested times, and follow-up notes can be captured so your team can act after the call.
Billing and provider events
Subscription status, included-minute usage, overage events, and service webhooks show billing and connection activity.
Which outside services do which jobs
A connection can be saved before it works end to end. Test the feature you plan to use and keep a fallback for failures.
Twilio
Phone numbers, inbound/outbound calling, call status callbacks, and recordings when enabled.
OpenAI
Realtime voice handling, transcription, summarization, and extraction when the AI receptionist is connected.
Stripe
Checkout, subscription portal, webhook status, and usage metering for billable minutes.
Supabase
Authentication, tenant data, call activity and notes, leads, appointments, settings, and role-gated app access.
Optional integrations
Slack, Google Calendar, HubSpot, Zapier, Make, n8n, or custom webhooks only when you choose and connect them.
AI handles routine intake; people keep the decisions
The receptionist follows your rules and captures the details. Your team chooses when it should try a person and owns the final decision.
- 01
Incoming
Rules
Business hours, intake questions, transfer targets, and recording preferences define the call playbook.
- 02
In progress
AI
The AI receptionist answers, asks follow-up questions, and summarizes the conversation.
- 03
In progress
Escalation
Transfer and callback rules can try the person you chose or preserve the details for follow-up.
- 04
Ready
Follow-up
Owners can check calls, transcripts, summaries, leads, appointment requests, billing usage, and connection health.
AI output can be imperfect. Check important calls and keep a person responsible for critical decisions.
Operational states
Setup states you will see in the app
A saved setup step is not the same as a tested call or event.
You can draft the greeting, hours, intake questions, routing, and dashboard setup before connecting live phone service.
Provider credentials must be added through secure setup before connected tests can run.
Twilio, OpenAI, Stripe, and optional integrations each need the matching account resource.
A saved number or OAuth connection still needs a real call, webhook, calendar event, or billing event.
Inbound calls and webhooks need a callback URL the connected service can reach.
Go-live should wait until phone service, billing, recording notice, escalation, fallback, and support checks pass.
Before routing real callers
Test phone service, public callbacks, billing, recording notices, human fallback, privacy terms, and the full call path before production signoff.