Start with one rule: every active lead needs an owner, useful context and a dated next action. Automate repetitive reminders only after defining when they stop, including when someone replies or declines.
1. Find enquiries with no next action
A lead is a person or business that has expressed interest in a service. A new enquiry is not automatically an appointment, a quote or a sale. Someone needs to understand the request and help the person take the next step.
Review your recent enquiries and ask three questions: who owns this request, what was the last response and what should happen next? “Follow up” is too vague. “Call tomorrow morning to confirm the service area” gives someone an actionable task.
Separate potential sales from support requests, supplier messages and duplicates. If a person calls after submitting a form, attach the conversation to the existing enquiry instead of starting two independent follow-up sequences.
2. Keep the source and the actual need
A useful record includes necessary contact details, the incoming channel, the requested service, the area, the requested timing and the latest conversation. The source might be a website form, a call or a referral. If you do not know it, mark it as unknown rather than inventing an attribution.
Distinguish the communication channel from how the person discovered you. Someone may read an article, return to your site later and call. The phone is the contact channel; the article may be a declared or observed source, depending on the information you actually have.
For website forms, arrange to retain the landing page, relevant article and campaign parameters when available. Check that these details reach the CRM. Do not make visitors fill out a long questionnaire to compensate for an incomplete technical setup.
3. Assign an owner and a backup
Give each enquiry one owner. In a small team, this could be the person answering the phone. Other businesses may assign requests by service or territory. The owner coordinates the follow-up even when a technician needs to answer a specific question.
Decide what happens during absences. A designated person should review the unassigned queue. Sending a notification to everyone is not the same as assigning responsibility.
Choose a review routine that fits your opening hours and service commitments. An acknowledgement should describe a realistic next step, without promising an immediate response your team cannot provide.
4. Qualify the enquiry before proposing a next step
Ask questions that affect what happens next: do you provide the requested service? Is the address in your service area? What timing does the person have in mind? What information is missing before you can arrange a call or a visit?
For an HVAC enquiry, you might distinguish maintenance, replacement and installation, then ask for the area and intended timeframe. Urgent or technically sensitive requests should go to a qualified person. An automated message does not replace an assessment.
Use clear stages: new enquiry, information needed, appointment offered, appointment confirmed, quote sent, won, lost or project postponed. The stage describes the situation; the task explains what the team needs to do.
5. Give every next action a due date
After each conversation, record the next action, its owner and its date. If a person asks you to call next month, respect that timing rather than continuing a standard sequence.
The following fictional tracking table illustrates an approach. Its timing is an operational example, not a universal cadence or a promise of results. Adjust it to the request and the agreed availability.
| Source | Need | Owner | Stage | Next action | Due |
|---|---|---|---|---|---|
| Website form | HVAC maintenance | Coordinator | To qualify | Confirm area and equipment | Next business window |
| Phone call | Replacement | Advisor | Appointment offered | Confirm chosen availability | Agreed date |
| Referral | Postponed project | Advisor | On hold | Reconnect if agreed | Requested period |
Once the appointment is confirmed, remove the reminder that is no longer needed. If the request is outside your offering, explain that clearly and close the sales follow-up instead of keeping an artificially active opportunity.
6. Write messages that move the conversation forward
Each message should refer to the actual request and ask one useful question. These are illustrative templates: replace the bracketed details and read the latest conversation before using them.
Acknowledge a request
Hi [first name], we received your request for [service] in [area]. [Owner] will review it during [realistic time window]. What timeframe do you have in mind for this project?
Complete missing information
Hi [first name], we need [specific detail] to help with your [service] request. Could you confirm it? We can then suggest the next step.
Follow up on an unanswered conversation
Hi [first name], I’m following up about [project]. Would you like to move ahead now, revisit it later or close the request? I’ll update your file based on your preference.
Confirm a postponement
Thanks for letting us know. I’ve noted that the project is postponed until [agreed period], and we’re pausing the current follow-up. Would you like [owner] to contact you then?
7. Automate reminders with clear stop conditions
Start with internal tasks: notify the owner when a request arrives, remind them of an overdue action and flag records without an owner. Add automated messages once the manual process is clear.
Before sending, check the enquiry’s status, communication preferences and any replies received since the message was scheduled. A reply should pause the relevant sequence and return the conversation to a person. A refusal, stop request, confirmed booking or closed record should also stop reminders that no longer apply.
Avoid restarting the same sequence repeatedly when a stage changes. Test duplicate enquiries, ownership changes and replies received just before a scheduled message. Available channels and conditions depend on your configured integrations; verify them in your account before enabling a workflow.
8. Measure useful enquiries, not just forms
Separate form opens, successfully received enquiries, qualified leads, attended appointments and sales. Clicking Submit proves neither that the CRM received the enquiry nor that it is a good commercial fit.
To assess an article’s contribution, preserve its source information when available and compare it with the lead’s progress in the CRM. Do not force an attribution when the source is unknown. A conversation may start on one device and continue on another.
In your team review, look at unassigned enquiries, overdue actions, outstanding replies and reasons for lost opportunities. For any rate, define the group and period: for example, attended appointments among qualified enquiries received during a particular period. With only a few records, inspect individual cases before drawing a trend.
9. Put the process into practice with Ocliq
Ocliq presents lead centralization, pipelines, conversations, tasks and follow-up capabilities. The configuration should reflect your operation: channels actually connected, owners, stages and exit rules.
For a useful demonstration, bring an anonymized scenario: an enquiry arrives, information is missing, an appointment is offered, and the person replies or postpones the project. Check each transition and whether context is retained. Do not assume an integration or automation is already enabled.
Start with one service and a few stages. Verify that the team uses next actions consistently, then expand the setup. A CRM helps organize the work; it does not replace team availability or the quality of its responses.
Explore further
Frequently asked questions
Can a spreadsheet be enough to start?
Yes, if the volume is manageable and someone keeps owners, due dates and conversation notes up to date. A CRM becomes useful when multiple people, channels and follow-ups make that coordination difficult.
How many follow-up messages should we send?
No single number fits every enquiry. Consider the need, previous conversations and stated preferences. Set a limit, a next action and stop conditions instead of following up indefinitely.
Should every response be automated?
No. Simple reminders can be automated after validation. Objections, urgent situations, complex enquiries and commercial decisions should be handled by a person.
How can we tell whether an article generates leads?
Keep available source information when the enquiry arrives, then track qualification and outcomes in the CRM. Separate those outcomes from visits and clicks. An unknown source should remain unknown.
Every enquiry should have a next action.
See how to centralize incoming requests and organize follow-ups around your actual process.