Complete the CRM handoff
Complete the CRM handoff.
3 stages · 1 approval
Roles and responsibilities
-
Step 1Review qualification
Lead NumberCompanyOwnerAssigned AE
-
Step 2Create CRM handoff
Conversion NumberLeadTarget WorkspaceOpportunity Name
-
Step 3Reconcile conversion
Conversion NumberLeadTarget WorkspaceOpportunity Name
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Approval required
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.
Approvals and exception handling
1 approval required in this process
-
Review qualification
Account Executive signs · create crm handoff waits
Leads - Record ownershipKeep every reference and attachment in the authorized workspace and the acting person’s permitted scope. A copied link cannot grant access to another customer’s record.
- Current decisionsReview the latest saved state before changing work. If someone changes protected facts after approval, send the revised record through its required review again.
- Repeated actionsA retry returns the original result when the same action has already been accepted. Keep an uncertain external outcome visible until its original request is reconciled.
- CorrectionsRetain the earlier decision and the reason for correcting it. A report or automation should not hide a reversal by deleting the original evidence.
When the process needs attention
-
reject
Create CRM handoff
ConvertedAt and AccountAction remain unset in Draft, Pending, Failed or Unknown.
-
reject
Reconcile conversion
Investigate failed or unknown requests through their original command key and provider reference.
Follow the outcome
The receiving team needs the current owner, the next action and a traceable result. Use the linked operating records when investigating a delay rather than treating a status label as the complete explanation. If a required person is unavailable, route the decision through an authorized replacement who remains independent of its preparer. Resolve missing evidence before closing the handoff. A locally completed action may still require a confirmed response from its configured destination.
Lead capture. A repeated web-form event resolves to the same lead. Reject foreign-workspace references and imports without a stated source.
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.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Review qualification | Leads | Record an independent decision on the submitted revision |
| 2 Create CRM handoff | LeadConversionsIntegrationEvents | Retain the stated outcome and its source evidence |
| 3 Reconcile conversion | LeadConversionsIntegrationEvents | Retain the stated outcome and its source evidence |
Process reports
All reportsSource Quality
Qualification outcomes by source and scoring-policy version, with unknown outcomes separate.
Conversion Reconciliation
Pending, unknown and failed CRM handoffs with original request references.
Lead Funnel
Lead intake through independent qualification and acknowledged CRM conversion by source.
Run by an agent
Agent support
An agent acts within the current user or service scope. It cannot provide its own independent human approval, restore a withdrawn contact purpose or turn an unknown external response into a confirmed result.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› complete the crm handoff · review qualification on Leads
⏸ approval · waiting for the account executive
# 2 more stages after approval: create crm handoff, reconcile conversion