CHATBOTS

Route qualified Intercom chats to the right rep by territory and deal size

When an Intercom conversation gets tagged as sales-ready, it looks up the visitor's region and estimated deal size, assigns the matching account owner in Salesforce.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps4
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerIntercom conversation tagged sales-readyIntercomIntercom
  • LogicResolve territory and tier from firmographics
  • ActionAssign Salesforce lead to account ownerSalesforce
  • OutputDirect-message the owning rep with contextSlack

What it does

Replaces round-robin guesswork with deterministic lead routing. As soon as an Intercom chat is flagged sales-ready, the workflow reads the visitor's company data, decides which sales territory and tier the lead belongs to, sets the owner on a Salesforce lead record, and notifies that owner directly.

When to use it

You run inbound chat through Intercom and have a sales team split by geography or segment (SMB vs. enterprise). Use this when good leads keep landing in a shared inbox and going stale because nobody owns them.

How it works

  1. 1An Intercom conversation tagged "sales-ready" fires the trigger with the visitor and company attributes.
  2. 2A logic step maps region and headcount to a territory and tier using your routing rules.
  3. 3A Salesforce lead is created or matched and assigned to the resolved account owner.
  4. 4The workflow looks up that owner's Slack handle and sends them a direct message with the conversation context and a deep link back into Intercom.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.