Tag Contact

Add tags to the person behind this conversation — read by Contacts, segments, broadcasts, and able to move a deal via a pipeline rule.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Tag Contact.
  2. Use Tag Conversation instead if the tag is only about this one chat.
  3. Leave Action on Add Tag and On on Contact.
  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

  • A tag configured under Pipelines → Manage pipelines can also move or open a deal — check there before assuming a tag step only tags.
  • The AI agent can tag contacts too. Which tags it may use is chosen on the agent's Actions page.
The Add Steps menu open on the canvas, with Tag Contact highlighted.
The step panel with Add Tag picked and the vip-customer tag chip selected.
On switched to Conversation, which saves the step as Tag Conversation instead.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Tag Contact 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 Contact.
  3. Leave Action on Add Tag and On on Contact — switching either turns this into Tag Conversation, Untag Conversation 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 Contact step instead.
On
Whether the tag goes on the contact or on this one conversation.
Default: Contact
Limits: Choosing Conversation saves this as the Tag Conversation 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 resolves the contact behind this conversation and writes the tag onto their record — what the contact sidebar shows, what Contacts filters by, and what segments and broadcasts target. It does not touch the conversation's own tags; that is Tag Conversation's job.
  • It works even if nothing earlier in the workflow looked up the contact.
  • Adding a tag the contact already carries does nothing: no error is shown, and because nothing changed, nothing new is logged to the Activity tab either.
  • 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 contact who already carries “Sale” does not create a second tag.
  • The write is folded onto the tag list's existing spelling, though the step still counts it as an add and logs “sale” on the Activity tab.
  • A tag actually added (not a no-op) is logged to the contact's Activity tab — marked as added by a workflow, or by the AI agent inside an AI turn.
  • A pipeline stage can be configured, under Pipelines → Manage pipelines, with “Tagging a contact with these moves its deal here (forward only)”.
  • Adding a tag on that stage's list moves this contact's already-open deal in that pipeline forward to it. If the contact has no open deal in that pipeline, a new deal is opened only if they have never had a deal there. A won or lost deal counts as having had one.
  • That move fires Deal Stage Changed for any workflow listening on it, with Moved by set to A rule or import. A tag not configured on any stage does none of this — the workflow author decides which tags matter by setting them up there.

When it fails

  • This conversation has no linked contact: the step fails with this conversation has no contact to tag, and nothing is written.
  • A temporary Inchat problem reading or writing the contact — not something you did — also fails the step. This is a different case from the one above: no specific reason is set for it, so the run's Activity tab shows the fixed line failed without a reported reason instead of the message above.
  • 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 contact.

Limits

  • It never touches this conversation's own tags — a workflow that wants the tag to disappear with the thread needs Tag Conversation instead.
  • The tag applies to the contact everywhere, not to this conversation's channel alone — a contact who writes in on two channels carries the same tag on both.
  • It does not fire this workspace's Contact Tag Updated trigger for other workflows. Only a change made in Contacts, the inbox sidebar, the app or the public API does that — use Trigger Another Workflow to hand off on purpose instead.
  • There is one exception, though: a tag that a pipeline stage watches for (see How it works) can still open or move a deal.
  • That still fires Deal Stage Changed for other workflows — even though this specific trigger never fires.

Best practices

  • Reach for this step, not Tag Conversation, whenever a later broadcast or segment needs to find the same people again.
  • Check Pipelines → Manage pipelines for stages with tags configured under "Tagging a contact with these moves its deal here" before assuming a tag step only tags — one of these tags can also move a deal.

Use cases

  • Tag a contact webinar-attendee after Record Attendance marks them attended, so a later broadcast can target exactly that segment.
  • Tag a contact vip once their deal crosses a value threshold, so every future conversation with them is visible in one Contacts filter.

Reading this with an AI assistant? Plain Markdown version.