Back to all articlesSales handoffs

Handle New Customer Requests That Arrive During the Handoff Window

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A customer replies to the sales confirmation with an extra request: include another location, bring the launch forward, or add a report. Sales forwards the message to delivery. Delivery sees it in the handoff notes but assumes sales is still discussing it. The customer hears nothing—or hears a friendly acknowledgment that sounds like acceptance.

Handle new customer requests during sales handoff with one explicit rule: the sending team owns capture and customer communication until the receiving team explicitly accepts that responsibility. A named assessor evaluates the request, but assessment does not make it accepted work. Record the decision separately, and tell the customer what is confirmed, what remains pending, and when they will hear more.

This approach covers the interval after the sale and before delivery accepts ownership. It does not replace proposal revision procedures or the change-management process used once delivery is running.

1. Define the transfer event before assigning requests

A handoff needs an observable end. Sending an email, scheduling a kickoff, or moving a record to another stage may show progress, but none necessarily demonstrates that someone has accepted responsibility.

Choose a transfer event that your team can record. For example, a named delivery lead acknowledges receipt of the agreed work baseline, accepts customer coordination, and confirms which unresolved requests they now own. This is a recommended operating design, not a requirement to use a particular system.

Until that event, designate a sales-side handoff owner. After it, designate a delivery-side owner. Use names, not just departments. If the assigned person is absent, an identified backup takes over rather than leaving ownership implicit.

Keep two acceptances separate:

  • Ownership acceptance: someone agrees to coordinate the request and keep the customer informed.
  • Work acceptance: an authorised person confirms that the requested work is included, with any conditions recorded.

Delivery can accept responsibility for assessing a request without agreeing to perform it. Conversely, transferring ownership of the original sale should not silently approve every unresolved item attached to it.

2. Capture the request without changing the baseline

The baseline is the recorded work already accepted for delivery. Keep it visible and separate from incoming requests. Otherwise, a well-intentioned edit to a handoff summary can turn a customer's suggestion into an apparent commitment.

Whoever receives the request should capture it in a shared request record or send it to the named handoff owner for capture. Do not require the customer to repeat a message merely because it reached the wrong person. Preserve enough context to distinguish the customer's request from an internal interpretation.

Each entry should contain:

  • The arrival time and channel, plus the person who received it.
  • A plain-language description of the requested difference from the baseline.
  • The customer's stated reason, deadline, and dependencies, if known.
  • The current owner, named assessor, and person authorised to decide acceptance.
  • A separate acceptance status and next-update commitment.
  • A reference to the final decision and customer response when available.

Use a small set of unambiguous statuses: captured—not accepted, assessment pending, clarification needed, accepted with recorded conditions, not accepted, or duplicate of accepted work. Avoid a standalone status such as “added,” which could mean either added to a list or added to the work.

If the baseline itself is unclear, record that uncertainty. Do not label the request “already included” merely to clear the queue.

3. Give capture, assessment, and response different responsibilities

The person closest to the customer is often best placed to capture the request and explain its purpose. That does not necessarily make them qualified to assess effort, timing, or dependencies. Likewise, a delivery specialist may be able to assess feasibility without having authority to accept a commercial consequence.

Use this division of responsibility:

  • Receiver: captures the request or passes it to the owner with its original context.
  • Current owner: maintains the record, obtains an assessment, tracks the next update, and ensures a customer response.
  • Assessor: evaluates what would change, what is unknown, and what existing commitments could be affected.
  • Acceptance authority: approves or declines inclusion within their actual decision rights, or routes it to the appropriate decision-maker.

One person may hold several roles in a small team. The distinction still matters: they should know whether they are acknowledging receipt, evaluating a possibility, or authorising work.

Assign one customer-response owner even when several specialists contribute. This reduces the risk of sales saying the addition is straightforward while delivery is still discovering dependencies. Specialists can speak directly with the customer, but their findings should return to the same request record.

4. Use a filled request decision table

Fictional worked example: A supplier has sold a reporting implementation. The accepted baseline covers one business unit, a standard report pack, and a recorded launch date. Maya owns the sales handoff; Leon is the incoming delivery lead; Priya is the implementation assessor. Elena is the designated authority for accepting changes to this fictional engagement. All names, timings, requests, and decisions below are hypothetical.

The following decision table is presented as labelled rows so it can be copied into a shared document without losing the distinction between ownership and acceptance.

Row A — A second business unit

  • Arrival timing: Monday morning, after the sale and before delivery has accepted the handoff.
  • Request: Include a second business unit in the same launch.
  • Current owner: Maya; sales still owns customer coordination.
  • Assessment responsibility: Priya checks additional setup and dependencies; Leon checks capacity and launch impact.
  • Acceptance status: Assessment pending—not included in accepted work.
  • Customer response brief: Confirm receipt, explain that the second unit is not yet included, and commit to a feasibility update on Tuesday afternoon. Keep the original unit's launch as the working baseline.

Row B — A report already listed in the baseline

  • Arrival timing: Monday afternoon, while the handoff review is underway.
  • Request: Include the weekly summary report.
  • Current owner: Maya until the recorded ownership transfer.
  • Assessment responsibility: Priya compares the requested report with the accepted report list and confirms that the customer means the same output.
  • Acceptance status: Duplicate of accepted work; no additional work authorised.
  • Customer response brief: Confirm that the weekly summary is already included, identify its place in the agreed deliverables, and invite correction if the customer meant a different report.

Row C — An earlier launch

  • Arrival timing: Tuesday morning, during the handoff meeting but before Leon accepts ownership.
  • Request: Launch earlier than the recorded date.
  • Current owner: Maya at arrival; Leon explicitly accepts this unresolved request with the handoff that afternoon.
  • Assessment responsibility: Leon checks capacity and dependencies; Priya checks implementation constraints. Elena decides whether a revised commitment can be accepted.
  • Acceptance status: Not accepted after assessment; the existing launch date remains unchanged.
  • Customer response brief: State that the earlier date cannot be confirmed, explain the relevant dependency, and reaffirm the existing date. Do not imply that the assessment changed the schedule.

Row D — A terminology adjustment

  • Arrival timing: Tuesday afternoon, shortly before ownership transfers.
  • Request: Replace internal department labels in the planned reports with customer-facing labels.
  • Current owner: Maya initially; Leon accepts coordination at transfer.
  • Assessment responsibility: Priya confirms that the change affects display labels only, not calculations or source mappings.
  • Acceptance status: Accepted by Elena with recorded conditions: use the customer's supplied label list; no calculation or mapping changes; no launch-date change.
  • Customer response brief: Confirm the precise label change and its boundaries. Ask the customer to confirm the supplied list; treat any later mapping request as a separate item.

This table makes different outcomes visible. Row A remains open without becoming included work. Row B resolves an apparent addition through clarification. Row C transfers ownership without transferring an unapproved promise. Row D records a bounded acceptance rather than a vague agreement.

5. Assess impact before deciding acceptance

A useful assessment answers a narrow question: what would have to change to fulfil this request? It is not simply an opinion that the request sounds easy.

Ask the assessor to check the requested output, required inputs, dependencies, capacity, timing, and effect on the existing baseline. Where relevant, identify who must decide any commercial consequence. Record unknowns rather than filling them with optimistic assumptions.

There are two reasonable approaches to uncertain requests. A quick triage can identify obvious duplicates or missing information without slowing the handoff. A fuller assessment is appropriate when a request could change resources, sequencing, or customer expectations. The trade-off is speed versus confidence: a fast acknowledgment is useful, but a fast commitment based on incomplete information can create rework.

Do not let pending requests freeze the whole transfer by default. Delivery can accept the original work while explicitly taking coordination of unresolved items. If an unanswered request makes the baseline impossible to interpret or execute, however, record that blocker and assign a decision owner before treating the handoff as complete.

6. Respond with a status, not an accidental promise

The first response should confirm receipt and explain the next step. It should not suggest that capture equals approval. Give a specific update commitment that the owner can manage; if a decision is not possible by then, send an interim update rather than going silent.

Hypothetical acknowledgment for Row A:

We have recorded your request to include the second business unit. It is not yet part of the confirmed delivery scope. Priya and Leon are checking the setup and launch implications, and Maya will update you on Tuesday afternoon. The agreed work for the first business unit remains our current baseline.

A final response should identify the request, state the decision, describe any accepted boundaries, and explain what happens next. If the decision needs the customer's confirmation, say so. Keep “we can assess this” distinct from “we will deliver this.”

When declining a request, explain the relevant constraint without hiding behind internal ownership disputes. The customer needs a usable answer, not a history of which team forwarded which message.

7. Recover when the request falls between teams

If a request has gone unanswered, assign an owner before debating how it was missed. Reconstruct the arrival context, check whether anyone made a commitment, and distinguish recorded facts from assumptions.

  • It exists only in a private message: capture it in the shared record, preserve context, and acknowledge the missed follow-up.
  • Sales implied acceptance without assessment: escalate to the appropriate decision-maker. Do not quietly remove the request or ask delivery to absorb it without review.
  • Delivery started work on a pending item: flag the disputed work, obtain a decision about whether it should continue, and check effects on accepted commitments.
  • The customer received contradictory answers: appoint one response owner, reconcile the internal position, and send a clear correction.
  • The owner is unavailable: activate the named backup and transfer the record, including the next customer-update commitment.

After recovery, improve the specific control that failed. A missing owner needs an ownership rule; a misleading status needs clearer wording; an unseen message needs a capture route. Adding more handoff meetings will not necessarily fix any of these.

8. Test the rule on the next handoff

Before the next transfer, name the sales owner, delivery owner, backup, assessor, and acceptance authority. Record the transfer event and place the request decision table beside the accepted baseline. Confirm that unresolved requests have an owner and a next-update commitment before closing the handoff.

For a small pilot, review every request received during the next few handoffs. Count how many lacked a named owner, how many missed a promised update, and how many were acted on before acceptance was recorded. Also note whether requests labelled as additions were actually clarifications of existing work.

The observable result to look for is not simply a shorter request list. It is a record in which every incoming request has a visible owner, assessment path, acceptance status, and customer response—without altering the agreed work by implication.

Sales handoffsRequest ownershipScope controlCustomer communication

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications