How do you organise customer follow-up?
To organise customer follow-up, give every enquiry one record with an owner, a stage and a dated next action. Agree four to six stages, log each quote with its send date, set a rule for when to chase, and review stale records weekly. A CRM such as Odoo CRM enforces this and keeps the history in one place.
Where follow-up breaks in a typical sales team
Think about how enquiries arrive: a WhatsApp message to one salesperson, a website form, a phone call, an email to a shared inbox. Each lands somewhere different. A quote goes out as a PDF in a chat. Three days later nobody remembers who promised to call. When the salesperson goes on leave, their conversations leave with them.
The fix is one record per enquiry holding the contact, the need, the quote, the owner and the next step, whatever the source.
Step 1: name your stages
List the steps an enquiry passes through between arrival and a decision, using words your team already says aloud. A common set:
| Stage | Meaning | Exit rule |
|---|---|---|
| New | Enquiry received, nobody has replied | A salesperson makes first contact |
| Qualified | Need, budget range and decision maker are known | Requirements are clear enough to quote |
| Quote sent | A quotation has gone out | Customer replies or the follow-up date arrives |
| Negotiation | Scope or terms are being discussed | Customer accepts or declines |
| Won or lost | A decision was made | Reason recorded |
Add a stage only when staff know exactly when a record enters it. A short list used identically by everyone beats a long one each person reads differently.
Step 2: decide what to record
Keep what the next person needs to continue the conversation:
- Contact name, company and preferred channel: WhatsApp, phone or email.
- Source: website form, referral, ad, exhibition or walk-in.
- The need in a sentence or two, in the customer’s words.
- The quote: date sent, file or link, validity date.
- Owner, and the next action with its due date.
- Reason, if lost.
Do not collect personal data you will not use, and keep passwords and payment details out of notes. Agree who may view, edit and delete a record, and what happens to a leaver’s records.
Step 3: make every quote easy to chase
A quote that is easy to chase is easier to close.
- State what is included, what is not, and what you need from the customer to start.
- Show a validity date so the customer knows when the offer ends.
- Log it in the CRM the moment it is sent, with the file attached.
- Set the follow-up date while the customer is still on the call: “I’ll ring you Thursday morning with any answers.”
- Chase on the date, not when you remember.
Many teams use a simple rule: first follow-up two working days after sending, second after five, then a decision call. Choose your own timing, then keep to it.
Short follow-up messages
- After sending: “I sent the quotation yesterday. Did it arrive, and do you have questions on item three?”
Step 4: record why deals are lost
Lost reasons are the cheapest market research you will get. Use a short list: price too high, chose a competitor, not ready, no response, scope mismatch. After a month patterns appear. If “no response” dominates, your follow-up is late. If “scope mismatch” dominates, your qualifying questions are missing something.
What it looks like in Odoo CRM
Odoo CRM is the app we set up most often for this. It shows your pipeline as columns, one per stage, with each opportunity as a card you drag forward.
| Odoo CRM feature | What it does for your team |
|---|---|
| Pipeline (Kanban) | Every opportunity by stage and owner at a glance |
| Activities | Schedule a call, meeting, email or to-do with a due date and reminder |
| Expected revenue and probability | Forecast what the pipeline is worth |
| Quotations from the opportunity | One click creates a quote in Sales, linked to the record |
| Lost reasons | A required reason when an opportunity closes as lost |
| Sales teams | Separate pipelines and targets per team |
| Website forms and email aliases | Enquiries arrive as leads automatically |
| Reports | Pipeline analysis, conversion by stage and source, lost reasons |
When the customer accepts, the quotation becomes a sales order and flows into Inventory and Invoicing without retyping. See our CRM implementation and Odoo implementation pages.
Where WhatsApp fits
Many enquiries start in WhatsApp. The WhatsApp Business API can be connected so an incoming message creates or updates a lead, and reminders and quote follow-ups go out as approved templates. What is logged automatically depends on the channel and the agreed scope, so we define it in the project. Read about WhatsApp automation.
A rollout that sticks
- Map the stages with the people who use them. A one-hour workshop with real past enquiries, names removed.
- Configure the pipeline and fields. Keep required fields few.
- Import contacts and open opportunities from Excel or your current tool, after cleaning duplicates.
- Train by role. Salespeople practise logging a call, creating a quote and moving a card. Managers practise the weekly review.
- Run a two-week pilot with one team, then adjust.
- Review adoption weekly at first: records with no owner, quotes without a next step, old records that need closing.
If the system feels slow to use, the team will avoid it. Cut fields before adding reminders.
The weekly review that keeps it honest
Spend 20 minutes a week with the pipeline open:
- Opportunities with no next action.
- Quotes older than your follow-up rule.
- Deals stuck in a stage longer than usual.
- New enquiries still untouched.
- This week’s lost reasons.
A CRM does not prove sales value by itself. It makes gaps visible so a manager can act on them.
When a shared spreadsheet is enough
A team of two or three with a few enquiries a week can run on a shared sheet if everyone agrees on columns, owners and update habits. Consider a CRM when handovers fail, when finding the last conversation takes too long, or when nobody knows the next action. Define the problem first. For the platform decision, read Odoo or custom software.