A practical checklist for passing outreach leads to a client or sales team with clear ownership, evidence and the next action intact.
A prospect replies with a real problem, agrees to a conversation, and then gets passed to someone who has never seen the thread. The next message asks questions the prospect already answered. The calendar invitation has no agenda. Nobody knows who should follow up.
For an agency handing leads to a client, the deliverable needs to include enough context for the receiving person to take the next step. Use the checklist below to agree on that handoff before the campaign starts.
Agree on what counts as ready
Write a short acceptance rule with the client. State which facts must be confirmed, which can remain unknown, and what action the prospect has actually agreed to. A friendly reply, a request for a price, and an accepted meeting are different outcomes.
CRM labels need the same care. In HubSpot’s lifecycle-stage documentation, lifecycle stage describes a contact or company’s place in the marketing and sales process; Lead Status describes sub-stages within Sales Qualified Lead. Your agency’s acceptance rule is a separate operating agreement. Map it deliberately to the client’s fields.
Keep confirmed facts separate from assumptions. “Asked about onboarding for a team of eight” is evidence. “Has budget and buying authority” remains unknown unless the conversation established it. Give the receiver that distinction rather than filling gaps with an optimistic summary.
Build one compact handoff record
Keep the essentials together in the agreed CRM record or shared workspace. Link to supporting material instead of scattering the handoff across direct messages.
The entries below are illustrative; adapt the fields to the client’s process.
| Field | Illustrative entry |
|---|---|
| Person and company | Maya Chen, operations lead at Northstar Studio; verified profile and company links |
| Campaign context | Agency operations campaign; conversation began on 19 October |
| Stated need | Asked how onboarding works for an eight-person team |
| Qualification gaps | Budget, purchasing authority and implementation date not yet confirmed |
| Evidence | Link to the relevant conversation and date of the latest reply |
| Commitment | Send an onboarding outline before the introductory call |
| Receiving owner | Alex, client sales lead; acceptance awaiting confirmation |
| Next action | Alex to review the thread and send the outline by the agreed deadline |
Do not put account passwords or unrelated customer conversations in the handoff. Share the context the receiver needs, through an access method the client has agreed to use.
Assign the next action separately
An owner field answers who is responsible for a record. A follow-up task answers what someone needs to do next. Check both.
HubSpot’s task documentation describes assignees, due dates and times, notes, and associations with records. It also notes that an unassociated task does not appear on a record timeline. When using that workflow, associate the task with the relevant record and verify it appears where the receiver will work.
Write a concrete action: “Review the conversation and send the promised onboarding outline.” Add the agreed deadline and time zone. Avoid an empty “follow up” task that leaves the receiver to reconstruct the commitment.
Decide who handles replies while acceptance is pending. Record when the agency should stop its own follow-up and who takes over. Updating CRM ownership alone should not be treated as proof that every separate outreach tool has changed its behavior.
Separate the agenda from internal context
The prospect-facing invitation should explain the purpose of the meeting, who is attending, and what to prepare. Keep internal qualification gaps and negotiation notes in the appropriate internal record.
For a concrete implementation example, HubSpot’s meeting documentation distinguishes an attendee description, which appears in the calendar invitation, from Internal Notes, which do not appear in the contact attendees’ invitation. That distinction concerns the invitation; it does not establish who else can access notes inside the CRM.
Before sending, inspect the actual invitation. Check that the agenda matches what the prospect agreed to and that the receiving person can open the supporting conversation. A link that works for the agency may still require access for the client.
Verify ownership after imports or conversion
If the handoff involves an import or record conversion, inspect the resulting record and outstanding tasks.
HubSpot documents that importing an owner assignment does not notify that user. It also notes that an already-owned contact booking a meeting with another user does not replace the existing contact owner. Ask the receiver to acknowledge the handoff through the agreed channel.
Salesforce’s lead-conversion guidance makes another useful distinction: when a new owner is assigned during lead conversion, open tasks assigned to the converting user are reassigned to that owner, while open tasks assigned to other users are not. Check the task assignee after conversion instead of assuming all unfinished work moved with ownership.
Close the loop with the receiver
Return to the illustrative Northstar handoff. Alex opens the thread, confirms the promised outline, accepts responsibility, and checks the task deadline. The agency records that acceptance and updates its follow-up plan. If Alex cannot accept it, the record stays pending with a reason and a named person responsible for resolving it.
For the first few handoffs, review each one together. Look for missing evidence, inaccessible links, unclear commitments and tasks without an owner. Use those observations to refine the checklist. Track submitted, accepted and returned handoffs separately so the client can see what was delivered and what still needs attention.
