Back to blog
Medical Tourism Operations

Beyond a WhatsApp chatbot flow builder: medical tourism sales paths

A conversation diagram needs clear rules for patient identity, missing files and clinical questions. Here is how to configure and test those paths in AriaBee before publication.

•Published: •8 minute read

When evaluating a WhatsApp chatbot flow builder for medical tourism sales, check how it controls progression beyond scripted replies: who is receiving treatment, which files are required, what happens when information is missing and when staff must intervene. In AriaBee, use the visual editor to design the conversation, configure the separate goal and prerequisite controls, then test realistic scenarios before publishing a live version.

Your agency already works through WhatsApp. Patients send reports there; relatives explain cases there; coordinators discuss the next step there. AriaBee is the AI operations employee for medical tourism agencies — commanded from WhatsApp. Its web configuration workspace is where owners and administrators set and review how that work should happen.

What our November 7 visual editor adds

On November 7, 2026, we introduced an interactive visual editor that lets staff design, customize and save how sales agents navigate prospect conversations. It gives the team a visual way to review the intended selling path.

The surrounding controls have separate jobs. Ordered goals establish which milestone the agent pursues first. Capabilities determine which actions are available. Document policies establish prerequisites. Guardrails define prohibited claims and tactics. Scenario tests provide conversations to inspect. Drawing a path does not, by itself, establish that every prerequisite will work as intended.

This also differs from Meta’s WhatsApp Flows. As Infobip’s documentation explains, those use interactive screens with components such as text fields, radio buttons and checkboxes. AriaBee’s release concerns the design of sales-agent conversation paths; it is not a claim that the editor builds or publishes Meta WhatsApp Flows.

Start with the conversation your coordinator would have to repair

Consider an illustrative enquiry: “I’m asking about treatment for my mother. I have her report. Can we speak tomorrow?” A weak chatbot sequence can collect the sender’s name and move straight to a booking. The coordinator then has to establish whose treatment is being discussed, whether the report belongs to that person and what remains missing.

For an operations manager, that means repeated questions and clinic clarification work. For the owner, it means coordinator capacity spent reconstructing an enquiry that appeared ready to advance. Across the wider patient journey, incomplete or mistyped details can contribute to mis-scheduled appointments, wrong bills and missed travel arrangements.

Aviral’s builder page describes generic triggers, questions, branches, simulation and handoffs. Those are useful building blocks. A medical tourism agency must also decide whose documents count, which prerequisites apply and which questions require human judgment.

A worked sales path: a daughter enquiring for her mother

Use the following as an agency-specific design brief for the visual editor. It is a proposed conversation, not a transcript from a customer or a universal clinical protocol.

  1. Establish the patient. The sender says she is enquiring for her mother. Confirm that relationship before treating the sender’s personal details as the patient’s details.
  2. Collect the agreed files. Request the medical documents your team has identified as necessary for this enquiry. Enable file intake and place the relevant collection goal before the consultation goal.
  3. Resolve missing information. If the daughter sends only part of the requested material, identify what remains outstanding. If an identity document is required by the agency’s configured policy, apply that requirement at the relevant step.
  4. Route clinical questions. If she asks whether her mother is medically suitable or whether an outcome is guaranteed, arrange staff clarification or clinical review rather than letting sales progression supply a medical answer.
  5. Proceed when the configured prerequisites are met. For a consultation path, use the enabled booking capability and configured calendar availability. Keep the patient, submitted material and outstanding questions clear for the person taking over.

Review each transition with the responsible coordinator. Ask what evidence makes the next step appropriate and what should happen when that evidence is absent. A report arriving is an event; it does not establish clinical suitability.

Put progression rules into the documented controls

Open AI Sales Agents and select the agent. In Goals, arrange the required milestones using Move Up and Move Down. The agent advances the highest unfulfilled goal first. For this example, prioritize medical file collection ahead of the consultation milestone.

In Capabilities, enable File Intake for requesting and receiving medical documents. Enable Callback Scheduling if the agent should offer and book calls.

Under Requests to the lead, enable Ask who is being treated. This requires the lead to specify the treatment recipient before call availability can be checked or booked.

Then decide which identity prerequisites your agency actually needs. AriaBee separately documents Require patient ID before a sales call, Require patient ID before doctor review and Require patient ID before a price quotation. These are configurable agency policies, not a statement that every medical tourism enquiry must supply identification at first contact.

Document prerequisites have a limited meaning

Receiving or reading a document does not prove its authenticity. A completed identity step does not establish medical suitability. AriaBee can read documents, ask for clarification and coordinate approved workflows; medical judgment and the agency’s legal responsibility remain with people.

Give the missing-information path an owner

Configure Hours between reminders and Reminders before staff are alerted so an incomplete request has a defined follow-up policy. In Operations, configure Notify staff on escalation and the responsible recipient.

In Guardrails, enable Medical Safety to include the configured medical safety text in the agent’s prompt. Add statements such as “This treatment guarantees the result you want” to Forbidden Claims. These instructions still need testing against realistic patient questions.

Test the detours before publishing the conversation

Use Save to preserve draft changes, then open Test. AriaBee’s scenario testing uses a synthetic lead model. You can configure the opening message, language, personality, treatment goals, budget concerns, stop conditions and test medical files.

Use made-up patient details and test files. Before running simulations, review the test settings governing outbound WhatsApp delivery and keep live outbound messages disabled for this review.

  • Relative asking for treatment: Start with “This is for my mother.” Check that the conversation establishes the treatment recipient before checking or booking call availability.
  • Missing prerequisite: Request a call while withholding an identity document required by your configuration. Check that scheduling remains held and the agent explains what is missing.
  • Unreadable identity photo: Supply an unclear test image. Check whether the agent requests a clear replacement rather than treating the upload as completed identification.
  • Clinical certainty request: Ask “Can you guarantee she is suitable?” Check that the response avoids a guarantee and seeks appropriate staff or clinical review.
  • Files arriving during scheduling: Send test documents while discussing call times. Check that the response remains coherent and the next action is clear.
  • Returning conversation: Refer to material already submitted. Check for unnecessary repeat requests and inspect whether the agent uses the available conversation context.

Review the score, turn count and message log together. A favorable score is not enough if the log shows a call offered before patient confirmation or an unsupported medical promise. Define the expected behavior for each scenario, inspect deviations and rerun affected cases after changes.

Keep answer maintenance separate from path design. If the conversation reaches the correct step but quotes outdated package information, use the workflow in our post on keeping medical tourism answers up to date. For the decision to offer a coordinator call, see medical tourism sales objections.

Saving the design and publishing it are separate actions

The documented publication workflow distinguishes draft storage from live changes. Save saves the draft. Once the configuration is saved and reviewed, Create Version publishes it as a live agent version.

After publication, inspect relevant conversations in Chats. The documented review tools expose messages, tool execution logs and captured runtime prompts. Use them to investigate whether the intended progression occurred. Staff can also pause automation and send a manual response when intervention is needed.

For case-specific guidance, our post on WhatsApp internal notes explains the private staff workflow. The broader AriaBee medical tourism operations overview shows where sales conversations fit alongside documents, quotations, travel and finance.

Frequently asked questions

What should a medical tourism agency look for in a WhatsApp chatbot flow builder?

Look beyond scripted replies. Check patient-subject confirmation, ordered goals, configurable document prerequisites, clinical escalation, scenario testing and publication controls. Ask to see how the proposed conversation behaves when information is missing.

What does AriaBee’s visual selling-flow editor do?

The November 7, 2026 release introduced an interactive visual editor for designing, customizing and saving how sales agents navigate prospect conversations. Goals, capabilities, document policies, guardrails and testing are separately documented controls.

Is AriaBee’s selling-flow editor the same as Meta WhatsApp Flows?

No. Meta WhatsApp Flows use interactive screens with form components inside WhatsApp. AriaBee’s documented release concerns sales-agent conversation design; it does not establish Meta Flow creation or publication.

Can AriaBee hold a booking until the patient and required documents are established?

AriaBee has a configurable patient-subject requirement before call availability is checked or booked. It also has separate identity prerequisites for sales calls, doctor review and price quotations. Configure the relevant policies and test the missing-information paths.

Does saving a conversation configuration publish it?

Save preserves draft changes. The documented action for publishing the saved configuration live is Create Version. Review scenario results and conversation logs before publication.

Review a medical tourism sales path

Bring an example enquiry and the prerequisites your team uses. See how the conversation can be designed, configured and tested in AriaBee.

Beyond a WhatsApp chatbot flow builder | Medical tourism