Fields and clear start/stop rules
Keep the model tiny: add three fields to your lead/contact record — SLA target (minutes or hours), SLA start timestamp, SLA status (Pending / Met / Breached / Paused). These are enough to measure and act without bloating your CRM.
Decide one clear start rule and one clear stop rule. Example start: "when a record is created as a lead AND owner is assigned, set SLA start = now and SLA status = Pending." Example stop: "when status becomes Contacted or Qualified, set SLA status = Met and clear SLA start." Pause the timer for genuine holds (Do not contact, On hold) by setting SLA status = Paused and leaving SLA start unchanged.
Escalation paths and how to avoid automation loops
Keep the escalation chain short and human-first: 1) reminder to the owner at 50–75% of SLA, 2) manager alert on breach, 3) move-to-human-queue (shared inbox or round-robin) after a second breach. Each step should be an additive notification, not a state change that re-triggers the timer.
Avoid retriggers by making actions idempotent and using checks before you write values: only set SLA start if it is empty; only mark Breached if SLA status is Pending and now > SLA start + target. Use a short processing flag or a non-triggering field update to prevent workflows firing other workflows. The principle applies across HubSpot, Salesforce, Marketo and Pardot — don’t change the same property repeatedly and always check prior value before acting.
Quick platform pointers, test steps and one-page monitoring checklist
- HubSpot pointer: create three custom properties and a workflow that enrolls when "SLA start is known" and "SLA status = Pending"; disable re-enrolment on the same triggers and use scheduled delays for reminders. Use property-value checks to avoid resetting SLA start.
- Salesforce pointer: use a record-triggered Flow with entry criteria "SLA start is null and owner assigned" to set the timestamp; use Decision elements that compare NOW() to SLA start + target and a checkbox 'SLA Processing' to avoid loops. Apply the same idempotent checks.
Testing steps (60–90 minutes): configure the three fields, build the reminder and breach paths, run three smoke tests (new lead with owner, new lead no owner, lead moved to On hold). Confirm: SLA start only set once, reminders fire, breached leads appear in the breach list and do not re-enrol.
One-page monitoring checklist to keep on a sheet or dashboard:
- SLA properties exist and are populated on new leads
- Active Pending leads > 75% of target (list) — owner assigned
- Breached leads list and manager alerts log
- Human-queue has unassigned items and someone owning them
- Weekly review: false positives, paused records, and automation error notes
Rollout and local adoption tips: set a conservative SLA for your team (many Fareham/South Coast small teams start with 4–8 hours for inbound leads), run the 60–90 minute pilot with the two busiest reps, and add the breach list to the daily standup. Keep rules visible in one sentence in your ops notes so cover shifts know how to act.
If you want a practical hand to implement and test this pattern, Optira can help run the 60–90 minute setup and handover; for more on automating small-team handoffs see our workflow automation for small teams on the South Coast.