Automations
⚠️ Core Features6.4GHL

Maintenance

Monitors calls, STOP replies and stop-bot tags — tagging call activity and running a full opt-out compliance sequence across every channel.

4 triggers 11 steps 4 branches Advanced
What it does

This automation monitors four critical system events simultaneously and routes each into the appropriate maintenance action. Inbound and outbound calls are tagged accordingly and exit cleanly. Unsubscribe or stop bot triggers run through a full compliance sequence — applying DND across all channels, disabling the bot from responding, turning the AI bot off entirely for that contact, editing the conversation status, and removing the contact from all active workflows. Unrecognised triggers exit without action.

The value

This is the system's self-regulating compliance engine — the automation that ensures the platform never contacts someone who has asked to stop being contacted, and never lets a bot continue running on a conversation that needs to be closed. Without this, unsubscribe requests can fall through the cracks, bots can continue firing on contacts who've opted out, and the business risks both reputational damage and regulatory exposure under Australian spam and privacy laws. With it, every opt-out is handled instantly, completely, and across every channel simultaneously.

Where it fits

This sits as a foundational infrastructure automation that runs quietly in the background across the entire system. It's not a revenue generator — it's a revenue protector. For clients operating at volume with active AI bots and multi-channel communication, this automation is essential for maintaining list hygiene, protecting sender reputation, and staying compliant with Australian Communications and Media Authority (ACMA) regulations. In client conversations, this is the answer to "what happens if someone wants to opt out?" — the system handles it immediately and completely, automatically.

Overall purpose

This workflow manages call activity and unsubscribe requests. It listens for inbound calls, outbound calls, STOP/Unsubscribe replies, and a "stop bot" tag being added. Based on the trigger, it either tags the contact appropriately or completely disables future bot communication by enabling Do Not Disturb (DND), updating contact records, archiving conversations, and removing the contact from all active workflows.

The build — trigger → steps → branches

Triggersentry point

Incoming Call

Call Status

Call Direction = Inbound

Identify contacts who initiate inbound phone calls.

Outbound Call

Call Status

Call Direction = Outbound

Identify contacts who receive outbound phone calls.

Customer STOP / Unsubscribe Reply

Customer Reply

Accepted keywords: STOP, Stop, stop, Unsubscribe

Detect contacts requesting to stop future communications.

Stop Bot Tag Added

Contact Tag Added

Tag = stop bot

Manually disable bot communication for a contact.

If / Elsesplits into 4

Which trigger started the workflow?

Inbound Call2 steps
  1. Tag — Inbound Call

    Action

    Add Tag · inbound call

    Mark the contact as having participated in an inbound phone call for reporting, segmentation, and future automation.

  2. Workflow Ends

    End
Outbound Call2 steps
  1. Tag — Outbound Call

    Action

    Add Tag · outbound call

    Mark the contact as having participated in an outbound phone call.

  2. Workflow Ends

    End
Unsubscribe / Stop Bot6 steps

Entered when a customer replies with STOP or Unsubscribe, OR the "stop bot" tag is added.

  1. Enable DND

    Action

    Enable Do Not Disturb · All Communication Channels

    Prevent all future automated communications with the contact.

  2. Alert Human User

    Action

    Add Tag · alert user

    Flag the contact so the bot no longer responds and indicate that a team member may need to take over.

  3. Turn Off Bot

    Action

    Update Contact Field · Bot Status = No Bot

    Persistently record that automation has been disabled for this contact.

  4. Archive Conversation

    Action

    Edit Conversation · Mark as Read + Archive

    Close the conversation and keep the inbox organized.

  5. Remove From All Workflows

    Action

    Remove From Workflow · All workflows (incl. current)

    Immediately stop every active automation for the contact to ensure no additional messages or actions are triggered.

  6. Workflow Ends

    End
None (Fallback)1 steps

Acts as the fallback branch when none of the configured trigger conditions match; the workflow simply ends.

  1. Workflow Ends

    End

    No Actions

Timeline

  1. 1Incoming Call → tag: inbound call
  2. 2Outbound Call → tag: outbound call
  3. 3STOP reply or stop-bot tag → enable DND (all channels), tag alert user, set Bot Status = No Bot, mark read + archive conversation, remove from all workflows
  4. 4No match → no actions
complianceopt-outdndcallsmaintenance