Partner lead intake is a handoff. It fails when the receiving team has to reconstruct the partner's conversation. Capture enough context for someone else to act, preserve the prospect's permission, and give the partner a clear way to see what happened. Treat consent as part of the lead record, alongside identity and buying context. Naming the lead buyer before the consent page can restrict the lead to that company.1 Lead buyers should consider requiring a copy of the consent language with the other lead data.2 Build the form around that rule, then review the record before it enters the sales process.
The intake sequence
- Prepare
- Identify
- Context
- Consent
- Review
Use the stages below to keep the handoff in order. Move forward when the question in one stage has a clear answer, and send the record back when it does not.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Prepare | whether the partner is connected and knows the submission format | Can you submit a test lead in the required format? |
| Identify | whether the record names the prospect and proposed transaction | Which company is this, and what transaction is under discussion? |
| Context | whether the record contains enough buying detail to act | What has the prospect told you about goals, pains, timing, and next steps? |
| Consent | whether permission can travel with the record | What consent did the prospect give, and what exact language can you attach? |
| Review | whether qualification, contact, and account checks are complete | Is this a new lead, or does an active opportunity already exist? |
| Handoff | whether the partner knows the status path and can correct an active record | What should happen after submission, and how will you flag an error? |
Set up before the first live submission
Before a partner sends a live lead, settle access, format, and the test path. This keeps an intake problem from looking like a lead quality problem.
Accept the invitation to connect and formalize the relationship with the lead buyer.3 Read the partner submission documents so the required format and data mapping are clear.4 Verify the setup with a test lead that meets the technical requirements before moving into live submissions.5 Some parts of the testing process may not apply to every process.6
If partner groups need different intake fields, enable and customize the lead form separately for each group.7 Write down the required fields, the consent artifact, the destination for accepted leads, and the path for failed submissions. Move on when the test record reaches the receiving workflow with the intended values intact.
Capture identity and buying context
A partner submission should let the receiver understand who the prospect is, what they may buy, and what work has already happened. Ask for enough detail to support review without making the receiver reopen the partner conversation.
Require a completed referral sheet that identifies the referral customer and describes the proposed transaction.8 One documented partner form requires Company Name, Country, City, Company Type, Email, Phone, Primary Product of Interest, First Name, Last Name, Title, Total Potential Users, Goals, Pains, Next Steps, Purchasing Timeframe, Zip Code, Number of Employees, and Potential Sales Value.9
Have the partner enter the prospect, opportunity details, and work completed so far.10 Use the partner's account to fill gaps in the record. Ask, "What was that process like?"11
Do not accept a submission that gives you a name and email while leaving the buying situation unclear. Send it back for the missing context before review begins. The record is ready for the next stage when another person can understand the opportunity without relying on the partner's memory.
Preserve consent in the handoff
Give consent its own checkpoint in the form. Treat it as a submission requirement that the reviewer can inspect, rather than something the team will recover later.
Place consent capture before any buyer specific selection in the workflow. Make the permission record travel with the contact and buying context. If the consent language is missing or cannot be read, hold the lead and ask the partner to correct the submission. Keep the consent check separate from qualification so a promising opportunity does not bypass the permission review.
Review before acceptance
Review is the gate between a partner's submission and internal action. Use it to test lead quality and account ownership before anyone starts a new motion.
The lead review checks whether the lead is properly qualified and whether the prospect contact information is valid.12 For a qualified lead, check the system for active opportunities and related leads on the account.13 When existing opportunities are found, the Account Executive confirms which partner is working with the client and whether that partner's role is a sourcing partner or a joint sales partner.14
Route the record only after these checks produce a clear outcome. If the account already has activity, resolve the relationship before creating another path. If the contact or qualification is weak, return the record with the exact field or answer the partner needs to fix.
Submit, update, and monitor the record
Submission should create a traceable handoff, with clear expectations about who works the lead and how the partner sees progress. Keep the record editable while it is active, then close the editing path when its state changes.
For a submitted lead, the company's sales team works to close the customer and keeps the partner updated on the lead's status.15 In a documented portal flow, the partner logs into the Partner Dashboard.16 From there, they click "Your programs" and select the company receiving the lead.17 The next step is the "Leads" tab.18 They then choose "Submit a lead".19 All mandatory fields must be complete before submission.20
Give the partner a way to view the original lead information and make changes while the lead is active. One documented workflow does this through the Partner Lead Number.21 Do not build the correction process around post conversion edits, because converted leads may not be edited.22 Update every case action required to document lead completion.23
Tell the partner where status will appear and what event closes the intake loop. A submission is complete when the record is reviewable, the receiving team can act on it, and the partner can see what happened next.
What not to do
These intake failures create avoidable follow up and unclear ownership.
- Do not leave lead monitoring undefined. Partners are responsible for monitoring their leads, and being proactive is in their best interest.24
- Do not make an informal message the only correction path. If a partner believes a lead was not processed correctly, they should submit a support case for review.25
- Do not promise that a converted record can be changed. Converted leads may not be edited.22
Use the approved record structure consistently as new partners enter the process.