Give inbound enquiries a reliable route from capture to ownership, next action and outcome. A practical workflow for forms, calls and messages.
An enquiry may have been seen in an inbox, shared in a team channel and discussed in a meeting without anyone taking responsibility for it. Buying a more sophisticated CRM does not automatically resolve that gap. Establish where the record starts, who owns it and which action moves it forward. The tool becomes useful when it supports that operating process.
Map the actual entry points
List forms, calls, WhatsApp, social messages, events and referrals. For each source, record how information enters the system and who sees it today. “Everyone sees it” is not ownership. An enquiry remaining in an individual inbox before it reaches the shared process can become an invisible loss.
Keep initial information purposeful: the request, necessary contact details, source, capture time and relevant service. Define how an existing record will be found when the same person uses another channel. Duplicate records can cause different teams to approach someone without knowing the previous conversation.
Connect ownership to a next action
Every open enquiry should have an owner and a next step. Replace ambiguous statuses such as “handled” with stages that have a clear operational meaning: initial review, awaiting information, meeting arranged or proposal in preparation. A stage change should correspond to something observable.
HubSpot's record-ownership documentation explains assigning records to users. An equivalent field in your CRM is only a starting point; the process also needs to establish that the person knows about and accepts the work. Define what happens to pending enquiries during absence, overload or a staffing change.
Make waiting records an actionable list
Consider a hypothetical project enquiry assigned correctly but left waiting for more information. If nobody defines the follow-up action and its timing, assignment alone does not move it forward. Making the reason for waiting visible may be more useful than adding another notification.
| Stage | Event that moves it forward | Required follow-up |
|---|---|---|
| New enquiry | Owner reviews the request | Owner and first action |
| Awaiting information | Required answer arrives | Missing information and next review |
| Meeting arranged | Meeting takes place | Purpose, owner and outcome |
| Proposal in preparation | Proposal is prepared and shared | Inputs and approval owner |
| Closed | Win or closure decision is made | Outcome and useful reason |
Use the same outcome definitions across sales and marketing
Marketing needs to learn which enquiries fit and why others do not progress. An overly broad service description may attract unsuitable requests; slow handling of suitable enquiries points elsewhere. Investigate the record instead of assigning every loss to advertising or sales by default.
Regularly review open records without owners, records without next steps and those that have stopped progressing. Choose a review rhythm appropriate to the sales cycle. Record a usable outcome rather than an ambiguous closing note. The system should help the team identify the next useful action, not merely create more fields to complete.