Make revenue handoffs explicit and accountable

Choose the responsibility that each handoff transfers. For SDR-to-AE, it may be discovery follow-up on a qualified opportunity. For AE-to-CS, it may be onboarding coordination for a signed agreement. Neither transfer automatically changes account ownership, renewal ownership, or support coverage. Write those distinctions into the responsibility matrix. Keep the AE as the commercial owner when CS only accepts implementation work. Require a separate authorized decision for any broader ownership change.

Use CRM events as prompts to evaluate readiness, not proof of acceptance. HubSpot distinguishes deal pipeline stages and requires internal stage identifiers in API requests. Its conditional stage properties address manual record creation or movement. Do not assume a populated stage or required UI property validates the whole handoff packet at every entry point. The handoff service must enforce its own contract for manual requests, imports, and event-triggered proposals.[1][2]

Require handoff_id, handoff_type, crm_record_id, packet_version, ledger_revision, state, sender_user_id, recipient_user_id, responsibility_type, source_event_id, offered_at, acknowledge_by, assignment_policy_version, and expected_current_owner_id. Add account_id, opportunity_id, contact_reference_ids, context_links, missing_fields, and unresolved_questions. A decision adds decision_id, decision_actor_id, decision_at, accepted_packet_hash, and rejection_reason. A routing result adds action_key, task_id, routing_receipt, and activated_at. Distinguish received_at from source_event_occurred_at so delayed evidence stays visible.

For SDR-to-AE, require the qualification basis, business problem, known stakeholders, completed interaction, promised next action, and next-action deadline. For AE-to-CS, require the contract reference, purchased scope, implementation assumptions, customer success criteria, commitments requiring confirmation, and outstanding commercial dependencies. Mark an unknown as unknown rather than allowing generated prose to fill it. Synthetic h-208 uses handoff_type=ae_to_cs, packet_version=4, recipient_user_id=cs-12, responsibility_type=onboarding_coordination, and state=offered. No customer details belong in this example.

Use drafted, ready, offered, accepted_pending_routing, active, rejected, expired, superseded, and completed as explicit handoff states. Move drafted to ready only after the sender confirms required context. Offering freezes the packet version and names the recipient. Acceptance moves offered to accepted_pending_routing. Activate only after required task and ownership effects have receipts. Completion requires the accepted next action's proof, not an elapsed timer. Keep the sender accountable while the record is pending routing.

Allow rejection only with a reason and a remediation owner. Missing context returns work to the sender. Wrong recipient sends work to the assignment manager. Expiry preserves existing responsibility and opens an exception. A corrected or rerouted offer supersedes the prior version rather than editing its history. Reject late decisions for superseded versions. The acceptance check attempts offered-to-completed without recipient acceptance and returns Invalid transition, with no task or ownership change.

Assemble context from approved CRM references and sender-confirmed facts. Link the agreement or qualification evidence rather than copying every conversation into the packet. Separate a documented commercial commitment from a desired implementation outcome. If the AE promised an exception that lacks authorization, show it as an unresolved dependency and route the commercial question to the designated manager. Do not let a generated summary turn that promise into an approved delivery obligation.

Show the AE the qualification evidence, immediate next action, due time, sender, and missing decisions. Show CS the purchased scope, success criteria, unresolved assumptions, implementation owner, and commercial contact. Give both recipients the exact packet version they are deciding on. The acceptance check blocks h-208 when contract_reference is missing, with a named sender remediation task. Once the sender adds the approved reference, issue a new version. The recipient must not accept a stale card against changed scope.

Create one recipient decision task with handoff ID, packet version, responsibility, and deadline. Authenticate the actor and verify recipient authority. A task checkbox does not record accepted responsibility. Bind the decision to the packet hash. Atomically require offered state, packet version, and ledger_revision for acceptance, rejection, expiry, and supersession. Acceptance or rejection also requires authoritative server decision time before acknowledge_by. After that deadline, commit expiry through the same guarded transition and return Offer expired without routing or ownership effects. Only one transition wins. Test a late current-version callback while the timeout job is delayed. It must preserve sender responsibility, not become accepted_pending_routing.

HubSpot's tasks API supports a due timestamp, an assigned owner, subject, body, status, and record associations. Use hs_timestamp for the acknowledgement deadline and hubspot_owner_id for the task recipient. Keep the business handoff state in the handoff ledger, not hs_task_status. For the synthetic offer, use hs_task_subject=Review handoff h-208 version 4 and hs_task_status=NOT_STARTED. Retrieve the installed association type instead of assuming one numeric identifier applies to every record type.[3]

Read installed metadata and document the ownership fields that each handoff type may affect. Salesforce sObject Describe exposes fields and relationships. HubSpot deal properties include hubspot_owner_id. Keep current opportunity ownership unchanged when assigning only a CS onboarding task. Before an approved ownership change, re-read the current owner and compare with expected_current_owner_id. A different owner invalidates the routing decision. Show Assignment changed, manager review required instead of overwriting the newer assignment.[5][1]

Enforce the comparison at the write boundary, not only before a network request. Salesforce documents supported conditional headers and 412 precondition failures. Its time-based comparison is weak, and Account ETag support is not an Opportunity guarantee. Use a proven atomic routing path coordinated with all ownership writers. If the installed path lacks that guarantee, require an assignment administrator to execute the change through the controlled process. Never claim an application-side lock prevents an unrelated CRM automation from changing ownership.[6]

HubSpot webhook subscriptions send event payloads to a configured endpoint and expect a 2xx receipt acknowledgement. Separate that transport receipt from the recipient's business acceptance. Persist the authenticated source event before acknowledging delivery. Re-read the CRM state before creating an offer. Treat delayed or repeated events as reasons to reconcile, not to repeat ownership changes. Use handoff_id plus packet_version plus action_type as the durable action key. Preserve separate receipts for the review task, operational task, and any authorized assignment change.[4]

Reserve each action_key under a unique database constraint and atomically claim it before contacting the CRM. Write a pending action record first. Return the existing receipt for completed keys. Store returned task IDs and reconcile uncertain responses before retrying task creation. If you cannot determine whether a task exists, route that key to an operator rather than creating another. Keep accepted_pending_routing visible when a required action fails. Activate only after the current ownership and required tasks match the accepted packet. The recipient then sees Active handoff h-208 with the next-action task link, while the sender sees the same activation receipt.

Define acknowledge_by using the recipient team's business calendar. Save the computed UTC deadline and the policy version. n8n's Wait node supports time limits and authenticated resume callbacks, but its time-based waits use server time rather than the workflow timezone. Compute business hours and holidays outside that timer. On expiry, check the current packet state before escalating. An offer validly accepted before acknowledge_by must not expire because a delayed deadline job wakes up.[7]

Make expiry an exception owned by the sender's manager or the assignment manager, depending on the reason. Do not transfer responsibility to a general queue without a named accountable person. Keep the sender's next action visible until a replacement recipient accepts. If the recipient is absent, issue a newly versioned offer to approved cover. The negative case is a late acceptance on version 4 after version 5 was offered elsewhere. Refuse it and show the current recipient without changing CRM ownership.

Append every state transition with actor, previous state, new state, packet hash, event reference, policy version, and reason. Preserve sender and recipient at the time of each decision. Record both the operational responsibility and the CRM owner before and after any change. Show packet amendments as versions, not silent replacements. Give managers a timeline that explains why a handoff was rejected, rerouted, or activated without reconstructing conversations from private messages.

Keep sourcing attribution, opportunity ownership, operational acceptance, and payout eligibility in separate fields and processes. A recipient accepting discovery work does not resolve SDR credit. CS accepting onboarding does not resolve expansion credit. Finance or the compensation owner must resolve overlapping sourcing claims under the installed plan. Mark unresolved cases credit_status=disputed with a case reference. Keep service work moving when responsibility is clear, but prevent the handoff agent from editing commission inputs or inventing a credit split.

Name failures before measuring them. Duplicate decision returns the existing result. Wrong recipient leaves responsibility with the sender. Ownership conflict blocks routing. Missing agreement blocks AE-to-CS readiness. Revoked acceptance requires manager resolution. A reopened deal requires a fresh business decision, not automatic reversal of CS work. Task creation without its required association remains pending routing. Use a distinct exception reason for each case so managers can distinguish missing context from integration failure.

Define one cohort of offers whose acknowledge_by falls in the reporting window. Calculate timely acknowledgement as offers in that cohort with a valid decision before their own deadline divided by all cohort offers, in percent. Report timely acceptance and rejection separately using that same denominator. Show superseded offers separately with an explicit inclusion policy. Calculate incomplete-packet rate as blocked submitted packets divided by submitted packets. Calculate routing-conflict rate as ownership-blocked accepted offers divided by accepted offers attempting routing. Use the same period for each ratio. Measure activation latency in business minutes between acceptance and confirmed routing. Calculate orphan rate as active handoffs lacking a valid recipient or required task divided by active handoffs. Show counts; an empty denominator is unavailable.

RevOps owns the state machine and assignment policy. Sales and CS managers own context requirements and rejection disputes. The GTM engineer owns event receipts and guarded routing. Finance owns compensation ambiguity. Start with one SDR-to-AE responsibility and proposal-only task routing. Use synthetic duplicate, late-acknowledgement, missing-context, owner-change, and uncertain-response cases before enabling applications. Add AE-to-CS only after the first recipient team can explain every active and expired handoff from its record.

Rollback disables new offers and routing actions while leaving existing responsibility visible. Reconcile pending actions before canceling or superseding them. Do not bulk restore old owners because a newer authorized assignment may exist. A manager approves any reversal against current values. Mark related tasks canceled or superseded through the installed process, preserve their receipts, and prevent old decision links from reactivating offers. End the rollout with a manager queue that names every unresolved owner, deadline, and credit dispute.