Back to blog
Medical Tourism Operations

Medical tourism: how to stop WhatsApp bot when human takes over

A disputed quotation needs one person handling the reply. Here is how to pause automation in AriaBee, review the recorded context and test that replies and retries stay paused.

•Published: •7 minute read

To stop automated WhatsApp replies when a coordinator takes over a medical tourism conversation, use the staff composer in AriaBee’s Chats tab to pause automation, then send the manual response. The pause covers the WhatsApp chat window and session lifecycle, preventing automated replies and retries while paused.

Your team already handles patient questions, clinic quotations and travel details through WhatsApp. AriaBee is the AI operations employee for medical tourism agencies — commanded from WhatsApp. Staff delegate ordinary work by text or voice. When a conversation needs direct human handling, the web interface provides the exception workspace for reviewing context and intervening.

A quotation dispute needs a clear owner of the next reply

Consider an illustrative patient message: “Your quotation includes the hotel, but the coordinator told me I would pay separately. Which is correct?” The operations manager needs someone to check the quotation and establish what was actually promised before the conversation continues.

If automation continues while the coordinator investigates, another package explanation can give the patient more wording to dispute. The coordinator then spends time reconciling messages as well as resolving the original question. The owner inherits the cost: repeated clarification, delayed coordination and a patient who is unsure which answer to trust.

The same handover discipline applies when a patient asks whether a medical condition makes treatment appropriate. Pause the automated conversation, review what is recorded and involve the appropriate clinician. AriaBee can coordinate work and request human handoff; medical judgment remains with people.

Pause the patient conversation before replying manually

  1. Open the relevant agent. In the left navigation, select AI Sales Agents, then select the agent handling the conversation.
  2. Find the patient thread. Open Chats and browse or search the conversation list. Check that you have selected the intended enquiry.
  3. Pause automation. Use the staff composer to pause automation before sending your manual response. The help guide documents this workflow without specifying a named pause button.
  4. Review the recorded context. Inspect the messages and dated turns. Tool execution logs and captured runtime prompts are also available when you need to investigate how an answer was produced.
  5. Let the responsible person respond. Use the staff composer to send the direct manual message or an approved WhatsApp template. For the disputed quotation, establish the confirmed inclusions first. For a clinical question, obtain the appropriate clinical input.

In the quotation example, the coordinator can acknowledge the discrepancy while checking the recorded offer: “I’m checking the hotel inclusion against the quotation we sent. I’ll confirm the correct arrangement here.” This is an illustrative staff response, not an automated AriaBee script.

If resolving the issue requires a conversation by phone, see our post on when to offer a coordinator call. The decision to arrange a call and the decision to pause automated replies are separate operational steps.

What stays paused across the chat and session lifecycle

Our October 12, 2026 release extended conversation pause across the entire WhatsApp chat window and session lifecycle. Its documented behavior prevents automated replies and retries while the conversation is paused.

The retry scope matters during a handover. A coordinator may be carefully checking a disputed answer while an automated attempt would otherwise try again. The pause needs to hold during that handling period, including retry activity, so staff can resolve the case without competing automated responses.

Use the documented pause explicitly

Do not assume that sending a human reply, assigning a colleague or answering from a phone automatically pauses AriaBee. The documented intervention workflow uses the staff composer to pause automation. The release establishes suppression while paused; it does not establish automatic takeover detection.

Takeover behavior varies between products

Wabot’s takeover instructions describe manually disabling its chatbot for a conversation. Waplify’s documentation describes a workspace setting that can pause its bot when a chat is assigned or a teammate replies, with additional conditions for replies from a phone. These are different control models. For AriaBee, follow the explicit pause workflow above and verify its scope with a test contact.

Test the handover with a contact your team controls

Before using this workflow for a live quotation dispute, run a controlled WhatsApp conversation with made-up patient details. This checks the actual handover behavior on the connected line. Set the expected result for each step and inspect the transcript afterward.

  • Establish the starting behavior. Send an ordinary test enquiry and confirm that automated replies are active before the handover.
  • Pause before the manual response. Open the test conversation and pause automation through the staff composer. Send a staff message explaining that a coordinator is checking the quotation.
  • Send another patient message. From the test contact, ask a follow-up question. Confirm that no automated reply appears while paused.
  • Check manual handling. Send the coordinator’s clarification through the staff composer and verify that the test contact receives it without a competing automated answer.
  • Revisit the thread. Leave the conversation view, return to it and send another test message. Confirm that the paused conversation remains quiet.
  • Check session transitions. When the test spans a session transition, repeat the inbound-message check while the conversation remains paused. Verify the documented lifecycle scope rather than assuming a new session clears the pause.
  • Inspect retry behavior where available. If the controlled test includes an automated attempt awaiting retry, check that it does not send while paused. If no retry occurred, record that this part of the scope was not tested.

Keep a named coordinator responsible for the paused case and its next action. Before returning the conversation to automated handling, resolve the disputed information and check for outstanding clinical questions. The documented pause behavior does not specify a fixed timeout or an automatic return condition; verify the return workflow with your test contact before relying on it.

Keep the handover context inside the agency

The coordinator can review what reached the connected company line. Conversations and files on the official WhatsApp Business line connected to AriaBee are captured automatically. A promise made in a private conversation becomes available only when staff route that information through AriaBee.

For the disputed hotel inclusion, ask the colleague to supply any missing context before confirming the answer. Pausing automation cannot reconstruct an off-platform promise. Our guide to medical tourism quotation management covers the wider quotation problem.

Private staff guidance serves another purpose: it lets colleagues provide context or instructions without notifying the patient. Our post on WhatsApp internal notes explains that workflow. Use the explicit conversation pause when a person needs to handle the patient’s next replies directly.

The AriaBee medical tourism operations overview shows how these conversations connect with documents, quotations, travel and finance. During a handover, the immediate requirement is concrete: the responsible coordinator has the recorded context, automation stays paused and the patient receives the checked answer.

Frequently asked questions

How do I stop automated WhatsApp replies when a coordinator takes over in AriaBee?

Open AI Sales Agents, select the relevant agent and open Chats. Select the conversation, use the staff composer to pause automation, then send the manual response.

Does replying manually automatically pause AriaBee?

The documented workflow requires an explicit pause through the staff composer. It does not establish automatic pause detection from a human reply, assignment or phone activity. Pause before replying manually.

Does AriaBee’s conversation pause also stop automated retries?

Yes. The October 12, 2026 release documents pause across the WhatsApp chat window and session lifecycle, preventing automated replies and retries while paused.

How long does the conversation stay paused?

The documented behavior specifies what is suppressed while paused, without stating a fixed timeout or automatic return condition. Keep a coordinator responsible for the case and verify the return workflow with a test contact.

Can the coordinator see promises made in a private WhatsApp conversation?

Only when staff route that information through AriaBee. Conversations and files on the connected official WhatsApp Business line are captured automatically; private side conversations are not automatically captured.

What should happen when the patient’s question requires medical judgment?

Pause automation, review the recorded context and involve the appropriate clinician. The coordinator can manage communication, but AriaBee does not replace medical judgment or the agency’s legal responsibility.

Review a patient conversation handover

Bring an example quotation dispute or clinical escalation. Review how your team can pause automation, inspect context and handle the response in AriaBee.

Stop WhatsApp bot replies when a coordinator takes over