Customer-Led Cross-Sell and Upsell: Team Playbook

A cross-sell goes wrong when a weak account signal becomes an offer before anyone checks what the customer needs or whether a service problem comes first. Start with one request and fill the card below. It takes the team to one visible result: present checked options, ask for clarification, route to service, or take no action.

Start with the expansion decision card

1. Customer's request in their words:
2. Current service issue or reason to pause:
3. Approved options and source date:
4. Decision: [present | clarify | service first | no action]
5. Person responsible for the next step:
6. Stop or handoff condition:

First action: copy the card into a document or CRM note and fill the customer's exact request. Do not begin with a model score or a sales target.

Completion standard

• Start state: a verified customer event suggests a new job or expanded constraint.
• End state: an approved option is accepted for consideration, a human owns clarification, or the record closes with no action.
• Evidence: original customer wording, account/service state, option-source version, approval, handoff acceptance, and final disposition.
• Time horizon: one approved evaluation window; re-entry needs new customer evidence.

Roles and prerequisites

Before starting, define eligible evidence, service precedence, approved catalog and version, commercial authority, per-channel permission, no-action rule, rollback, response targets, and quality baseline.

In a small team, one person may combine account, catalog, and operations duties. Keep service or safety review separate when the same person cannot independently judge the issue, and always name a backup for customer replies.

Phase 1: verify the expansion event

• Owner: account owner.
• Inputs: customer wording, verified identity, account history.
• Actions: distinguish explicit new job from inferred interest; record source and freshness.
• Output: eligible event or no-action record.
• Exit gate: job and evidence are confirmed or labeled unknown.
• Escalation/rollback: suppress when identity or permission is uncertain; never convert model affinity into stated intent.

Phase 2: apply service and eligibility precedence

• Owner: service owner.
• Inputs: eligible event, open cases, returns, disputes, commitments.
• Actions: reconcile newer events and determine whether commercial action is allowed.
• Output: proceed, wait, or service-first decision.
• Exit gate: no unresolved higher-priority state conflicts.
• Escalation/rollback: cancel queued offers on a new issue; restore the prior account state.

Phase 3: build an approved option set

• Owner: catalog/commercial owner.
• Inputs: customer job, current catalog, eligibility and authority rules.
• Actions: select zero to three factual options; state differences, assumptions, and unknowns.
• Output: versioned option packet or no-match result.
• Exit gate: every claim and price/scope element has current approval.
• Escalation/rollback: remove stale or unsupported options; route exceptions to the authorized owner.

Microsoft publishes a vendor scenario for contextual cross-sell/upsell with human support. It illustrates a mechanism, not an outcome or Easy AI integration.

Phase 4: present, clarify, and hand off

• Owner: account owner.
• Inputs: approved packet, customer channel and permission.
• Actions: restate the job, present bounded choices, include no-action, and capture correction.
• Output: customer disposition and next owner.
• Exit gate: recipient accepts the handoff or the customer closes the decision.
• Escalation/rollback: withdraw an incorrect packet visibly; send negotiation or procurement authority questions to a person.

Phase 5: reconcile and review

• Owner: account owner; RevOps owns QA evidence.
• Inputs: interactions, order/service events, corrections, handoffs.
• Actions: cancel obsolete tasks, record final reason, sample quality, and decide whether to keep or pause the route.
• Output: reconciled disposition and review record.
• Exit gate: no stale action remains and every exception has an accepted owner.
• Escalation/rollback: pause the route when correction, service-conflict, or unaccepted-handoff thresholds are crossed.

Fictional completed run

A fictional equipment distributor receives a message from a warehouse manager opening a second site. Account owner Noor records the customer's request for device compatibility, not an “upsell intent.” Service owner confirms an unrelated repair case is closed. Catalog owner supplies two current scanner options and flags that procurement authority is unknown. Noor presents the factual comparison and a no-action choice; the manager asks procurement lead Ravi to join. Ravi accepts the handoff, and the automation closes without creating a quote or claiming expansion.

• Customer's request in their words: “Which scanners will work at our second warehouse?”
• Current service issue or reason to pause: Prior repair case checked and closed
• Approved options and source date: Two current scanner options from catalog version dated 15 August 2026
• Decision: clarify
• Person responsible for the next step: Noor; procurement lead Ravi accepts the authority question
• Stop or handoff condition: Do not quote until purchasing authority is confirmed; close if Ravi declines

Handoff, QA, and measurement

QA checks: explicit evidence; current identity/permission; service precedence; catalog version; factual option differences; no-action available; accepted handoff; stale actions cancelled.

Failure signals include inferred intent presented as fact, stale options, offers during service cases, high customer correction, and timed-out owners. Pause the affected rule, repair source or ownership, and replay representative cases.

What to do after completion

Review the strategic boundary with cross-sell using customer context, implement one approved record using the contextual recommendation template, or connect ecommerce timing through the repeat-purchase use case.

Evidence and limitations

No revenue, conversion, recommendation quality, integration, catalog availability, or Easy AI capability is claimed.