A simple follow-up system gives every enquiry a record, an owner and a next action. It helps your team know whom to call, why they are calling and when the customer expected to hear from you. The tool can be modest; the working habits must be clear.
For a small business, a shared Google Sheet can be a useful starting point. It should capture website enquiries reliably, preserve phone numbers and record the received date and time. The team then adds conversation notes, status and the next follow-up. A sheet alone does not make calls happen, so ownership is essential.
Start with the minimum useful lead record
Record the customer's name and callback number, the business or requirement, the source and the received timestamp. Add a unique lead ID so a record can be referred to without confusion. For website enquiries, capture the page and form name to preserve context.
Separate the received time from the last contacted time. The first tells you when the opportunity arrived; the second tells you what the team did. A preferred callback time is a customer preference, not proof that a callback was completed.
Store phone numbers as text so a spreadsheet does not remove a plus sign or leading digit. Keep the original useful information and a normalised version for call links where needed. Restrict access to the people handling enquiries.
Choose a small set of statuses
A practical starting set is New, Contacted, Follow-up, Qualified, Won, Lost and Invalid. Define what each means. “Contacted” should reflect an actual contact attempt or conversation according to your agreed rule, not merely assigning the row to someone.
Use notes to explain the context rather than creating a new status for every situation. A customer waiting for a family decision can remain in Follow-up with an agreed review date. A wrong number can be Invalid with a short reason.
If you need to distinguish attempts from conversations, add a dedicated field later. Start with definitions the team can maintain accurately.
Assign one person to the next action
A lead may involve several team members, but the next action should have one clear owner. “Sales team” is not enough if everyone assumes another person will call. Use a name or an agreed role with a known person responsible that day.
When ownership changes, include a short handover: what the customer needs, what was promised and what should happen next. Avoid forcing the customer to repeat the same information to each new person.
Plan for absence. A backup person should be able to find open enquiries and understand the next action without relying on private messages or memory.
Let the customer influence the timing
Ask when a callback is convenient. If the customer offers a time window, record it clearly with the relevant timezone. For an India-focused team, IST can be the default, but international requests need explicit clarification.
Agree on the next contact after a meaningful conversation. The right interval depends on the purchase, urgency and customer preference. A same-day appointment and a long-term project should not receive an identical sequence.
Do not continue contacting someone who declines or asks you to stop. A follow-up system should make communication more relevant, not more persistent without purpose.
Make each follow-up useful
Before calling or messaging, read the last note. Prepare the answer or information that moves the conversation forward. A useful follow-up might clarify a quotation, confirm a date, provide a relevant example or ask whether the requirement has changed.
Keep the message tied to the previous discussion. “You asked about a weekend appointment; here are the available options” gives the customer context. Repeated generic reminders can feel disconnected from their need.
If there is no response, use a reasonable, limited approach based on the relationship and channel. Record the attempt and decide whether another contact is appropriate. Do not confuse repeated attempts with progress.
Illustrative example: a missed callback
Imagine a fictional clinic receiving a website request late in the evening. The form saves the customer's number, preferred callback time and received timestamp. The next morning, a designated staff member filters for New enquiries and calls within the customer's requested window where feasible.
After the conversation, the staff member updates the status and records the agreed next step. If the customer wants to check availability later, the next follow-up date is set. If the request is resolved, the record is closed appropriately.
The value of this example is the visible handover. It does not imply a guaranteed response speed or any specific improvement in bookings.
| Field | Purpose | Who updates it |
|---|---|---|
| Received timestamp | Shows when the enquiry arrived | Submission system |
| Mobile number | Enables a callback | Customer, then team if corrected |
| Help required | Preserves the original need | Customer |
| Assigned to | Names the next-action owner | Team |
| Last contacted at | Records actual activity | Team |
| Next follow-up at | Creates a clear reminder | Team |
| Call notes | Preserves useful context | Team |
Build a short daily routine
At the start of the working day, review new enquiries and overdue follow-ups. Assign any unowned records. Prioritise based on the customer's stated urgency and the business's ability to help, rather than only on the order in which staff notice the messages.
During the day, update records after conversations. A short factual note is usually more useful than a long transcript. Record the next action before moving to another task.
At the end of the day, check that promised callbacks and proposals have a clear status. If something cannot be completed, update the plan and communicate appropriately. The routine should make work visible without turning record-keeping into the main job.
Handle duplicate and repeated enquiries correctly
A customer may click submit twice because the network is slow. The website should use a stable submission ID so retrying the same request does not create duplicate rows. A later, genuinely new enquiry should still be allowed.
The team may also receive the same person's request through a call and a form. Link the context when it is clearly the same opportunity, while preserving useful source information. Do not automatically merge unrelated requests merely because the number is the same.
If the system cannot confirm a save, the customer should see an honest message and retain their entered details. A success screen is not appropriate when the request was only redirected to WhatsApp or when the backend failed.
Know when a spreadsheet is no longer enough
A spreadsheet can become difficult when many people edit at once, different teams need different access or reminders and conversation history are spread across tools. Those are reasons to evaluate a CRM or a more integrated workflow.
Before migrating, document the current fields, statuses and working rules. A new tool should support a process the team understands. Importing unclear records into a more expensive system rarely resolves the underlying confusion.
Pilot with a small group and confirm that the new workflow is easier to maintain. Keep a backup and a clear plan for which system becomes the source of truth.
A weekly quality check
Sample a manageable number of records and check whether the status matches the notes. Look for missing owners, old follow-up dates, incomplete numbers and open enquiries with no next step. Correct the process that produced the gap, not only the individual row.
Review whether the information being collected is actually used. If an optional field never helps the team respond, consider removing it. If the same essential question is asked on every callback, consider adding a short, clear field to the form.
Keep the sheet private. Avoid public sharing links and unnecessary exports of customer details. Make responsibility for access and maintenance explicit as the team changes.
Common questions
Should calls happen automatically after form submission?
That requires a separate calling system and a suitable customer communication process. A saved lead and a call link do not place a call automatically. Start with a reliable human callback workflow.
What time should the sheet record?
Use an authoritative server timestamp and display it in the team's operating timezone, such as Asia/Kolkata. Keep a separate field for the time the team actually contacted the customer.
What should we automate first?
Capture, assignment reminders and overdue follow-up views are practical candidates. Read when to use automation and why leads do not convert before expanding the workflow.
Apply this to your business.
Tell us where you are getting stuck. We can discuss a practical next step.