WhatsApp Business Assistant: Respond with context
Answer routine questions using your business information.
Turn customer messages into useful enquiries and clear next steps.
The exact functions and integrations are agreed before implementation.
Answer routine questions using your business information.
Gather the details your team needs before a consultation or quote.
Scope bookings, quote requests and follow-ups around your existing process.
Implementation depends on your WhatsApp Business account, provider setup and approved messaging requirements. Provider and messaging usage charges are quoted separately; outbound campaigns are a separate scope.
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.
Start with the business number you want to use, the countries and languages your customers contact you from, and the tasks you want the assistant to handle. Number setup, account access and supported integrations are reviewed before implementation.
Provide approved prices, opening hours, delivery or service areas and the details your team needs for follow-up. Identify the business time zone and who receives enquiries. Confirm supported languages, message workflows and any supplier requirements in the project scope.
A first implementation might answer service questions and collect a callback request. Booking, payment or CRM integrations need their own agreed scope and testing. Review remote setup and data-handling requirements, then request a scoped WhatsApp quote.
Tell us how enquiries arrive and what should happen next. We’ll help you scope a practical first step.
WhatsApp implementations are separately quoted. The receptionist minute packages apply to the AI Receptionist product.
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.