Start with the enquiry and the permitted conversation
Provide the lead source, relevant enquiry details and the approved purpose of the call. Decide what the agent may explain, which optional validation questions it may ask and which decisions belong to a person. Do not use a general booking flow as a substitute for specialist advice.
Agree what happens during each call outcome
Define separate routes for no answer, voicemail, an interested lead, a wrong number, a request to stop and a question outside the approved scope. A call being answered is not an appointment. Confirm the booking before returning a booked status to the CRM.
Connect availability and human handoff
Agree the calendar, appointment duration and information needed for a useful booking. Test unavailable slots and rescheduling requests. If the lead asks for a person or needs an answer outside the playbook, return the context to the responsible owner instead of continuing the same script.
Understand the price and channel mix
Published starting engine prices are EUR 3.50, USD 4.00 or GBP 3.00 per processed lead. AI voice usage is billed separately at EUR 0.10 per minute; messaging and applicable setup costs are separate. A voice-only route and a combined messaging-and-voice route serve different contact preferences. Check the current pricing and terms.
Can the AI voice agent replace every conversation with my team?
Its scope depends on the configured playbook. Keep advice, exceptions and decisions that need a person on an explicit handoff route. Try the demonstration to assess the conversation, then agree the production scope.