Hand over a sales case without losing commitments

Separate contact transfer from case continuity

A contact list is not a case handover. The new owner needs the customer’s goal, options being considered, commitments already made, open questions and next contact date. Summarise the information needed for the next decision and link to its evidence. Pasting every email into a long note transfers the reading burden without preserving priorities. Keep personal impressions separate from observable facts and avoid including unrelated customer information merely because it is available.

Define a small, action-oriented handover record

Include case ID, outgoing and incoming owners, effective change time, customer notification status, next action, deadline, unresolved points and reference documents. Record when the incoming owner accepts the case. In sample H-031, a Friday specification response remains due on Friday even if the person changes on Thursday. A handover should transfer an existing obligation, not silently restart its clock. Make any renegotiated date explicit and explain who agreed to it.

Distinguish external promises from internal plans

“We will answer by Friday” is a customer commitment; “ask engineering on Thursday” is an internal plan. Give them different fields or record types. Add the time, recipient and message reference for external promises. A provisional delivery estimate should not turn into a firm promise simply because it appears in a date column. Mark uncertain statements for review. This helps the incoming owner explain the situation accurately instead of repeating assumptions as confirmed facts.

Ask the incoming owner to rehearse the next action

Do not define completion as sending a link. Ask the incoming owner to explain the next call or email: what they need to ask, what they will send and whose approval is required. Check access to the referenced documents as well. A valid-looking link that only the previous owner can open does not support continuity. For an urgent case, perform this review before the effective handover time and nominate a backup if the incoming owner is unavailable.

Handle messages arriving after the owner changes

Messages may continue arriving through the old channel. Define a forwarding route, a transition period and a customer-facing owner-change message. Forwarding alone does not confirm that the new owner has picked up the work. Record the most recent responder and next owner so both people do not send conflicting answers. Transfer access through the service’s normal permission model instead of sharing the outgoing person’s password or leaving work dependent on their account.

Review remaining obligations after the change

On the next working day, review unanswered questions, undelivered documents and overdue commitments. When something is missing, request that specific detail rather than returning the whole case to the previous owner. Categorise problems such as an uninformed customer, an unclear accepted quotation or conflicting delivery dates. Those patterns tell you which handover fields need improvement. Measure whether the new owner can continue the work, not merely how many records were reassigned.

H-031: verify the next contact on handover day

In H-031, ownership changes Thursday afternoon while a drawing response is promised for Friday morning. The incoming owner opens the drawing and verifies the internal reviewer and deadline before accepting. Missing document access is a handover gap to resolve, not a reason to mark the transition complete. On Friday, check for new messages through the old route. Internal acceptance and customer awareness are separate facts. Record the new contact route and review the case after the response so a discovered gap improves the next handover rather than becoming another hidden exception.

Choose a tool and budget around the actual workload

A shared document may be sufficient when handovers happen only occasionally. A case register becomes useful when several people transfer work regularly or need absence coverage. Compare editor access, backup permissions and document ownership alongside subscription costs. Include the effort required to remove obsolete access after the transition. Before adding another notification, assign one person to confirm acceptance: a large audience is not a substitute for a clear receiving owner.

• Build an Airtable enquiry tracker: intake, owners and follow-up states
• Hand over automation accounts, connections and unfinished work
• Pause, hand over or cancel Make: scenarios, connections and billing