Set Boundaries for Temporary Sales Cover and the Return Handoff
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Consider this hypothetical situation: an account owner returns, reads the latest conversation and assumes the opportunity is unchanged. Meanwhile, the covering colleague has revised a proposal, learned that another approver must attend the next review and promised an answer from implementation. The activity history exists, but nobody has made the active obligations clear.
Temporary sales cover needs two explicit transfers: authority at the start and responsibility at the end. Before cover begins, define what the substitute may decide, what requires approval and where material changes will be recorded. At return, reconcile those changes and assign every open commitment to a named person who accepts it.
The reusable record below focuses on account context and decision responsibility, not lead routing or staffing schedules.
1. Set the boundary before handing over the account
“Please look after this account” leaves too much room for interpretation. It might mean answering factual questions, negotiating a revised package or simply keeping the buyer informed. Each requires a different level of authority.
Separate four kinds of action:
- May decide: routine choices the cover can make without further approval.
- May communicate: existing information the cover can explain without changing its meaning or making a new promise.
- Must escalate: decisions requiring a named approver.
- Must not commit: promises outside the cover’s authority, even when requested urgently.
Write boundaries as customer-facing decisions. “Limited commercial authority” is vague. “May resend the current proposal; may not change its price, scope or validity period” is actionable.
Include an escalation fallback. If the approver is unavailable, should the cover contact someone else or tell the buyer confirmation is pending? Silence must not become implied permission.
Distinguish responsibility from access. Being able to edit an opportunity does not establish authority to change a commercial commitment. Conversely, responsibility for a buyer response is not useful without access to the relevant proposal. Check both before cover starts.
2. Capture a baseline, not the whole account history
The cover needs a reliable starting position against which to recognise change. A long collection of historical notes can obscure that baseline.
Record the current offer, the buyer’s latest stated position and obligations already in motion. Include uncertainty explicitly: an unconfirmed target date should not look like an agreed delivery date.
A useful snapshot answers:
- What is offered, and which version is authoritative?
- Who influences the decision, and what have they confirmed?
- What has the team promised to do next?
- Which risks or assumptions could change the next action?
- Where is the supporting evidence?
Point to the proposal, conversation or meeting note rather than copying entire histories. The snapshot explains what matters; the supporting material lets someone verify it.
If the starting position is disputed, mark that before cover begins. Otherwise, an uncertain internal assumption may become a confident customer statement.
3. Worked example: a filled cover-and-return record
This entire worked example is fictional. All names, dates, amounts, limits and commitments are hypothetical. The record illustrates a recommended operating practice, not a product control or customer result. Reuse its headings for your own assignments.
Cover agreement and starting snapshot
- Account and opportunity: Cedar Works; proposed sales-team rollout.
- Returning owner: Maya Patel.
- Temporary cover: Leo Grant.
- Cover period: 8–12 June. Return review: 15 June at 10:00. Leo retains customer follow-up responsibility until return acceptance; if that review is delayed, Priya must confirm an extension or replacement owner.
- Escalation owner: Sales manager Priya Shah. If unavailable, leave requested changes pending and give the buyer a time for the next status update.
- Authoritative offer: Proposal C, sent 5 June, for £18,000 annually. Scope and price remain unaccepted.
- Buyer position: Operations lead Elena supports the proposal. Finance approval and implementation feasibility are unconfirmed. Attendees for the next review are not yet agreed.
- Existing obligation: Maya promised a written answer on data-import feasibility by 11 June. Implementation specialist Sam is preparing it; Leo owns the customer response during cover.
- Known uncertainty: The buyer wants a July start. No delivery date is agreed.
- Evidence locations: Account record, proposal C and the 5 June meeting note.
Delegated decisions and authority limits
- Leo may decide: meeting times, internal follow-up requests and factual updates based on confirmed information.
- Leo may communicate: proposal C and its existing scope, price and conditions, without presenting them as agreed terms.
- Leo must seek approval: price changes, additional scope or extensions to proposal validity. Priya is the commercial approver.
- Leo must not commit: implementation start dates, delivery deadlines or unconfirmed capabilities. Sam’s feasibility assessment alone does not authorise a delivery promise.
- Logging rule: record changed buyer facts, approvals, new commitments and unresolved requests before ending the working day.
Material changes and new commitments
- 9 June — required attendees clarified. Elena said the finance director must attend the next review. Evidence: buyer message dated 9 June. Consequence: the review now requires finance participation and preparation for finance questions; approval remains unconfirmed. Leo arranged a review for 16 June. Maya must confirm attendees and agenda after return.
- 10 June — revised price approved and sent. The buyer requested a discount. Leo escalated rather than negotiating independently. Priya approved £17,400 annually with unchanged scope. Leo sent proposal D and stated that it replaced proposal C. Evidence: Priya’s approval note and proposal D. Status: offered, not accepted.
- 11 June — original answer not completed. Sam confirmed that a sample file is needed before assessing feasibility. Leo told Elena the answer was incomplete and requested the sample. The original commitment was not fulfilled by its due date. New commitment: provide an assessment update by 16 June at 14:00, even if still incomplete. Sam owns the assessment; Leo owns the customer update until Maya accepts it.
- 12 June — earlier start requested. Elena requested an earlier start. Leo acknowledged the request without agreeing. Evidence: meeting note dated 12 June. Status: pending implementation review; no start date committed.
Unresolved items at return
- Sample file: not received. Maya to request it from Elena by 15 June at 15:00, following acceptance.
- Assessment update: due to Elena on 16 June at 14:00. Maya to obtain Sam’s assessment or explain what is still missing.
- Finance review: scheduled for 16 June. Maya to confirm attendees and agenda by 15 June at 16:00.
- Earlier start request: unresolved. Maya to seek an implementation response by 15 June at 16:00 and keep the date unconfirmed unless authorised.
- Commercial status: proposal D is current; acceptance is outstanding. Maya to discuss its status at the 16 June review.
Return acceptance
Maya, 15 June at 10:25: I have reviewed proposal D, Priya’s approval and the change entries. I accept the customer follow-ups listed above from 10:25 today. The revised price is offered, not accepted; no start date is committed. Sam retains the technical assessment. Leo will forward his final meeting note by 11:00; that pending evidence does not prevent my acceptance of these follow-ups.
Leo, 15 June at 10:30: Transfer acknowledged. I will send the final note and make no further commitments unless Maya delegates a specific action.
4. Log changes that alter the next decision
A material-change log should not duplicate every email. Record information that changes what someone should decide, say or do next.
Triggers include a new decision-maker, changed objection, revised offer, promised response, withdrawn assumption or dependency threatening an existing commitment. A routine reminder usually needs no separate entry unless it changes an obligation.
For each event, capture the change, evidence, consequence and next responsible person. Separate the buyer’s request from the team’s response. A requested earlier start is not an agreed earlier start.
Likewise, distinguish requested, approved, communicated and accepted. In the hypothetical record, the revised price received internal approval and reached the buyer. Updating the proposal did not make it an accepted deal.
Logging everything creates noise; logging only completed actions hides emerging risks. Ask whether the returning owner would act differently knowing this fact.
5. Make return a reconciliation, not a reading assignment
“All notes are in the CRM” transfers the task of discovery, not necessarily responsibility. Reconcile the baseline with the current position:
- Identify changes. Compare the starting offer, buyer position and obligations with their current state.
- Check consequential evidence. Review approvals or customer messages for disputed prices, dates or scope.
- Read back open obligations. State who must do what, for whom and by when.
- Accept or reassign each item. Ownership does not transfer merely because someone has returned.
- Record the transfer point. Specify when the cover stops owning ordinary follow-up.
Asynchronous acceptance can work when changes are straightforward and the record is clear. A live conversation is more useful when commitments conflict, evidence is incomplete or an imminent buyer conversation requires judgment.
Acceptance does not mean every uncertainty is resolved. The returning owner can accept responsibility for obtaining an answer while recording that the answer remains unknown.
6. Recover explicitly when the arrangement breaks down
The cover made an unauthorised promise. Preserve what was said and notify the responsible manager. Assign someone to assess the promise and communicate a correction or confirmed position. Do not silently rewrite the note or assume the returning owner will absorb it.
The owner cannot review the record. Agree whether cover continues or another person takes responsibility. Record that decision. Urgent obligations need owners while the broader review waits.
A deadline arrives before acceptance. Escalate under the existing arrangement rather than treating a calendar return date as a completed transfer. If delegated authority has a hard end, the escalation owner must resolve responsibility before then.
Evidence conflicts with the summary. Mark the item as disputed, assign verification and avoid relying on the uncertain claim in a customer response. Correct the summary while retaining the correction history.
The buyer keeps contacting the cover. Pass on new information and identify the active contact. Receiving another message does not automatically renew authority to negotiate.
7. Keep one usable record with appropriate access
Use an agreed shared location accessible to both participants, with one authoritative return record. Scattered private notes make completeness difficult to judge.
Include decision-relevant context, not unnecessary personal information or speculation. Recording that a finance approver must attend is useful; guessing their motives is not.
Request only the access needed for cover and review temporary access when it ends. These are recommended operating practices, not claims that a particular system enforces the boundaries.
Whether you use CRM fields, tasks or a shared document, check that the record can be retrieved during a customer conversation. Check your workspace and current plan for available software support; do not assume a particular workflow exists.
8. Test the next return with a short checklist
Before cover starts, confirm:
- The authoritative offer and buyer position are identifiable.
- Delegated decisions, prohibited commitments and escalation responsibility are explicit.
- Existing obligations have named owners and due dates.
- Both participants know where to record material changes.
At return, check every open commitment for an owner, next action, due date and acceptance status. Count items missing any detail, then resolve those gaps or explicitly assign responsibility for doing so.
The completion test is observable: can the returning owner explain what changed, what remains unconfirmed and which obligations they accepted without reconstructing the conversation history? If not, keep the return handoff open.
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