An agency lead workflow needs a reliable capture record, one response owner, a qualification decision and a visible next action. Start by defining what happens after an inquiry reaches your team. Keep sales judgment with a person, and use automation to make missing information, overdue responses and failed handoffs easier to see.
- Capture inquiryKeep original wording and key details.
- Assign response ownerTreat it as work to resolve.
- Make qualification decisionCheck fit and missing information.
- Record next actionShow the last response and decision.
Flag missing fields for review instead of supplying a guess.
What should happen after an inquiry arrives?
Treat a new inquiry as an item someone must resolve, rather than a notification everyone can see. A website form, referral email and direct message may enter through different tools, but each needs a recognizable record. At minimum, record the contact, company, inquiry source, arrival time, requested service and person responsible for responding.
Keep the prospect's original wording. A summary can help the next person scan the request, but it should not replace the source message. If a field is missing, flag it for review rather than filling it with a guess. A referral that arrives with only an introduction still needs an owner.
Build a small status model
Use statuses that describe decisions your team understands. A record should move because something happened, not because an automated timer changed its label.
- NewAssign a response owner.
- ReviewingRespond or ask a specific question.
- Waiting on prospectSet a review date.
- ClosedRecord reason and stop reminders.
A record should move because something happened, not because a timer changed it.
| Status | What it means | Required next step |
|---|---|---|
| New | Inquiry captured; no response decision yet | Assign a response owner |
| Reviewing | Owner is checking fit and missing information | Respond or ask a specific question |
| Conversation booked | Prospect accepted a meeting | Record meeting details and preparation |
| Waiting on prospect | A response was sent; reply is pending | Set a review date |
| Closed | Inquiry was declined, withdrawn or converted | Record the reason and stop reminders |
You can use another vocabulary. The important part is agreement about who can change a status and what evidence supports the change.
Decide what the first response should accomplish
The first response should acknowledge the actual request and give a clear next step. An automated receipt can confirm delivery. It cannot establish that the prospect is a good fit or that your agency can deliver the requested work.
- Automated receiptConfirms delivery only.
- Sales responseAddresses request or asks qualification question.
- Relevant next stepChoose based on actual inquiry.
- Response recordRecord what was sent.
A receipt does not establish fit or delivery capability.
For example, an inquiry about a campaign launch may be missing the launch date and budget context. The owner can ask for those details before offering a meeting. A referral with a detailed brief may move directly to a conversation. Both routes belong in the same workflow, but they require different judgment.
Create a short response checklist: confirm the service requested, check whether another team member is already speaking with the prospect, choose the next step, and record what was sent. Set response expectations your team can actually meet.
Make follow-up conditional
A reminder should stop when the prospect replies, declines or becomes a client. Otherwise, a helpful workflow becomes an awkward sequence of messages after the conversation has already moved forward.
- Current next actionUse one authoritative field.
- Reply or declineStop the reminder sequence.
- Ambiguous caseCreate a review task.
- Owner judgmentFollow up, close, or wait.
Do not let an old status repeatedly trigger the same message.
Use a review task when the next action needs judgment. For a stalled inquiry, the owner may choose to send a brief follow-up, close the record or wait because the prospect supplied a later decision date. Do not let an old status repeatedly trigger the same message.
Keep one authoritative next-action field. If the CRM and a spreadsheet both hold different dates, your team will struggle to know which instruction to follow.
Test the inconvenient cases
Before enabling automatic assignment or reminders, try a duplicate submission, a referral without an email address, an inquiry from an existing client, an owner who is unavailable, and a prospect who replies after the record closes. Write down how each case is handled.
A useful completion test is simple: can someone open a lead record and identify the owner, the last meaningful response and the next decision without searching several inboxes? Measure unresolved records and missed handoffs first. A larger lead count does not tell you whether the process works.
For the broader decision about which workflow deserves attention, use the first automation guide.
Questions and answers
Should every agency inquiry enter the CRM?
Every inquiry needs a reliable record and an owner. Whether that record belongs in your CRM depends on your setup. If inquiries first arrive in an inbox, define when they become CRM records and how you prevent a request from being lost in between.
Can an automated receipt count as a sales response?
A receipt confirms delivery. A useful sales response addresses the request or asks a relevant qualification question. Track those separately so a fast automatic message does not hide an inquiry that nobody has reviewed.
How do we avoid following up after a prospect replies?
Use the reply or updated status as a stop condition, and have an owner review ambiguous cases. Test the stop condition before enabling a sequence. A reminder should depend on the current record, not just the date the inquiry first arrived.