SOP for Last 72 Hours: The Agency Lead Response Playbook

A repeatable daily procedure your team runs against every contact your CRM created in the last three days, so nothing goes cold while everyone assumes someone else has it.

Ask an agency owner where leads are lost and you will usually hear something about the offer, the ad, or the price. Look at the CRM instead and the answer is duller and more fixable: a contact came in, an automation sent the first message, and then nothing happened for a week because no person was ever told the contact was theirs. The gap sits in the first three days.

That is what this procedure covers, and it is deliberately narrow: not your whole pipeline, just what your team does every working day with everything the CRM created since the day before yesterday.

What an SOP for Last 72 Hours Actually Covers

The document has one job: turn a rolling three-day window of new activity into a list somebody owns, works through, and closes out before they log off. Everything else — nurture sequences, long-term reactivation, quarterly reviews — sits outside it. Keeping the scope this tight is what makes the procedure survive a busy week, because a page somebody can finish is a page somebody actually opens.

Why the window is three days and not one

A one-day window punishes the ordinary shape of a work week. A lead that lands on Friday evening gets looked at once, on Monday, by which time it is already old under a 24-hour rule and quietly drops off the list. A seven-day window has the opposite problem: it is long enough that a contact can sit untouched for most of it and still look current, so urgency drains out of the review.

Three days spans a weekend, tolerates one sick day, and is still short enough that the person working the list remembers the names on it — and a rep who recognises a name from yesterday writes a different second message than one meeting the record cold.

Build the smart list before you write the procedure

Write the filter first. A procedure that says “check the new leads” without pointing at a saved view is a procedure that produces a different list for every person who runs it.

The filters that define the window

• Date created within the last 72 hours — a relative filter, never a fixed date range, or the list silently freezes the day it was saved.
• Assigned user — either a specific person, or deliberately empty, because unassigned records are the ones that go missing.
• Pipeline stage limited to the earliest stages, so a contact already in a proposal stage is not dragged back into a first-response routine.

What to exclude, and why the exclusions matter more

Exclude anything already booked, anything marked as a duplicate, and anything created by an internal test. Test records are the usual reason a team stops trusting a list: two or three obvious fakes near the top and people start skimming instead of working. Exclude bulk imports too, unless the team knew one was coming — an upload can fill a three-day window overnight and turn a short routine into an afternoon.

The daily run: four passes over the same list

1. Triage. Open the list and split it by source. A form fill, an inbound call and a paid-social lead deserve different first sentences, and sorting them once is faster than deciding record by record.
2. Ownership. Assign every unowned record to a named person before anyone starts messaging. An unowned record with three outbound messages against it is worse than an untouched one, because it looks handled.
3. Contact. Work the list top to bottom in one sitting. Whatever channel you use, the note goes on the record the moment the attempt is made, not at the end of the day from memory.
4. Close-out. Every record on the list ends the day in one of the three states in the table below. None of them is “still on the list tomorrow because I did not get to it”.

Let automation take the first touch and the SOP take the rest

The first response should never be a human task. Speed to first contact is the one part of this that software does better than any rota, and a workflow that fires on record creation removes an entire class of failure from the procedure. Where automation runs out is judgement: deciding a lead is unqualified, that a second call is worth making, or that a record duplicates one from last month.

Two supporting mechanisms are worth building before the SOP goes live. A time-based rule that flags a record which has had no human touch inside the window makes the failure visible rather than invisible — the same logic as a stale opportunity trigger, applied earlier in the pipeline. And a response-time standard, set up the way a conversation SLA is, gives the escalation step something objective to fire on instead of a manager’s impression that things feel slow.

The three states a record can end the day in

The reason code on the third row is the part teams skip and later regret. Without it you cannot tell whether the window is full of bad leads or of good leads nobody reached — two problems with opposite fixes.

Ownership, escalation and the handoff

Name a single owner for the list itself, separate from the reps who work it. That person confirms once a day that the list is empty by close of business, and escalates when it is not — as a defined action, not a feeling. A task assigned to a named manager with a due time works; a message in a group chat does not.

Handoffs between shifts, or between a setter and a closer, are where the window leaks. Build the handoff as a record change rather than a conversation: reassign the contact, add a note in a fixed format, and let the receiving person’s own view pick it up. A handoff that exists only as something someone said does not survive a day off. Where a step genuinely needs a person to decide before the sequence continues, a pause step such as a manual action keeps the record in the automation rather than dropping it out of it.

What to measure so the procedure can be corrected

Four numbers, reviewed weekly, are enough to tell whether the SOP is working:

• Time from record creation to first human touch — the number the whole procedure exists to protect.
• Share of records leaving the window in each of the three end states — a sudden rise in “closed out” usually means a traffic source changed, not that the team got stricter.
• Records that aged past 72 hours without a touch — this should trend to zero, and any non-zero week deserves a named cause.
• Contact attempts per engaged record — if this climbs, the first-touch message is doing less work than it used to.

Scoring can make the list easier to work in what order, but treat it as a sorting aid rather than a filter. A lead scoring setup that quietly hides low-scoring records from the view will eventually hide a good one, and nobody will notice because the record never appeared.

How the procedure quietly stops working

Three failure modes account for most of it. The saved filter gets edited by someone building a different report, and the list narrows without anyone noticing — so put the filter definition in the SOP itself and check it monthly. The list grows past what one person can work in a sitting, usually after a campaign launch, and the routine turns into skimming — so define a volume above which a second person is pulled in, before it happens. And the close-out step erodes first, because it is the least satisfying part, leaving a window that looks clean while records drift out the side.

None of these are exotic. They are the ordinary decay of a manual routine, which is why the SOP should be short, owned by a name, and reviewed against its own four numbers.

Frequently Asked Questions

Why an SOP for last 72 hours rather than a same-day rule?

A same-day rule breaks across weekends and days off, and records that fall outside it disappear from the view rather than being worked late. Three days covers a normal work week’s edges while staying short enough that the person working the list still recognises the names on it. The window is a floor for attention, not a target for response time — first contact should still happen through automation within minutes.

Should the first message in the window be sent by a person or by automation?

By automation. Speed to first contact is the part software does more reliably than any rota, and firing a workflow on record creation removes an entire failure mode from the procedure. The SOP then covers what automation cannot do: assigning an owner, judging fit, spotting duplicates, and deciding whether a second attempt is worth making.

What should the smart list filter on?

A relative date-created filter covering the last 72 hours, an assigned-user condition, and a pipeline stage limited to the earliest stages. Use a relative date filter rather than a fixed range, or the saved view freezes on the day it was created and slowly empties. Exclude test records, known duplicates and bulk imports the team was not expecting.

What are the end states a record should be in by close of business?

Engaged, attempted, or closed out. Engaged records move into the normal pipeline. Attempted records drop into a longer nurture sequence with a scheduled re-touch. Closed-out records get a reason code and leave active follow-up. Anything still sitting on the list untouched at the end of the day is the failure the procedure exists to prevent.

Who should own the 72-hour list?

One named person, separate from the reps who work it. Their job is to confirm the list is empty at close of business and to escalate when it is not. Escalation should be a defined action with a due time attached to a named manager, because a message in a group chat leaves no trace and no owner.

How do you tell whether the SOP is actually working?

Track time from record creation to first human touch, the share of records leaving in each end state, the count that aged past the window untouched, and contact attempts per engaged record. The untouched count should trend toward zero, and any week where it does not deserves a named cause rather than a general observation that things were busy.

What usually causes the procedure to decay?

Someone edits the saved filter while building an unrelated report and the list quietly narrows; a campaign launch pushes volume past what one person can work in a sitting and the routine turns into skimming; or the close-out step erodes because it is the least satisfying part, leaving a window that looks clean while records drift out of it unrecorded.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.