Untag Contact

Remove one or more tags from the person behind this conversation, so segments and broadcasts stop targeting them for a state that has passed.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Untag Contact.
  2. Leave Action on Remove Tag and On on Contact.
  3. Pick one or more tags to remove from the tag buttons.
  4. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • Removing a tag the contact lacks — even one differing only in case — is a silent no-op: nothing written, nothing on the contact's Activity tab.
The Add Steps menu open on the canvas, with Untag Contact highlighted.
The step panel with Remove Tag picked and the vip-customer tag chip selected.
On switched to Conversation, which saves the step as Untag Conversation instead.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Untag 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. The step only writes to the contact behind this conversation.

Set up

  1. Open the workflow and click + where the removal belongs.
  2. Pick Untag Contact.
  3. Leave Action on Remove Tag and On on Contact — switching either turns this into Untag Conversation, Tag Conversation or Tag Contact instead, since all four share one editor.
  4. Pick one or more tags from the tag buttons.
  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: Remove Tag
Limits: Choosing Add Tag saves this as the Tag Contact step instead.
On
Whether the tag comes off the contact or off this one conversation.
Default: Contact
Limits: Choosing Conversation saves this as the Untag Conversation step instead.
Tags
A tag button for every tag already used somewhere in the workspace. Several may be picked on one step.
Limits: A free-text box to type a name only appears when the workspace has no tags at all yet. With any tag already in the workspace, Remove offers tag buttons only, so you cannot type a name that is not on the list.

How it works

  • The step resolves the contact behind this conversation and removes the named tag from their record — the same tags Tag Contact writes, and what Contacts, segments and broadcasts read.
  • Removing a tag the contact does not carry — including one that only differs in letter case from what they actually have — does nothing: no error is shown, and the step still counts as ok.
  • That makes it safe to remove several tags that cannot be true together (for example “no-show” and “attended”) without checking which one the contact has. If a flow tags a contact “no-show”, add an Untag Contact step for “no-show” in the branch that later marks them “attended”. Otherwise the tag stays.
  • 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.
  • The tag name must match exactly, including capital and small letters, against whatever is currently stored. The workspace's tag list keeps one spelling per name, and every tag added is matched to it.
  • If the tag name is spelled with different capital or small letters than the tag that already exists, the step does nothing and shows no error.
  • This can happen from typing while the step was on Add Tag, or from the AI builder. Pick the tag from the tag buttons instead of typing it.
  • A tag actually removed (not a no-op) is logged to the contact's Activity tab — marked as removed by a workflow, or by the AI agent inside an AI turn.

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, with no specific reason set: the run's Activity tab shows the fixed line failed without a reported reason.
  • A failed removal 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 with the tag still on the contact.

Limits

  • It never touches this conversation's own tags — clearing a tag Tag Conversation added needs Untag Conversation instead.
  • The removal applies to the contact everywhere, not to this conversation's channel alone — the tag lived on the contact, not on any one thread.
  • 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.
  • Removing a tag never moves or opens a deal. Only adding a tag with Tag Contact can — a pipeline stage's tag rule only reacts to a tag being added, never to one being removed.

Use cases

  • Remove “no-show” once the same contact has attended a rescheduled session, so a broadcast that targets no-shows for a nudge stops reaching them.
  • Remove webinar-attendee if a registration is later canceled, so a segment built on past attendance does not keep counting them.

Reading this with an AI assistant? Plain Markdown version.