Managed AI Receptionist: Answer routine questions
Use your approved services, opening hours and policies as the starting point.
Give your customers a helpful first conversation, even when your team is busy.
The exact functions and integrations are agreed before implementation.
Use your approved services, opening hours and policies as the starting point.
Ask agreed questions and capture contact details for your team.
Connect appointment requests, supported calendar bookings or a team handoff.
Receptionist packages include a VPI-provided web number, custom number porting or up to three lines depending on the plan. Country availability, carrier requirements and supported transfers are confirmed during onboarding.
Services, policies, common questions, routing rules and the tools you use.
The assistant’s conversation flow, agreed integrations and review process.
Approve the launch experience and decide which requests need your team.
Bring your country, existing telephone setup, customer languages and typical call volume to the consultation. We confirm number availability and routing before agreeing the scope. A web voice demo illustrates the conversation; it does not confirm that a particular local number or telephone integration is available.
Specify the time zone for each location, holiday hours and the person who receives callbacks. Where appointment integrations are included, agree how availability and time-zone differences will be tested. Confirm supported languages and escalation wording before launch.
Compare monthly plans in USD, included minutes and top-ups. Discuss data handling and supplier requirements, then test representative enquiries through the implementation process.
Tell us how enquiries arrive and what should happen next. We’ll help you scope a practical first step.
80, 280 or 650 included minutes, with a 7-day free trial advertised for receptionist packages.
80 included minutes
280 included minutes
650 included minutes
We agree the call types, approved business information, routing, and supported integrations before implementation. Your team reviews the configuration and tests the handoff before launch.
General receptionist plans list $29 for 80 minutes, $99 for 280 minutes, and $199 for 650 minutes per month. Confirm features and top-ups during onboarding. WhatsApp and custom automation are quoted separately.
Supported calendar booking, appointment requests, and transfers are configured according to the selected plan and integration. If a request cannot be confirmed, it should be routed to staff for follow-up.
Medical arrangements list $199 and $349 tiers with agreed BAA and data-handling scope. Review the actual services, access, retention, and contracts. Administrative assistants do not provide clinical, legal, tax, or other professional advice.
Review a live demo and agree a pilot with realistic calls, staff ownership, and acceptance criteria. A seven-day trial is advertised for receptionist packages; activation and account terms are confirmed during onboarding.
For an independent reference on evaluating AI risks, see the NIST AI Risk Management Framework.
Start by deciding which questions the assistant may answer and which require a person.
Opening hours, location, approved service descriptions, and booking procedures are useful starting points.
Keep the source information current and assign a staff owner who can approve corrections.
A confident voice should never substitute for an accurate policy or a current availability record.
Ask one question at a time and collect only information that helps the next action.
Read back important contact details and allow corrections.
Distinguish facts confirmed by the caller from assumptions and unanswered questions.
Staff should receive a usable summary rather than an unstructured transcript that requires them to repeat the entire intake process.
Voice and WhatsApp can support related customer journeys, but they are separately scoped services.
Agree whether a conversation may move between channels, which system owns the record, and who monitors replies.
Do not send a caller into an unattended message thread.
Confirm channel preferences and the appropriate handling of sensitive information before transferring details.
Document opening hours, holidays, the relevant time zone, on-call contacts, and the fallback when the first person does not answer.
A message marked urgent still needs a responsible human queue.
Tell callers what has actually happened: a request received, an attempted transfer, or a confirmed appointment.
Avoid vague promises of immediate attention when coverage has not been arranged.