- ReceivedRead the actual request.
- AssignedGive one person responsibility.
- AnsweredResolve the customer’s immediate question.
- Next step agreedRecord the action and due date.
- Outcome recordedKeep won, unsuitable and inactive distinct.
Start with the customer’s immediate question
Before designing stages or reminders, read the inquiry as a customer would. What are they trying to arrange? What uncertainty do they need you to resolve? What information have they already given you?
A person asking whether you cover their location needs a direct answer about coverage. A person requesting a quotation may need a short discovery conversation before you can price the work. Someone with a broken service may need an availability answer before any marketing discussion matters.
If your first response ignores those questions and repeats a generic sales introduction, you create another task for the customer. They have to explain the same problem again.
Keep a short inquiry summary in your record. For example: “Office manager needs a monthly maintenance arrangement for two premises; asks whether an initial visit is available next month.” This is an illustrative example, not a Rattle client result. The summary preserves the request while allowing another colleague to understand the next action quickly.
Avoid adding assumptions such as “urgent buyer” or “large budget” unless the customer has supplied evidence. A useful record separates what they said from what you still need to find out.
Choose one place to see the status
Your website form, shared inbox and CRM can all play a role. Decide which place your team will use to answer one question: what is happening with this inquiry now?
It might be your existing CRM, a shared inbox with agreed labels or a simple access-controlled spreadsheet. Choose the smallest system your team can maintain. If you already have a free CRM that stores the form submissions, start there before buying another tool.
Do not assume a new system will repair missing ownership. A request can disappear inside expensive software just as easily as it can disappear inside an inbox.
Record enough information to support the conversation:
- The date the inquiry arrived and its source, when known.
- The customer’s stated requirement and preferred contact method.
- The person responsible for responding.
- The current stage and the next action.
- The date that action is due.
- The eventual outcome and a short reason.
Use references to the existing conversation instead of copying the entire message into several tools. Limit access to colleagues who need the information. Avoid putting private customer details into public planning documents or screenshots.
Define stages around actions your team can recognize
Stages should describe real progress. “Hot”, “warm” and “interesting” mean different things to different people. “Awaiting site details” tells a colleague what is missing.
| Stage | What it means | Next action |
|---|---|---|
| New | Received but not reviewed | Assign an owner and read the request |
| Clarification needed | Important information is missing | Ask focused questions |
| Suitable inquiry | Requirement appears to fit the service | Agree a call, visit or quotation step |
| Proposal sent | A specific proposal has been shared | Record an agreed follow-up date |
| Awaiting customer | The customer has the next action | Keep an appropriate reminder |
| Closed | Won, declined, unsuitable or no longer active | Record the outcome and reason |
Adapt these stages to your work. A business that books appointments may not need a proposal stage. A project business may need a separate assessment stage. Each stage should make the next action clearer.
Do not label a request “qualified” simply because someone filled in a form. Agree the requirements that make it suitable for your service. Our guide to what counts as a qualified lead explains that distinction in more detail.
Give each inquiry a named owner
A shared notification is not ownership. If three people receive the same email, each can reasonably assume someone else has answered it.
Choose a primary owner and a backup arrangement. For a small team, one person might review new inquiries during the working day and pass specialist requests to the relevant colleague. For a solo business, the same person owns every request, but a daily review window still helps.
When ownership changes, record the handover. Include what the customer needs, what has already been promised and the next action. A silent forward with “please handle” leaves too much room for misunderstanding.
If you cannot meet a request, close the loop clearly. An unsuitable location or service requirement is still a real customer question. A concise answer is more useful than a message left indefinitely in a new-inquiry queue.
Set a response expectation you can actually maintain
There is no single response time that suits every service business. An emergency repair service and a long-term consultancy have different customer expectations and working arrangements.
Choose your own response standard based on your delivery capacity, opening hours and the promise made on the website. If the form says your team will reply within a stated period, the operating process needs to support that statement.
Distinguish an acknowledgement from a useful answer. An automatic message can confirm receipt. It does not mean someone has reviewed the requirement or confirmed availability.
An acknowledgement should tell the customer what happens next, give an honest response expectation and provide an alternative route if one is appropriate. Avoid implying that a booking or project has been accepted merely because the form was submitted.
Check the practical edge cases: weekends, holidays, absent colleagues and requests received near closing time. A standard that only works on a quiet Tuesday is not a reliable standard.
Ask for the missing information in one useful message
Read the original form before requesting details. If the customer already provided their location and service requirement, do not ask for them again.
Ask only for information that changes the next decision. That may include the site location, the type of service required, an approximate timescale or whether the inquiry concerns an existing arrangement.
Make the reason clear. “Could you confirm the postcode so we can check whether we cover your area?” is easier to answer than “Please supply further details.”
Group related questions into one message where possible. Keep the number manageable. If a complex project requires a longer discussion, offer a suitable call or discovery step rather than sending a questionnaire that nobody wants to complete on a phone.
Sensitive documents should use an appropriate agreed channel. An initial inquiry is rarely the right place to request every account credential, financial record or customer list.
Make the next step specific
“Let us know” can be too vague when the customer expects guidance. State the proposed next action and what it is for.
For example, an initial assessment call might confirm scope and decide whether a quotation is possible. A site visit might establish access and delivery requirements. A written estimate might explain what is included and what remains provisional.
Tell the customer what they need to prepare, if anything. If the next step does not require preparation, say so briefly. Remove unnecessary work from the journey.
Where you offer times, use the customer’s relevant time zone and avoid assuming availability. Where a colleague will make contact, identify the role or person and provide enough context for the customer to recognize the message.
Do not promise a result before you understand the work. A clear next step can be reassuring without becoming a guarantee.
Follow up according to the conversation
Follow-up works best when it refers to an agreed action or an unanswered question. It becomes less useful when every customer receives an identical sequence regardless of what they said.
If the customer asked for information, send that information before prompting them to book a call. If they said the project is on hold, record the timing instead of repeatedly requesting a decision. If they declined, respect the decision and close the inquiry.
For an unanswered proposal, a follow-up can check whether the customer needs clarification and whether the timing has changed. Keep it concise and easy to answer. Avoid guilt, invented scarcity or claims that an offer will disappear unless that is genuinely true and relevant.
Set a reasonable closing point for inactive inquiries. Your team needs to know when to stop carrying a conversation as an active opportunity. Record “no response after agreed follow-up” separately from “service not suitable” because those outcomes suggest different improvements.
Keep automation small and visible
A free account may allow only limited workflow actions. That does not prevent a consistent process. Use available reminders, saved views or an acknowledgement where they help, and support the rest with a clear manual routine.
Before enabling an automation, write down its trigger, action and owner. Check what happens if the customer submits again, replies by email or is already an existing contact. Test with an authorized internal example rather than a real customer’s private information.
Do not assume an automation ran because its setting is switched on. Check the resulting record or notification. If a free plan cannot perform a needed action, record the limitation and choose a workable manual step.
Automate repeatable administration first. Keep decisions about suitability, promises and sensitive information with someone who understands the request.
Review a few meaningful numbers
Start with measures that reveal where the process breaks. More inquiries do not automatically mean more suitable work.
| Measure | What it helps you understand | Important limit |
|---|---|---|
| Inquiries received | The volume reaching the business | Exclude known tests and duplicates consistently |
| Inquiries assigned | Whether requests have an owner | Assignment is not a response |
| Time to first useful reply | How quickly the customer gets relevant help | An automatic acknowledgement is different |
| Suitable inquiries | Whether requests fit your service | Use an agreed definition |
| Next steps agreed | Whether conversations move forward | A booked call is not a won project |
| Outcomes and reasons | Where opportunities end | Small samples can be misleading |
Use the same definitions each review period. A change in how you count suitable inquiries can look like an improvement even when customer demand has not changed.
If you are comparing marketing sources, keep unknown sources visible. Do not allocate every unattributed request to the channel you prefer. Our marketing report review guide explains how to connect numbers to practical decisions.
Improve the website from repeated questions
Inquiry handling can reveal missing website information. If customers repeatedly ask whether you cover an area, your coverage explanation may be unclear. If they repeatedly expect a service you do not offer, the service page or advert may need attention.
Record themes rather than publishing individual conversations. Then choose a specific improvement: clarify a service boundary, explain an assessment step, add a practical FAQ or change a misleading call to action.
Keep form friction in perspective. A long form can reduce irrelevant requests but also discourage suitable customers. A short form can be convenient but leave your team needing more clarification. Review the quality of the conversations alongside completion numbers before changing the fields.
When a customer says they received no confirmation, verify the form journey. A follow-up process cannot recover a request that never reached your business. The conversion tracking service can help define what your website should measure, while your team verifies receipt and outcomes.
A practical routine for a small team
At the start of the working day, review new and overdue inquiries. Assign owners, send useful responses and update the next action. Check again at a time that fits your delivery schedule.
Once a week, review requests without owners, proposals waiting for a response and records without an outcome. Look for repeated customer questions and process failures. A short review of specific exceptions is often more useful than a long meeting about every inquiry.
Once a month, compare inquiry volume, suitability and outcomes using stable definitions. Choose one improvement, give it an owner and check whether it helped. You do not need to change the form, website, adverts and follow-up process all at once.
Frequently asked questions
Do we need a paid CRM to follow up website inquiries?
Not necessarily. An existing free CRM, a shared inbox or a controlled spreadsheet can support a simple process. The important requirements are ownership, a visible next action and a record your team can maintain. Check the actual limits of your account before relying on automation.
Should every inquiry receive an automatic reply?
An acknowledgement can be useful when it accurately confirms receipt and explains what happens next. It should not imply that someone has reviewed the request or accepted the work. Verify that it is sent as expected and does not conflict with a personal response.
How many follow-ups should we send?
There is no universal number. Follow the customer’s stated timing, the context of the request and any agreed next step. Establish a reasonable stopping point, honour requests to stop and distinguish inactive conversations from active opportunities.
What if two colleagues reply to the same inquiry?
Give the record one owner and make assignment visible. Use a shared conversation or record where possible. When ownership changes, include the customer requirement and the action already promised.
What should we change first if inquiries are being missed?
Confirm that submissions reach the business, then check assignment and overdue actions. Fix the earliest broken step before adding more reminders or buying more software.
Make the website and follow-up process work together
The form is the beginning of a conversation. A clear service page, reliable submission and useful first reply should all lead towards the same next step.
