Email hello@woblar.com and we’ll arrange a time. Online contact requests are temporarily unavailable.
Your phone setup. Your callers’ languages.
Phone connectivity depends on your current number, phone system, provider and the chosen AI platform. We verify routing, transfer, fallback, call quality and phone and AI usage costs for the proposed setup before agreeing the connection.
Language coverage is agreed after testing how well the proposed setup hears, understands and speaks over the phone. We check relevant local accents, language switching, names and addresses with speakers, and agree a human fallback.
The call flow, provider capabilities and languages are scoped to what has been verified for your project.
A call comes in. Your team can’t pick up.
An illustrative missed or after-hours call example, not client proof or a working voice assistant demo. Routing, questions, languages, message capture and human transfer are agreed and tested per project.
Before: the caller waits for a reply.
A customer calls while your team is busy or after hours.
The call goes unanswered or reaches the existing voicemail.
Someone returns the call and asks what the customer needs.
A question needing another team member is passed on separately.
With an assistant: follow the agreed call flow.
The inbound call reaches the assistant through the agreed phone route.
The assistant answers an agreed service question from approved business information.
When a person is needed, capture the caller’s message and agreed contact details.
Human handoffPass the message and relevant details to the agreed team contact. Include live transfer only where the selected setup has been verified.
If live transfer is unavailable, follow the agreed message and follow-up process. We test the handoff and fallback with your team before go-live.
A scoped call flow. A tested handoff.
Agree the questions, boundaries, call route and next steps before building.
The agreed call flow
Define when the assistant handles calls, which approved questions it answers, what it captures and when a person takes over.
Assistant and phone connection
Configure the selected assistant and connect the agreed phone setup once routing, provider capabilities, authorised access and costs have been verified.
Tested messages and handoffs
Check representative calls, message capture, the agreed human handoff and fallback. Test live transfer where it is included in the verified setup.
Training and handover
Show your team how the call flow works, where messages go and how to use the assistant within the agreed scope.
Bring your call-handling needs and the people to test them.
Approved business information. Current service details and answers your team is prepared to give callers.
Authorised phone-system access. Permission to inspect and connect the selected setup, with changes agreed together.
An escalation contact. The person or team who receives messages and takes over when needed.
Time to test calls together. Representative scenarios and speakers to check the agreed languages, handoff and fallback.
Support after go-live. Usage costs explained upfront.
30 days of support
For 30 days from the agreed go-live, we cover faults and help using the assistant.
Phone and AI usage charges are explained before building, so you can consider the ongoing costs before committing.
Changes beyond that scope
New call flows, languages or integrations are scoped separately. We agree the work and costs before making those changes.
Do customers also message your team?
For written customer conversations, explore AI Customer Support Assistants. Channels and any connections are agreed for that project.
What should happen when you can’t take a call?
Tell us how calls reach your team now, when you need cover and who should receive messages or handoffs. Start with a free 30-minute fit call, with no commitment.