Changing account contacts: hand over customer promises

Another employee is taking over a customer’s account permanently. For the customer, this should not mean starting their story again. They may be waiting for an agreed document, information or the next step in a current order. Your team must take over those promises with their actual status. Naming a new contact is the beginning. Reliable continuation comes when it is clear what was promised, what is already done and who acts now.

Treat the handover as taking over specific customer work. The new person does not need an uncommented collection of every message. They need outstanding commitments, their sources and their own next task. Unlike temporary cover, responsibility is reassigned permanently here. The process aims at a clear future working state without assuming a later handback to the previous contact.

Define the scope of the new account responsibility

First clarify which customers and types of work the new person actually takes over. The change may concern an entire customer relationship or only a specific current order. A blanket internal announcement can hide that difference. Record the scope so another colleague can identify who owns the next response and which responsibility stays with an existing specialist team.

Agree the actual takeover time. Until then, ongoing processing must remain assigned. Afterwards, nobody should silently assume the old situation still applies. Name individual exceptions expressly where a specific reason requires different treatment. The overview needs no new organisational layer. It should show the actual allocation so a new customer enquiry does not fall between old and new responsibility.

Capture promises from the authoritative sources

Review current open cases using existing records. What specific answer or service has the customer already been promised? Refer to the relevant message, meeting note or confirmed order basis. The new person must be able to read the statement and assign it to the case. The previous contact’s recollection is useful but not complete evidence for every detail of an extensive conversation.

If a basis is missing or contradictory, identify that gap precisely. A response may have been announced without its content being clearly recorded. The successor then needs targeted clarification rather than reconstructing a convincing-sounding promise. Record who can check the missing information and whether the customer needs asking. Unknown content remains visibly unknown until a reliable basis exists.

Keep wishes and promises separate

An expressed expectation is not automatically a confirmed promise by your business. The customer may have requested a delivery date while your employee only promised to check. The handover must preserve that distinction. Record what was actually confirmed and which decision remains open. A wish must not turn into an apparently agreed service during the transfer.

Also distinguish an internal work plan from a response communicated externally. Your team may intend to prepare a document this week without promising that timing to the customer. Both facts can help planning but mean different things. The new person should know which statement they need to honour with the customer or actively renegotiate if it changes.

Establish fulfilment status for each promise

Check what has demonstrably been done for every open commitment. A prepared file has not necessarily reached the customer. A sent response may answer a question while the underlying order continues. Keep these results separate. The new contact can then identify the next work without repeating a fulfilled part or prematurely treating an outstanding service as completed.

Link an asserted completion to its supporting material. Is the sent version, confirmed response or other evidence actually used present in the case? If the connection is missing, retain a specific check. You need no additional document collection if the existing records already contain the evidence. What matters is a clear link between the promise, fulfilment to date and the next step still required.

Turn the handover into a next action

Describe the remaining task so the new person can start. Instead of merely writing quotation open, specify the outstanding customer detail and the internal decision that follows. The case should show what must be done now and what the next step awaits. Changing responsibility does not complete that work. It only makes clear who will own it.

Give the task appropriate timing based on the actual agreement and available processing capacity. A promised response belongs in planning with its real context. A new internal deadline stays recognisable as an internal decision. If the existing timing appears unachievable, that deviation needs a responsible decision. Do not hide it behind a generic handover task that obscures the customer’s actual need.

Preserve professional decision responsibility

The new account contact does not automatically take over every specialist decision in the company. Clarify who checks technical information, a commercial exception or a specific quotation change. The contact should know the route to a confirmed answer. They need the case and identified open question. A broad promise to decide everything themselves is no useful handover basis.

Check the access actually required to information and tools. Can the new person find the case, read the authoritative document and process a task through your existing procedure? Access and responsibility must fit the work and be set up by the responsible people. Announcing a name does not demonstrate available access. Missing permission receives its limited clarification step before the customer waits for an unnecessarily blocked answer.

Test the takeover with a real open case

Ask the successor to explain a current case in their own words. What does the customer need, what was promised, what is done and what action do they now take? This shows whether the documents provide usable context. It is more useful than generally confirming that every file arrived. The new contact need not know every old detail but must be able to continue the actual open work correctly.

Resolve any remaining question within that case. The current document version may be missing or a note may describe an earlier status. Correct that precise reference and check the next task again. Independently clarified cases need not be handed over entirely anew. A limited check protects upcoming work and prevents an extensive collection of unchecked documents being treated as a completed takeover.

Tell the customer clearly about the change

Focus the notice on future cooperation. Who is reachable, through which confirmed route and what does that mean for the current case? Where possible, connect the introduction to a specific response already due. Customers can see their matter has been carried forward. A personal notice need not explain an internal staffing history to make responsibility clear.

State only confirmed contact details and responsibilities. If a specialist contact remains, that can help customers where true. General promises of unchanged conditions or availability also need a real basis. An open order question receives its specific next step. The message then guides customers rather than merely announcing a name without connection to their ongoing work.

Compare new statements with previous promises

Further wishes can arise after takeover. First examine how they relate to what is already confirmed. An additional service is different from following up an existing promise. The new person should distinguish the two before preparing an answer. They can respond warmly and organise the decision without unnoticed expansion or retrospective reinterpretation of the old commitment.

If the customer describes a different agreement from the records, begin clarification at that specific difference. Ask about the point concerned and check available sources. A different memory does not automatically prove either the customer or former employee wrong. The new contact needs a reliable shared basis. Until then, the disputed statement remains open and is not covered up by an improvised new promise.

Give the first response under the new responsibility

Prepare the next response actually due using the transferred case. Use the current document and confirmed fulfilment status. Customers should recognise which question is answered and what work may still follow. The new contact need not recount the entire history. The value lies in understanding the existing context and continuing at the right point.

Record the new result where further processing happens. What was communicated, which decision is newly confirmed and what next task remains? The case then does not stop in a handover document while the actual customer record stays unchanged. The new owner works in the normal process from now on. A permanent separate list of inherited cases makes sense only if it serves a genuinely needed purpose.

End the old assignment cleanly

At the agreed time, check that the new allocation has reached the contact and working routes actually used. An enquiry should not still routinely reach the former person after they have handed over. Assign a specific task where an existing route needs adjustment. This organisational conclusion does not claim automatic forwarding or transfer of personal access.

If a transition question still needs the previous person, name the specific reason and agreed contact route. This creates no unlimited ongoing responsibility. The new person remains responsible for the next processing and organises the information needed. Knowledge can still be used while account ownership is genuinely transferred. The customer need not mediate between two people because the business failed to clarify who owes the answer.

Judge the handover by the customer work

A good result is visible in the open promises taken over: source, fulfilment and next responsibility are understandable. The successor finds their basis and can prepare the next agreed response. Gaps are named and assigned for clarification. This is more reliable than a checked-off meeting without examining whether the next customer contact can actually be handled.

Use concrete experience from the first processed cases to improve preparation. What information was missing, which status was outdated and which direct source reference helped? Add that specific finding to your existing approach. Quality does not lie in the number of handover fields. It lies in a promise being understood correctly, processed traceably and continued with an accurate result under new responsibility.

Keep customer work in shared context

webRichtung core connects contacts and business cases; tasks and deadlines stay linked to their case. Use an open customer matter to check which promise, source and next action your team needs for takeover. Through the existing contact route, discuss your intended process with us. This does not promise automatic detection of every commitment or transfer of third-party access.

Sources and context

Read on 25 October 2026: webRichtung core and Contact. The article describes organisational takeover of ongoing customer work. It sets no employment-law or contractual consequences of a staff change.