Follow-Up Systems LabWorkflow objective
When a legitimate new inquiry arrives, create a reliable record, acknowledge the lead, assign ownership, make the next step clear and keep following up appropriately until the state changes. The workflow should never continue blindly after a reply, booking, opt-out or closed outcome.
Entry requirements
- Known lead source and timestamp
- Usable contact method
- Required consent/context for the planned communication channel
- Rule for duplicate contacts or repeat inquiries
- Routing fields such as service, location or request type if needed
Workflow specification
Trigger: new inquiry
A supported form, ad lead, inbound event or integration creates/updates the contact.
Create CRM context
Set source, owner and initial opportunity state. Preserve the original event rather than overwriting history.
Immediate acknowledgement
Confirm receipt and tell the person what happens next. Do not imply a human has responded if they have not.
Internal assignment
Notify or task the owner. Escalate if the lead remains unowned beyond the team's internal standard.
Early follow-up
Use the expected channel and a limited sequence while the original intent is current.
Branch on engagement
Reply, booking or qualification moves the contact to a different path and stops generic messages.
Close or nurture
At the end of active pursuit, mark the state accurately and move eligible leads to a lower-frequency nurture or future reactivation segment.
Test cases before launch
| Test | Expected result |
|---|---|
| New unique lead | One contact, one appropriate opportunity, acknowledgement and owner task. |
| Existing contact submits again | Defined update/reopen behavior; no accidental duplicate cascade. |
| Lead replies immediately | Generic follow-up stops. |
| Lead books | Appointment sequence begins and pre-booking prompts stop. |
| Lead opts out | Channel-specific automated messaging stops as required. |
| Invalid contact data | Workflow surfaces the failure for human review rather than silently continuing. |
What to monitor
Measure acknowledgement delivery, owner assignment, meaningful first response, booking/reply state and workflow exits. Do not judge the system only by how many messages it sent.
Sources & verification
Product and pricing details can change. These first-party sources were checked on October 1, 2026.