LEAD GENERATION

Route Hot Conference Leads to Reps in Teams

When a conference lead's score crosses the hot threshold, posts a routed alert to the owning rep in Microsoft Teams with the intent signal and a one-click link to the Attio record.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAttio lead score updatedAttio
  • LogicFilter to hot threshold and not-yet-alerted
  • LogicRoute lead to owning rep
  • ActionPost routed alert with signal and link to TeamsMicrosoft Teams
  • OutputMark record alerted in AttioAttio

What it does

Gets the hottest conference leads in front of the right rep instantly. When a lead's priority score crosses your 'hot' threshold, the flow figures out which rep owns that territory or account and posts a targeted alert in Microsoft Teams, including the intent signal that fired and a direct link to the Attio record so the rep can act in seconds.

When to use it

Use it during and right after a busy conference when scoring is updating in real time and you can't have reps refreshing a queue. It pushes only the truly hot leads to the person who can act, instead of flooding a shared channel.

How it works

  1. 1The flow triggers when an Attio conference lead's score is updated.
  2. 2A filter passes only leads that cross the hot threshold and haven't already been alerted.
  3. 3A routing step maps the lead to the owning rep by territory, industry, or account ownership.
  4. 4A Teams message is posted to that rep with the lead name, company, firing intent signal, and a link.
  5. 5The Attio record is marked 'alerted' to prevent duplicate pings.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AttioReal-time CRM with structured data + powerful views.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.