Agree transfer conditions, acceptance and outcome reporting so enquiries move forward with their original context.
An enquiry needs an accepted owner
A campaign and form may work while a shared inbox leaves everyone assuming someone else will reply. The failure lies in the handoff, not necessarily in demand generation.
Define when sales accepts responsibility. A notification alone is insufficient: the enquiry needs an owner, an action deadline and a way to detect inactivity. This separates poor contact quality from poor handling.
Agree the minimum useful context
Sales should know the request, its source and what the prospect has already done. Someone asking about a specific service should not need to restart the whole explanation. Equally, excessive required fields can discourage contact without improving the conversation.
Collect what is needed to begin and enrich the record progressively. Marketing cannot establish purchase certainty from a short form. Qualification and sales exist to develop that understanding.
Handoff rules
- Named owner and cover for absences.
- Need, source and previous context.
- Deadline for a useful first response.
- Acceptance or a reasoned reassignment.
- Escalation for cases left untouched.
Give statuses shared meanings
Marketing may use qualified to mean a completed form, while sales means confirmed budget and timing. Without agreed definitions, reports create an artificial conflict. Document the condition for entering and leaving each stage.
A few consistently used statuses are better than a complex taxonomy nobody maintains. Distinguish unreachable, unsuitable, active discussion and an actual purchase decision.
Example: reassignment without acceptance
An implementation enquiry is assigned to someone selling another service. They forward it without changing the system owner. Reporting still shows an active case, but nobody is planning the next action.
Reassignment should end with the new owner accepting the task. Responsibility remains explicit until that happens. This matters during holidays, staffing changes and enquiries spanning several teams.
Feedback must be actionable
Poor quality is too vague to improve acquisition. Record a practical reason such as unsuitable scope, project size, market or no response after agreed contact attempts. A short explanation makes the category more useful.
Review good conversations too. They reveal which needs and messages lead towards sales. More volume can overload a team without increasing contract value, so enquiry count alone is an incomplete objective.
Test the process
- Send a test enquiry through every active form.
- Check assignment, notification and context.
- Rehearse an absent owner and cross-team transfer.
- Compare response times and outcomes for similar contacts.
A good handoff lets the customer continue one conversation with the business. It also gives the team reliable evidence about where sales progress actually stops.
Implementation plan: five steps
Define the handoff condition
Specify source, subject, context and response route. A download does not automatically request a sales call; the condition should reflect what the person expects after their action.
Assign ownership and response
Every contact needs a person or accountable queue, including holiday cover. Match response times to promises and distinguish an automatic receipt from an actual conversation.
Preserve offer context
Show salespeople the content preceding the request. This may help more than additional form fields and prevents clients having to repeat information they have already supplied.
Record specific return reasons
Separate mismatch, unsuccessful contact and insufficient handling capacity. “Bad lead” alone does not reveal whether the campaign, contact data, offer or sales organisation needs correction.
Pilot and review together
Test one service, comparing transfers, acceptance, conversations and proposals. Resolve ambiguous statuses before automation and finish each review with a specific improvement, owner and deadline.
Related articles
- Lots of leads but few sales. Where is the problem?
- Sales are declining. Where should a business start the analysis?
- Which products and customers actually generate margin?
- Sales follow-up: planning useful contact after a proposal
FAQ
Is a formal SLA necessary?
Larger teams benefit; a shared table of responsibilities, timing and statuses can be enough initially.
Who owns quality?
Both teams own their stages using common criteria and handling evidence.