Your CRM should store enough information for a colleague to identify a contact, understand why you’re talking and take the next step. Start with a name when you have one, a reliable way to get in touch, and the person’s organisation or role if it matters to the conversation. For an active enquiry, record what the person needs, who is handling the next action and when it’s due. You can fill in other details as they become useful rather than making a complete contact record a condition of replying.
What to capture when an enquiry arrives
If an enquiry comes from a shared inbox and nobody signs it, log the enquiry with the address and organisation, if known, rather than guessing who sent it. Add a person’s record when they introduce themselves. If someone has already contacted you by email, a missing phone number is rarely a reason to delay. Make a field mandatory only when your team can’t reliably do the work without it.
Describe the request in terms a colleague can use tomorrow. “Interested” is less useful than “Needs a quote for servicing two sites before the current agreement ends.” Write the next step as a task: “Sam to confirm both addresses by Thursday” is clearer than “Follow up.” Distinguish an internal reminder from a deadline promised to the customer. If the customer says they’ll revisit the work after moving premises, record that condition instead of turning an estimated moving date into a commitment. You can still set an internal reminder to check whether anything has changed.
Track where enquiries come from if the information helps you assign work or understand which channels bring in relevant requests. A team comparing referrals with website enquiries can start with a short list and an explicit “unknown” option. Agree on what the field measures: a person might hear about you through a referral and then submit a form on your website. If both facts matter, distinguish how they heard about you from how they got in touch. For an example of using source information beyond the initial reply, see the guide to connecting an enquiry to a sales outcome.
Keep contacts, organisations and deals separate
A contact record describes a person: their name, work contact details and, where relevant, their job title or preferred way to get in touch. An organisation record holds information about the business, such as its name and main office number. A deal describes a specific potential sale: what’s being discussed, where it stands and what needs to happen next. Even if your CRM shows all three in one view, keep updates attached to the record they describe.
Suppose a facilities manager asks for a quote for one site while negotiating a renewal for another. Both conversations involve the same person, but “quote sent” may describe only one of them. Keep the deals separate and link the contact to both. If another person approves the renewal, record their role on that deal rather than labelling them the decision-maker for every purchase. If someone changes jobs, check how your CRM handles historical associations before updating their employer so that older activity remains tied to the right organisation.
Separate responsibility for the relationship from responsibility for the immediate work. The account manager may remain the same while another colleague prepares a revised quote. Assign the task to the person doing it, and note who will send the quote if that’s someone else. A contact name alone won’t tell your team where the work is waiting. The guide to moving from first contact to the next sales action covers that handover in more detail.
Write a history someone can use
After a meaningful call, note what was confirmed, what’s still open and what each side agreed to do. “Customer wants a cheaper option” leaves room for interpretation. “Customer asked for a version without on-site training and will review both options on Monday” tells a colleague what to prepare and when to expect a response. Distinguish a request from a promise and a working estimate from an approved figure. If an agreement changes, update the task as well as the notes so the old reminder doesn’t send someone back to the customer with the wrong question.
You don’t need to duplicate every email or attachment. If the team edits a proposal in a shared workspace, link to the current version and check that the people taking over can open it from their own accounts. If you connect email or calendar tools to the CRM, test the integration with a few records first. Check who can see the activity, where it appears and what happens when a message includes several contacts. An email thread can contain the evidence of a decision without making that decision easy to find, so keep a short note when it saves someone from reading the whole exchange.
Leave out personal details and private observations that don’t help the team do its work. “Use email for scheduling” is a useful preference; the private reason behind it usually isn’t. Don’t store passwords in a contact record. Agree who corrects inaccurate details and reviews stale records under your organisation’s retention policy. If an old number is no longer valid, update the record so staff know which number to use.
How a three-person team hands over an enquiry
Imagine a small commercial maintenance company. Nadia, a property manager, emails to ask about regular servicing for two buildings. Alex adds her name, work email and employer, then opens a deal for the two-site enquiry. He records that Nadia wants separate prices for each building but hasn’t confirmed when staff can get in. Rather than promising a quote date before he has the information he needs, he sets a task for Tuesday: ask Nadia for the access hours and the equipment list.
Alex is out on Tuesday, so Jo picks up the task. The record tells her why she’s writing and what Nadia has already explained. Nadia sends the equipment list and introduces Lee, the site supervisor. Jo adds Lee as a separate contact and notes that he can confirm access arrangements for this deal. She doesn’t mark him as the buyer. Priya, the third team member, gets a task to prepare the two prices once Lee confirms the hours. Until then, the record shows what’s holding up the quote.
A few days later, Nadia asks about a one-off job at a third building. Jo links the new enquiry to Nadia and the existing organisation but keeps it separate from the servicing deal. At the weekly review, Lee has confirmed the hours, so the servicing deal is ready for pricing, while the one-off job is waiting for a site visit. Priya also finds that the equipment list links to Alex’s private folder. Jo puts a working copy in the appropriate shared folder, updates the link and asks Priya to open it before starting the quote. The handover exposes a problem that checking whether every contact field was filled in would have missed.
A practical checklist before you import or add fields
Test your setup on a small batch before importing the whole address book. Include an incomplete enquiry, a repeat customer and an organisation with several contacts. Try a contact without an active deal as well: if someone asked you to get back in touch when another project starts, you can record that reminder without creating a sales opportunity. If you’re still comparing tools, use these cases alongside the criteria for choosing a small-business CRM.
- Check what’s required at intake. A colleague should be able to log an enquiry with one usable contact channel and a short description of the request.
- Search before adding a person. Look for the email address, name and organisation. A shared mailbox isn’t proof that two records represent the same person, and someone copied on a single email doesn’t automatically need a record.
- Review before merging records. Identify the current details and check which conversations and deals belong with the record you’ll keep. Check the links again after the merge.
- Test a handover without coaching. Ask someone unfamiliar with the enquiry to identify the latest commitment, the next action, who’s responsible for it and when it’s due.
- Test document access and review custom fields. Have the colleague taking over open the linked documents. For each extra field, ask who uses it, who updates it and whether a report, decision or task depends on it before making it optional or removing it.
Record where the trial stalls. If a colleague finds the proposal but can’t tell whether it was sent, agree where to record the send date and try the handover again with a different deal. That second test shows whether the change helps someone who wasn’t there when you fixed the first record.
