A reliable client follow-up process gives each opportunity one owner, a specific next action and a date. Record the last conversation and what the client needs to decide. Review overdue actions, then close or pause opportunities when there is no agreed next step. Email and WhatsApp can carry the conversation; a shared record keeps the commitment visible.
This guide is for Indian professional services firms, including chartered accountants, company secretaries, law firms, IT services companies, agencies and consultancies. It covers enquiries and proposals for new work. Follow-up on an existing engagement belongs with its delivery record; collecting an overdue invoice needs a separate receivables process.
What to record before sending another message
Keep the opportunity record small enough to maintain. These fields answer the questions a colleague needs to pick up the conversation:
- Client and engagement: the organisation, contact and service being discussed.
- Stage and last interaction: what has actually happened, with a dated note or link to the relevant exchange.
- Owner: one person accountable for the next action, even if someone else makes the call.
- Decision needed: the question, missing input or approval holding up progress.
- Next action and date: a specific task and when it is due.
- Outcome: the reply, new commitment, reason for pausing or reason for closing.
For a broader field list, see CRM fields for professional services. Keep sensitive documents in the appropriate access-controlled location, and link to them rather than copying them into every note.
A six-step client follow-up process
1. Agree the next step during the conversation
Before ending a call, ask what the client needs to decide and when it is useful to reconnect. “I will send the revised scope on Tuesday, then call on Thursday after you have reviewed it” is actionable. “We will stay in touch” is not.
2. Assign one owner and record the commitment
Log the note while the context is fresh. Separate your task from the client's task. If you promised a revised fee schedule, send it before asking for a decision. If a partner must answer a question, assign that internal action instead of repeatedly nudging the client.
3. Follow up on the decision, not just the proposal
Make each message useful: answer a question, provide the agreed information or ask for a specific decision. Mention the service or deliverable so the recipient can place the conversation. Avoid repeating “just checking in” without new context.
4. Set the next date from the response
Choose timing from the client's stated review date, urgency and preferred channel. There is no universal sequence that suits every engagement. If the client asks you to reconnect after a board meeting, record that date. If no date is agreed, set an internal review point and decide whether another message is appropriate.
5. Review overdue actions and blockers together
At a regular pipeline review, ask which actions are overdue, who owns them and what is preventing progress. Resolve internal blockers before increasing the number of client messages. A stage such as “proposal sent” should describe the situation, not hide the absence of a next step.
6. Confirm, pause or close the opportunity
Record the actual outcome. A verbal expression of interest is not the same as an agreed engagement. When the work is confirmed under your firm's process, prepare a client project handoff. If timing has changed, pause with an agreed review date. If the client declines or asks you to stop, close the opportunity and respect that request.
A copyable client follow-up record
Use this structure in a shared working record or your CRM. It is an operating checklist, not a requirement to add every line as a custom software field.
CLIENT FOLLOW-UP RECORD
Client / engagement:
Contact and preferred channel:
Opportunity stage:
Owner:
Last interaction (date and record link):
Decision / information needed:
Our promised action and due date:
Client's agreed next step, if any:
Next follow-up action and date:
Internal blocker and owner:
Latest response / outcome:
Pause or close reason, if applicable:
Next review date, if agreed:
A worked example: a proposal awaiting a scope decision
Illustrative example: the client and people below are fictional. This is a sample process, not a Workplate customer result.
| Point in the process | What the owner records or does |
|---|---|
| Context | Northstar Services is considering a website audit. Meera owns the opportunity. The proposal covers five pages; the client asks whether two more pages can be included. |
| Monday conversation | The client will review internally on Thursday. Meera promises a revised scope and fee schedule on Tuesday, with a follow-up on Friday. |
| Internal action | Arun confirms the delivery effort before Meera sends the revision. If that input is delayed, Meera tells the client and agrees a new review date. |
| Tuesday update | Meera sends the revised proposal and links its current version in the opportunity record. The next task is to ask for the scope decision on Friday. |
| Friday response | The client says the internal review has moved to next week and asks for a call the following Tuesday. Meera records the response and changes the next-action date. |
| If there is no response | Meera reviews whether a further message would help. She can offer to pause, rather than mark the opportunity won or continue an indefinite daily chase. |
| When work is confirmed | Record the agreed scope and commercial terms under the firm's acceptance process, then hand delivery an owner, deadline and current documents. |
Sample messages that give the client a clear next step
Adapt these examples to the conversation. They are drafts for a person to review and send, not an automated campaign.
After sending agreed information
Hi [name], I have sent the revised scope covering the seven pages we discussed. Is there anything else you need for Thursday's review? I will reconnect on Friday as agreed.
When a decision is still pending
Hi [name], were you able to review the website audit scope? If a question is holding up the decision, let me know and I will help resolve it. Has your review date changed?
When it is better to pause
Hi [name], is this engagement still a priority? If the timing has changed, we can pause the proposal. Let me know whether there is a suitable date to reconnect.
Use the channel the client expects. Avoid sending the same nudge across several channels at once. A request to stop should end the chase.
Use Workplate CRM to keep the next action visible
Workplate CRM provides deal ownership, custom pipeline stages, tasks and reminders, and activity records for notes, calls and meetings. Use the opportunity to hold the current context, a task to name the next action and due date, and the activity record to capture the outcome. Update the record after the interaction.
The copyable record above describes a team process. It does not promise automatic WhatsApp or email capture, automatic message sending, or an automatic transfer into Projects. AI Chat can work with CRM, Projects, eSign and Invoice information, but the team still needs to record decisions and keep commitments current.
When the next action is a call
Workplate Voice provides configured agents for callbacks and outbound follow-ups. Its Workplate CRM integration can add call summaries, captured answers and follow-up actions to the lead record. Use it for a clearly defined conversation and review the outcome before deciding the next step.
Start with the open proposals you already have
Review each active proposal. Name its owner, record the decision needed and set the next action. Separate opportunities with a real next step from those that should be paused or closed. This gives a colleague a record they can act on and gives the client a useful conversation instead of another vague reminder.