What AnswerCheap handles, and what still needs setup
A plain-English guide to call data, provider boundaries, AI limits, billing events, and handoffs before you route real callers through AnswerCheap.
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.
Trust cues to look for during setup
Config present means server settings or an OAuth record exists; it is not proof that live traffic works.
Webhook seen means the provider has sent at least one event to your app.
Live validated should wait for a real provider event, call, or billing sync before you rely on 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 your configuration enables the related call handling 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 meter events, and provider webhooks help keep billing and operations understandable.
Providers are involved only when the matching feature is configured
AnswerCheap coordinates several services. A fresh local or staging account may show setup screens before any live provider path is ready.
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 records, leads, appointments, settings, and role-gated app access.
Configured integrations
Slack, Google Calendar, HubSpot, Zapier/Make, n8n, or custom webhooks only when you choose and configure them.
AI answers; humans stay in control
The receptionist follows your rules, captures details, and escalates when a person should take over. Owners review the result in the app.
- 1
Rules
Business hours, intake questions, transfer targets, and recording preferences define the call playbook.
- 2
AI
The AI receptionist answers, asks follow-up questions, and summarizes the conversation.
- 3
Escalation
Configured transfer and callback paths let uncertain, urgent, or high-value calls reach a person with context.
- 4
Review
Owners can review calls, transcripts, summaries, leads, appointments, billing usage, and provider health.
AI output can be imperfect. Review important calls and configure escalation paths for critical decisions.
Readiness language you will see in the app
Setup status is intentionally separate from production readiness. A local step can be complete while live provider validation remains gated.
You can draft your receptionist, business hours, intake questions, routing preferences, and dashboard setup without live provider traffic.
Staging credentials must be populated outside chat before provider-backed checks can run. This page does not inspect those files.
Twilio, OpenAI, Stripe, and optional integrations each need resources created or configured in the provider dashboard.
Server settings or OAuth records can exist before the first real webhook, call, calendar event, or billing event proves the path works.
Inbound calls and webhooks require provider-accessible callback URLs. Localhost-only staging is not enough for real provider callbacks.
Go-live should wait until credentials, public ingress, billing, recording notice, escalation, and support processes are reviewed.
Before routing real callers
Confirm provider resources, public callback URLs, billing behavior, recording notices, human escalation, privacy/terms review, and production signoff.