Conversation triggers (opened, closed, resolved, pending, inactivity, lookup)

Learn how to start automations when a conversation is opened, closed, resolved, left pending or sits inactive.

Jun 26, 2026

Watch this step in the video · The palette: triggers and nodes

Conversation triggers start an automation whenever a conversation in your Inbox changes state. They are the foundation for routing, alerting your team, sending surveys or tagging contacts hands-free. This article covers the conversation triggers you will reach for most.

Available triggers

  • Conversation opened — when a conversation is opened or reopened (by an agent, the API, another workflow or a customer reply).
  • Conversation closed — when someone closes the chat. It carries the resolution time, handy for CSAT.
  • Conversation marked resolved — when it is marked resolved without closing it.
  • Conversation marked pending — when it is left waiting on the customer.
  • Auto-close on inactivity and its variants customer didn't reply / agent didn't reply — fire when the inactivity sweep acts on the chat.
  • Customer waiting on agent — a periodic watcher that looks up conversations where the customer is left waiting, ideal for escalation or alerts.

Requirements

  • A plan with Automations enabled.
  • Permission to manage automations in the workspace.

Steps

  1. Open Automations from the workspace menu and click New automation → Start from scratch.
  2. In the Trigger panel (left), open Choose how it starts and pick the conversation trigger you need, e.g. Conversation closed.
  3. In Settings (right panel) tune the filters: Channel type, Assigned team, Previous status or, for closures, the resolution time. Leave them empty to react to all.
  4. Drag one or more Actions from the palette and connect them to the trigger (notify the team, add a tag, send a template, and so on).
  5. Use the Available variables tokens (such as who opened the chat or which team closed it) inside your actions.
  6. Click Save, then Activate.

Verify it

  • Click Test to fire it with sample data, then open the Run history → View trace to see exactly what happened, step by step.
  • Trigger the real event (close or reopen a test conversation) and confirm the run shows as Completed.

If it doesn't work

  • Is the automation set to Active? An Inactive one never fires.
  • Check the filters: an over-strict Channel type or Assigned team can drop the event.
  • If you chose Conversation opened with a Previous status filter, make sure that status matches (e.g. Was closed for reopens).
  • Look in Run history for Paused by limit: you hit the plan's run cap.

Tips

  • Pair Conversation closed with a minimum resolution-time filter to send CSAT only on real cases.
  • The Customer waiting on agent trigger is great for SLAs: alert the team when nobody replies in time.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp