For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/features/automations/stop-automation-when-attendant-takes-over.md.
  • English

      • How do I stop the cadence when an attendant takes over the conversation?

      Add the Attendant took over the conversation trigger to the automation's Exit conditions. As soon as a team member starts handling the contact's conversation, the contact leaves the automation: the messages still to come are not sent, and the steps at the end of the cadence (for example, marking the opportunity as lost) don't run.

      Before you start

      • Workspace role: anyone who already edits automations.
      • A cadence or follow-up automation, for example: wait → WhatsApp template → wait → template → mark as lost.
      • The conversation must be linked to a contact. A conversation with no contact yet doesn't fire the trigger.

      Steps

      1. Open the automation in the editor.
      2. On the start trigger, under Exit conditions, click Add exit condition.
      3. Search for and pick Attendant took over the conversation (category Live chat).
      4. In Account:, keep Any account to stop the cadence whichever number or account someone takes over on, or pick a specific connected account.
      5. Click Save and publish the automation.

      From then on, the contact leaves the automation right away when a team member starts handling their conversation. Only that contact's executions stop; every other contact carries on with the cadence.

      What counts as "took over"

      The trigger fires when a team member starts handling the conversation, through any of these paths:

      • the person takes over the conversation in Live Chat;
      • a manager assigns the conversation to them;
      • they receive the conversation from the AI SDR escalation team, when the agent hands the conversation to a person.

      Any account is the default because the goal is usually "stop automating for this contact": if the salesperson takes over the conversation from another number, the cadence stops too.

      Also as a start trigger

      Attendant took over the conversation can also start an automation — for example, to create a task or apply a tag when someone on the team takes over. Add it as a start trigger, with the same Account: field.

      If it didn't work

      • The contact kept getting messages: check that the automation was published after adding the exit condition and that Account: isn't set to an account other than the one where the conversation was taken over.
      • The conversation went to the queue, but nobody took it: the trigger only fires when a person starts handling it. A conversation sitting in the queue with no attendant doesn't take the contact out of the automation.
      • The conversation has no contact: with no linked contact, there is no automation execution to end.