How it works
The journey of a conversation, from request to receipt
Five steps that repeat in every use case, from a Pix to an enrollment. Click each step and watch the conversation get there.
The five steps
Understands, collects, executes, confirms and hands off.
A patient books an exam on the WhatsApp of a fictional clinic. What happens in the clinic systems shows next to it.
The patient writes in her own words, no numbered menu. The agent identifies the request: booking an exam.
The agent asks for the ID through a secure form of the channel. The data goes straight to the clinic system, without passing through the AI.
With the plan confirmed, the agent queries the clinic schedule and offers the free slots. The rules (coverage, deadline, unit) belong to the system, not the AI.
The patient chooses, the agent reserves the slot and returns the receipt in the conversation: the exam voucher as PDF.
A request outside the use case goes to a person, with a summary of what already happened. They reply on the same number and, when done, hand the conversation back to the agent.
- Request recognized: exam booking
- Use case "Exam booking" triggered
- No data sent to the systems yet
Channels
One agent. WhatsApp, website and app.
You declare the use case once. The customer chooses where to talk; the agent is the same, with the same history and the same rules.
- WhatsAppOn your company numberVida Cliniconline
- I need to book this examJPGmedical-order.jpg
- I read the order: abdominal ultrasound. Which health plan?
- Saúde Plus
- Coverage confirmed. Thursday 8:10 am or Friday 7:40 am?
How it connects: Twilio, Meta Cloud API or Infobip, with the number the company already uses. Text, voice, photo and document.
- Chat on the websiteOne snippet of code on your pageLoja Norteassistant
- my order still has not arrived
- What is the order number?
- LN-48213
- Out for delivery today, expected by 6 pm. Shall I notify you when it is delivered?
How it connects: A snippet of code on the page. The color, the name and the position of the chat are your brand.
- Inside the appThe customer is already identifiedBanco SolMarina · verified
- Hi, Marina. What do you need?
- pix 350 to João
- João Pereira, R$ 350.00. Confirm with your code in the secure form.
- Confirmation codeentered outside the AI, straight to the bank
How it connects: The conversation inside the company app. The customer arrives identified and the agent skips the ID.
One single history
The customer switches channels. The agent asks nothing again.
- Starts on the websiteAsks to reschedule the exam in the clinic chat, before leaving work.
- Confirms on WhatsAppGets the slots on the phone and picks Thursday, 8:10 am.
- Receives it in the appThe exam voucher shows up in the clinic app, already in the history.
Handoff to a human
The person takes over without restarting the conversation.
The operator receives the summary, replies on the same number and, when done, returns the customer to the agent.
- Summary ready
Who they are, what they asked and what was already done.
- Reply on the same channel
Text, voice or file, on the number the customer already uses.
- Back to the agent
The agent resumes after the operator closes.
Next step
See your use case running
Thirty minutes with the sales team. You bring the request your customers make most; we show the agent executing it. Prefer to ask first? The assistant next to this text answers questions about security, channels and integration, and schedules the demo.
- 01Chat with the assistant: it asks for your details and what you are looking for
- 02The sales team receives your contact right away
- 03Demo with your use case
- 04Proposal and start of the pilot with a controlled group of customers