New Lead Follow-Up Template: Acknowledge and Assign

A new lead should not enter a generic message sequence before the team knows why the person contacted the business and who owns the reply. Start smaller: preserve the request, acknowledge it, assign one person, ask one useful question, and stop when the route is no longer valid.

Copy the workflow template

Template name:
What starts it:
Do not start when:
Information needed:
Checks before contact:

Step 1 — capture
- What to record or update:
- Source ID, date and time:
- If recording fails:

Step 2 — acknowledge
- Message:
- Expectation the team can keep:

Step 3 — assign and accept
- How to choose the owner:
- Primary owner and backup:
- Time allowed to accept:

Step 4 — useful follow-up
- One question that changes the next route:
- Approved sources for the answer:

Stop immediately when:
If nobody accepts:
What proves completion:
Who reviews it and when:

Estimated completion time: 25–35 minutes after the required information, available owners and message policy are known. Copy this block into a document, spreadsheet, CRM note or approved workflow tool. Replace every label, then save the reviewed version with its owner, version and review date.

Field guidance

  • Define eligibility from an observable inbound event and record its source ID, time and permission state.
  • List exclusions before actions so duplicates, suppressed records and active cases never enter silently.
  • Keep acknowledgement, assignment and owner acceptance as separate events.
  • Limit the first question to one answer that changes the route; bind any answer to approved sources.
  • Make every exit write a final state and cancel pending work.

HubSpot's workflow documentation separates enrollment, actions, branches, testing, re-enrollment and unenrollment. Learn that explicit lifecycle; do not assume the same feature names, limits or availability in another product. Review the workflow mechanism.

Fictional filled example: website consultation request

Template name: Website consultation intake
What starts it: New form submission with contact permission and service interest
Do not start when: Duplicate, test, existing open service case, do-not-contact flag, or missing contact route
Information needed: Source ID, received time, name, contact route, service interest, market, permission state
Checks before contact: Do-not-contact, bounced address, withdrawn permission, active owner conflict

Step 1 — capture
- What to record or update: Create a lead or attach the submission to the existing lead
- Source ID, date and time: Preserve source ID and the 10:02 received time
- If recording fails: Put it on the intake exception list; do not start messages

Step 2 — acknowledge
- Message: “We received request L-1842 about [service]. A team member is reviewing it. Next update by 10:20.”
- Expectation the team can keep: Next update only; no qualification or availability promise

Step 3 — assign and accept
- How to choose the owner: Market + service line; otherwise use the general consultation list
- Primary owner and backup: Selected salesperson; sales lead is backup
- Time allowed to accept: Team-approved 8 minutes during covered hours

Step 4 — useful follow-up
- One question that changes the next route: “Which current step creates the most delay: new enquiries, qualification, follow-up, or handoff?”
- Approved sources for the answer: Current approved service descriptions only

Stop immediately when: Reply received, person requested, owner changes route, do-not-contact appears, address is invalid, or two deliveries fail
If nobody accepts: Preserve the request, notify the backup, and make no unsupported promise
What proves completion: Accepted owner, useful question or approved answer sent, and next action recorded
Who reviews it and when: Revenue operations reviews exceptions and a response sample weekly

The timeout is an illustrative operating choice, not a benchmark. Replace it with a target based on coverage and baseline.

Quality checklist

  • The trigger records permission and original source time.
  • Acknowledgement is not counted as human acceptance.
  • One current owner and backup are visible.
  • Every message changes the decision or expectation.
  • Replies, opt-out, invalid contact, duplicate, and delivery failure stop the sequence.
  • Material product, price, timing, or availability claims use an approved source.

Common mistakes

Mistake Safer correction
Counting an acknowledgement as accepted ownership Store acknowledgement and owner acceptance separately.
Starting with missing source or permission data Route the record to an exception queue before messaging.
Promising a response the team cannot staff Use an owner-approved expectation tied to covered hours.
Continuing after a reply or route change Cancel pending actions and record the new state.

What to do next

Use the first-five-minute response clock to baseline every event before activating the workflow.

Evidence and limitations

This is a platform-neutral template. It does not prove an integration, conversion uplift, legal compliance, or an Easy AI feature.

FAQ

Recommended for you