How to build speed-to-lead alerts

What matters here

• Send the alert where the rep already works, with the lead, the account and the reason it was routed. A bare link to a CRM record makes them do the research first.
• Start the clock on arrival, not on assignment. The buyer has been waiting since they pressed submit.
• Escalate on a timer. If nobody has touched a hot lead in five minutes, the manager hears about it before the buyer gives up.
• Reassign leads nobody picks up. A lead sitting with a rep who is out sick is worse than a lead in a shared queue.
• Stop the clock on a real first touch, a logged call or a sent email, not on the rep opening the record.

Who this is for

You run sales operations or revenue operations. Routing already assigns leads, but response time still varies from minutes to days depending on who got the lead and what else they were doing. You want every hot lead called fast, and a clear record when one was not.

How it works in practice

What happens between a lead being assigned and the first call.

1. 1

   The lead is assigned and the clock starts

   The arrival time is already on the lead. The alert workflow reads it, the target for this lead type, and who owns it.

2. 2

   The rep gets one message with everything on it

   Name, title, company, size, what they asked for, the account owner if there is one, and buttons to accept or pass. In Slack or Teams, wherever the rep works.

3. 3

   Only real contact stops the clock

   The clock stops on the first logged call, sent email or booked meeting. Opening the record or clicking accept does not count as contact.

4. 4

   Past the target, it escalates

   The rep gets a reminder at half the target, and the manager and the team channel are told at the target, with how long the lead has waited.

5. 5

   Past the hard limit, it is reassigned

   The lead goes to the next available rep in the same pool, the original owner is told why, and the reassignment is stamped on the lead.

6. 6

   Every lead's time lands in reporting

   Arrival, alert, first touch, escalations and reassignments, so response time by rep and by source is one query away.

Paste these into Claude Code or Codex with the Tray Headless plugin installed. Each stage runs on its own. The systems named in them are the worked example rather than a requirement, and every prompt says so.

Once per project, run /tray-workflows:set-workspace to pick the workspace these build in. Point it at a sandbox first.

1. 1

   Set up, and see what is actually connected

   Before anything is built, confirm the ground truth.

   Headless skills build-workflow

   Copy

   Use build-workflow. The systems in play are Salesforce, Slack,
   Microsoft Teams, Outreach, Workday and Snowflake, or whatever we run in
   those seats. Before you plan anything, tell me which are already
   authenticated in the workspace. I expect Salesforce, Slack and
   Outreach.
   
   Tell me what is missing, and do not stub a connector I have not
   authenticated.

2. 2

   Send one alert with everything on it

   The message the rep acts on, so it has to be enough on its own.

   Headless skills build-workflow

   Copy

   Use build-workflow. Trigger when Lead.OwnerId changes to a user (not a
   queue) and Status is Marketing Qualified.
   
   Post a direct message to the owner in Slack with: name, title, company,
   employee count, what they asked for (form name and any free text),
   lead source, the matched account and its owner if different, the
   routing rule that fired, and how long ago the lead arrived. Add two
   buttons: Accept and Pass.
   
   Accept stamps Accepted__c. Pass sends the lead back to routing with
   the rep excluded and a reason. Both write to Salesforce.

3. 3

   Start the clock and stop it on real contact

   The part most alerting leaves out.

   Headless skills build-workflow

   Copy

   Targets come from a table I can edit, by lead source:
   
     demo or contact request: target 5 minutes, hard limit 30
     trial signup: target 30 minutes, hard limit 4 hours
     webinar attended: target 1 day, hard limit 3 days
   
   The clock starts at Arrived__c on the lead. It stops at the first
   Task of type Call or Email logged against the lead, or the first
   meeting booked, or the first Outreach email sent. Stamp
   First_Touch__c and the minutes taken.
   
   Count business hours only for the rep's region. A form at 23:00
   starts its clock at 08:00 local.

4. 4

   Escalate, then reassign

   Because the clock is only useful if something happens when it runs out.

   Headless skills build-workflow tray-patterns

   Copy

   At half the target with no first touch, send the rep a reminder in
   the same Slack thread.
   
   At the target, post to the team channel and tell the rep's manager,
   with the lead, the owner and the minutes waited.
   
   At the hard limit, send the lead back to routing with the owner
   excluded, stamp Reassigned_Reason__c, and tell the original owner.
   Never reassign a lead that has an open opportunity on its account.

5. 5

   Handle the four things that break it

   Each one has left a hot lead waiting.

   Headless skills tray-gotchas

   Copy

   Use tray-gotchas, then handle these explicitly:
   
   The rep is out. Read approved time off from Workday and the Slack
   status. If they are away, skip the alert and reassign at once.
   
   The rep works in Teams, not Slack. Send the same card to Microsoft
   Teams based on a field on the user record.
   
   The same lead is routed twice. Keep one clock per lead, and let a
   second assignment take over the existing one rather than start fresh.
   
   Nobody is available in the pool. Post to the team channel and the
   sales manager, and keep the lead with the original owner rather than
   bouncing it.

6. 6

   Report it, then hand it to ops

   The step that tells you whether it worked.

   Copy

   Land every alert, touch, escalation and reassignment in Snowflake.
   Weekly, report median and 90th percentile time to first touch by lead
   source, by rep and by hour of day, plus the count of leads that hit
   the hard limit.
   
   Then open the workflow in Tray Build so sales operations can change
   targets and escalation steps without a coding assistant.

   The hour-of-day view is usually where the gap is. Leads that arrive at lunch or after 4pm wait the longest.

What it connects to

Alerts read from the CRM and write to wherever reps spend their day.

Named systems are the ones most teams run, not the only ones that work. Each is an authentication in your Tray workspace, referenced by name, so the workflow never holds a credential. Where we have a connector page, the name links to it.

Questions people ask

Further reading

Background on the same subject, for the case rather than the build.

• Lead routing automation: why rules outlive the org chart
• Lead processing pipelines: what they are and what stalls them

Related guides