Follow up enquiries: a clear CRM process

Record incoming enquiries and ownership clearly

Start with a review of the current situation: where do enquiries originate, who receives them, and where is their handling documented? Include website forms, email, telephone, events and referrals. Use a few actual cases to check whether important information is lost during handovers or entered more than once.

Define a small shared minimum: company, contact person, inquiry, source, date received, and responsible person. Not every inquiry needs an extensive assessment immediately. The initial record should primarily preserve context and enable handling. Also establish who covers absences and how incorrectly assigned inquiries reach the right person.

Distinguish contact status, sales opportunity and task

A status describes the current situation; a task describes what needs to happen next. HubSpot, for example, distinguishes lifecycle stages in the marketing and sales process from a more detailed lead status. Exact terminology varies by system. Only adopt categories that your team can apply unambiguously.

Statuses such as new, awaiting response, needs clarified, proposal under review and completed may suit your process. Define when each status begins and how it ends. A company may also have several separate needs. Consider which information belongs to the contact and which relates to an individual project or proposal, so different matters are not mixed together.

Source: HubSpot: lifecycle stages for contacts and companies

Turn every conversation into a concrete next step

Finish handling a case with a clear note: what was discussed, what remains open, and who takes the next step? Where possible, agree an appropriate time with the person making the inquiry. A standard follow-up schedule does not automatically suit every need, decision process, or preference already expressed.

Create a task with an owner and due date. HubSpot documents features including associations with records, assigned users, due dates and reminders. Check your own CRM to see whether and how these functions are available. Make the task specific, such as “Answer the outstanding question about the service scope”, so that the next person can act without having to search again.

Source: HubSpot: creating and assigning tasks

Automate handovers with clear boundaries

First review recurring internal steps: can a new inquiry be assigned to a responsible person, a task be prepared, or an alert about missing information be generated? Describe the intended workflow initially without software terminology. This makes it clear which decisions follow a fixed rule and where someone needs to assess the context.

Then test typical exceptions. What happens with a duplicate enquiry, a response through another channel, a change in responsibility or a completed case? An automatically prepared message should not continue when the person has already replied and individual clarification is needed. Explicitly define starting conditions, stop rules and a visible route to manual handling.

• Trigger: exactly which event starts the process?
• Responsibility: who notices errors or reviews exceptions?
• Stop: which response or status change ends the process?

Review open cases and the quality of handovers

Establish a regular review of open inquiries. Look specifically for cases without a responsible person, without a next step, or with an overdue task. Discuss recurring causes with the team: is information missing, are status labels unclear, or is a handover undefined? First adjust the relevant process step.

Use the source of an enquiry together with its subsequent professional assessment to inform discussions between marketing and sales. This helps distinguish whether the messaging attracts unsuitable contacts or suitable contacts are not being followed up internally. Based in Hamburg, anwision connects marketing with CRM structures, lead allocation and follow-up processes. The starting point is your team's actual workflow and which steps need to be organised more clearly and reliably.

A decision example: when responses arrive through several channels

Suppose a prospect asks about a service through the website form. The responsible person replies by email and schedules a follow-up. Meanwhile, the prospect calls a colleague and resolves the matter by phone. If this information is not added to the shared record, the originally planned message may miss what was discussed. Therefore, describe how updates are handed over when they arrive outside the original channel.

Define the note required after such a conversation: the current issue, the decision discussed, and the agreed next step. The colleague also needs to see who will continue handling the case. A short handover should confirm the existing responsibility or explicitly change it. At the same time, check whether an outstanding task needs to be adjusted or closed.

Test the workflow with a sample record before activating automated messages. Ask one person to record the initial enquiry and another to document the telephone follow-up. Together, check which tasks remain visible afterwards and whether a prepared message is still factually appropriate. Record the outcome of this test in clear working instructions.

The same approach helps with returning contacts: a company may come back later with a different need. Make a deliberate decision about which information belongs to the existing contact and which should become a new case. A completed assignment should not automatically make every later enquiry appear resolved. This practical distinction needs to be clear before it is represented through fields, rules or notifications in your CRM.