After a customer conversation, your team should be able to see what has happened, who is responsible and what needs to happen next. Sales CRM software gives you a place to record those details, but a contact list on its own is not enough. “Proposal sent” tells a colleague where things stand. “Call on Tuesday to ask whether the revised delivery date works” tells them when to pick up the conversation and what to ask. If the person who sent the proposal is away, a colleague can make that call without asking the customer to explain the situation again.
Capture enough of the enquiry for someone else to act
Agree where the team will record enquiries, whether they arrive by email, phone, referral or website form. You do not need a transcript of every conversation. Record who got in touch, how to reach them, what they need, who is responsible for replying and what the team has already promised. Keep the source if it helps you understand which channels bring in relevant work. A short note such as “Opening a second site in May; needs a separate quote for installation” gives a colleague enough context to ask a useful question without reading the whole email thread.
Check for both an existing contact and an existing opportunity before creating a record. A person calling about yesterday’s web enquiry is usually continuing the same conversation. The same person asking for a quote for a different site may be starting a separate project with its own scope and decision date. Link both opportunities to the same contact rather than mixing their quotes and follow-ups. If enquiries come from several campaigns or channels, the guide to connecting an enquiry to a sales outcome explains why it helps to keep the original source attached beyond the first reply.
Define sales stages that colleagues interpret the same way
Start with milestones your team can recognise: enquiry received, needs confirmed, proposal sent, terms under discussion and closed. Write a plain-language rule for entering each stage. “Needs confirmed” might mean the customer has confirmed the scope and your team can price the work. Use “terms under discussion” when the customer starts discussing a specific point, such as the price or delivery schedule. Sending a reminder does not move an opportunity to that stage, and saving a draft quote does not count as sending it.
Two opportunities can both be at “proposal sent” and need quite different follow-ups. One customer may have promised feedback on Friday; another may need a delivery question answered before reviewing the quote. Write each action with a verb, a purpose and a date. If the timing depends on the customer, note what you are waiting for and pick a date that fits their decision process. When an opportunity closes, record the outcome and any reason you actually know. “No reply” and “chose another supplier” tell different stories. Neither is evidence that your price was too high unless the customer says so.
Worked example: a three-person team handles a venue enquiry
Imagine a small audio-visual supplier with three people handling sales enquiries. On Monday, a venue manager emails about equipment and on-site support for a conference. Maya, who checks the shared inbox, finds the venue’s contact record but sees no opportunity for this event. She adds one, notes the event date and records that the venue has asked for pricing for two rooms. She assigns the opportunity to Daniel, with a call due by Tuesday lunchtime to confirm the room layouts and check whether any speakers will join remotely.
During the call, Daniel learns that the smaller room only needs microphones, but the main room needs support for a remote panel and a rehearsal. He records those requirements and asks Priya, the technical lead, to check equipment availability and rehearsal staffing by Wednesday afternoon. Daniel is responsible for the opportunity; Priya is responsible for that check. She can tell Daniel what is feasible without taking over the conversation or confirming a booking. Daniel records when he agreed to update the venue, so he knows when to get in touch even if the technical check takes longer than expected.
On Thursday, after Priya confirms availability, Daniel sends a proposal, updates the stage and notes which version went out. The venue manager says the event committee meets on Monday. Rather than calling before the meeting, Daniel schedules a Tuesday follow-up to ask whether the committee approved rehearsal time and whether the quote should show costs for the two rooms separately. If Maya covers for him, she knows what was priced, which questions remain open and why the call is scheduled for Tuesday. If the venue postpones the event, the team can record that decision and agree when to revisit it instead of leaving the quote on the weekly follow-up list indefinitely.
Pilot the workflow before moving all your records
Choose a few real, open opportunities for the pilot: a new enquiry, a proposal awaiting a decision and a conversation a colleague will need to cover. During the first week, review actions due today and overdue actions separately from opportunities with no action or owner. An overdue call has someone who can make it; an unassigned enquiry may not. At the end of the week, look for the point where work went unattended. If it happened during a handover, agree who updates the record and confirms that the colleague has accepted responsibility before adding another reminder.
If you want email or form submissions to feed into the CRM, test the integration before relying on it. Use sample data to check where a submission appears, who sees it, whether a repeat enquiry creates a duplicate and how the team would notice a missing record. If you use AI to draft a follow-up, have the person responsible for the opportunity check the recipient’s name, scope, dates, price and any promises before sending it. For help deciding where to begin, see the guide to choosing which sales tasks to automate first.
First-week checklist and common questions
Ask a colleague who has not worked on an opportunity to read its record. Can they explain what the customer expects and show where they would record the outcome of the next call? If they need access to someone else’s inbox to answer, identify what is missing. A link to the proposal that actually went out may be more useful than a new field that everyone has to fill in.
- Name the person who checks for new enquiries and the colleague who covers absences.
- Ask two colleagues to apply the same stage rules to one opportunity and compare their answers.
- Make sure a colleague covering the account can find the latest proposal and the last promise made to the customer.
- Agree which details do not belong in sales notes and who needs access to the records.
Is free sales CRM software enough for a small business?
It can be if your team can manage its daily work without keeping a parallel record elsewhere. Test the plan with a real handover and check whether the people doing the work can see and update the right information. Review the plan’s current limits and check what you can export, including whether the export contains the notes or activity history you would need if you moved. The guide to choosing a CRM for a small business can help you compare options against the tasks your team actually performs.
What if there is no obvious next action?
Decide whether the opportunity is still active. If the customer expects to make a decision next month, record that and schedule a check-in around their plans. If nobody knows whether the project is going ahead, ask one person to find out. Once you reach the team’s agreed stopping point without a reply, take the opportunity off the active list and record that no response was received. If the customer comes back later, the next colleague can see where the conversation left off without treating the silence as a refusal.
