Tag Conversation

Add tags to this conversation only — they go away with the conversation and do not reach segments or broadcasts.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Tag Conversation.
  2. Use Tag Contact instead if you want to find this person later — Contacts filters, segments, broadcasts.
  3. Leave Action on Add Tag and On on Conversation.
  4. Pick one or more tags from the tag buttons, or type a new one and press Enter.
  5. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • The tag never follows the person into segments or broadcasts — for that, use Tag Contact instead.
The Add Steps menu open on the canvas, with Tag Conversation highlighted.
The step panel with Add Tag picked and the vip-customer tag chip selected.
On switched to Contact, which saves the step as Tag Contact instead.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Tag Conversation under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
  • Building and running workflows depends on your plan; see pricing.
  • Nothing outside Inchat has to be connected.

Set up

  1. Open the workflow and click + where the tag belongs.
  2. Pick Tag Conversation.
  3. Leave Action on Add Tag and On on Conversation — switching either turns this into Untag Conversation, Tag Contact or Untag Contact instead, since all four share one editor.
  4. Pick one or more tags from the tag buttons already used in this workspace, or type a new one and press Enter.
  5. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Action
Add Tag or Remove Tag.
Default: Add Tag
Limits: Choosing Remove Tag saves this as the Untag Conversation step instead.
On
Whether the tag goes on the conversation or on the contact behind it.
Default: Conversation
Limits: Choosing Contact saves this as the Tag Contact step instead.
Tags
A tag button for every tag already used somewhere in the workspace, plus a box to type a new one. Several may be picked on one step.
Limits: A step keeps at most 20 tags: any past the 20th are dropped when you save, with no warning. A name typed here that is not already in the workspace's tag list is added to it automatically; a name over 64 characters is refused when you save.

How it works

  • The step writes the tag onto this conversation. A saved view's tag filter checks the contact's own tags first; a conversation tag only matches as a fallback, so a saved view built around conversation tags still finds them.
  • Adding a tag the conversation already carries, or removing one it does not have, does nothing: no error is shown, and the step still counts as ok.
  • Naming several tags on one step tries every one of them, even if an earlier one in the list failed to write.
  • The step shows as failed in the run's Activity tab if any of them did.
  • Every tag name is cleaned up before it is stored — trimmed, capped at 64 characters, and matched to the workspace's existing tag list without regard to case. Writing “sale” onto a conversation that already carries “Sale” does not create a second tag: the write is folded onto the tag list's existing spelling.
  • The step still counts that write as an add and logs “sale” on the Activity tab, but the conversation still has one tag, “Sale”.
  • A name nobody in the workspace has used before is added to the tag list at the same time it is first written onto a conversation.
  • When the conversation has a linked contact, the same tag is also logged to that contact's Activity tab — marked as added by a workflow, or by the AI agent inside an AI turn.

When it fails

  • The only realistic failure is a temporary Inchat problem reading or writing the conversation — not something you did; try again later. This action does not report a specific reason, so the run's Activity tab shows the fixed line failed without a reported reason rather than anything naming the tag.
  • A failed tag write does not stop the run. The step shows as failed in the run's Activity tab and the flow moves to the next one, so a message or close placed after it still happens on the untagged conversation.

Limits

  • It never touches the contact's own tags — a workflow that wants the tag to follow the person into segments and broadcasts needs Tag Contact instead.
  • It never removes a tag that a saved view or another workflow relies on. Clearing a state a flow moved a contact out of is the author's job — add the matching Untag Conversation step to the same branch.
  • The tag disappears with the conversation; it is not carried onto whatever new conversation the same contact starts later.

Best practices

  • Pair this with Untag Conversation on the branch that reverses it — a tag set is only useful while it says something true about the thread right now.

Use cases

  • Tag every conversation that starts from a paid ad campaign ad-lead, so the Inbox's saved view for that campaign is one filter away.
  • Tag a thread needs-quote when a customer asks about pricing, then remove it once Quote / confirm order has sent one.

Reading this with an AI assistant? Plain Markdown version.