Qualification and handoff
Give account executives the context to accept a qualified lead.
Approval conditions
Visible to: Account Executive. Visibility does not establish approval authority.
- LDS-74186 Submitted lds-938 50 2 d
- LDS-12984 Submitted lds-943 55 7 d
- LDS-68986 Submitted lds-256 85 11 d
- LDS-59557 Submitted lds-477 20 14 d
- LDS-28060 Submitted lds-654 80 8 d
- Company
- CMP-233
- Owner
- DL
- AssignedAE
- GB
- Score
- 50
- QualificationReason
- Submitted lds-938
Approval conditions.
Work with the right context
Submit the prospect’s needs, fit and recent interactions to the assigned account executive. That person can accept the handoff or return it for more work with a clear reason. Keep the decision separate from the numeric score so the next team understands what was actually reviewed.
Keep the next action clear
When the lead is accepted, carry a durable request into the connected CRM. Retain the target account, contact and opportunity references only after the target confirms them. An uncertain connection result remains a visible handoff issue until reconciled.
Coordinate the workflow
Review qualification. The SDR submits qualification evidence and an eligible AssignedAE using Status: MQL → Submitted. That AE independently accepts the handoff into SQL or returns it to Working with a reason. The decision checks the same revision, current contact policy and territory assignment; a score alone cannot mark a lead SQL. Record QualificationSubmittedBy at submission and require it to differ from QualifiedBy, even after reassignment.
Create CRM handoff. Create one durable conversion intent for the approved SQL, with target workspace, connector and requested CRM identity. Submit the command once and correlate the returned account, contact and opportunity references. Pending or Unknown transport state leaves the lead unconverted. Mark Succeeded and Converted only after verified target acknowledgement. Record RequestedAt when creating the intent. ConvertedAt and AccountAction remain unset in Draft, Pending, Failed or Unknown. Succeeded requires correlated target AccountRef, ContactRef and OpportunityRef plus the acknowledged account action and verified success time.
Reconcile conversion. Investigate failed or unknown requests through their original command key and provider reference. A retry reuses that intent. If the target object already exists, reconcile its identity instead of creating another. An unresolved mismatch remains visible to the AE and Sales Manager.
Qualification approvals. The assigned AE accepts a reviewed MQL as SQL with recorded evidence. Reject self-review, stale revision and conversion based on score alone.
CRM handoff. Pending intent retains RequestedAt without invented success facts; verified target acknowledgement supplies all target IDs and permits Succeeded. Unknown cannot invent ConvertedAt or AccountAction; reject a success callback missing target IDs and a retry creating another opportunity.
Review a qualified prospect
The development rep assembles the prospect’s interest, recent conversation and qualification reason for the assigned account executive. The reviewer checks that current submission and records an independent decision. A high score can explain why the lead received attention, but it cannot stand in for the evidence needed to accept the handoff.
If the account executive needs another conversation, keep that outcome visible and return the open question to the working owner. Reassigning the lead must not allow its material preparer to become the independent reviewer of the same submission. The distinction protects the meaning of an accepted qualification even when the team changes responsibilities.
Finish the external handoff
An accepted lead can request an opportunity in the connected CRM. Retain the request identity and keep the conversion pending until the destination acknowledges the resulting record. If the connection times out, reconcile the original request before asking it to create anything again.
A repeated acknowledgement should resolve to the same external reference. A failed or unknown request remains available for investigation without marking the lead converted. The account executive can then distinguish accepted qualification from completed CRM creation. This makes the sales handoff useful to both teams: the lead record explains the qualification decision, and the returned CRM reference identifies where the opportunity will be worked next.
Modules
-
Lead capture
Bring incoming prospects into a consistent qualification queue.
-
Scoring and AI
Explain why a lead deserves attention before the team acts.
-
Routing and alerts
Put the next lead with someone who can act on it.
-
Outreach and preferences
Coordinate useful follow-up while respecting contact preferences.
-
Qualification and handoff
Give account executives the context to accept a qualified lead.
-
Funnel analysis
Learn which sources and signals lead to accepted opportunities.
Roles and permissions
Prepares lead sources, scoring policy and lead-list hygiene.
Owns team routing and independent duplicate resolution.
Works assigned prospects and submits qualified leads to the selected account executive.
Reviews assigned qualification handoffs and requests creation of downstream CRM records.
Reads permitted funnel summaries with personal contact fields masked.