Illustrative training scenario. Names, cities, experience and figures in this story illustrate the method. This is not a verified case study or a confirmed result of an XO network member.

Vacation, illness or a day without communication should not turn the client into a hostage of one phone. If the entire story is stored in the agent's memory, a colleague has to figure out the details again, the supplier receives conflicting requests, and the tourist is confused about who is responsible for the next step. The transfer of cases is part of the quality of service, and not an internal administrative ritual.

A good handoff creates temporary but clear responsibilities: what calls need to be handled, what has already been promised, where the deadline is, and what the colleague can decide on their own. At the same time, the client’s data remains protected, and all participants know the boundaries of authority.

Illustrative scenario: Andrey: the question came to the wrong person

Consider this illustrative training scenario: Andrey, a travel advisor from Cherkassy, ​​has been leading individual trips for seven years. He was used to personally monitoring each stage and believed that a detailed auto-response was sufficient. Before his short vacation, Andrey warned clients, but did not collect active cases in one place.

On the first day of his absence, the hotel requested confirmation of a late check-in for a couple who were already on the road. A colleague saw the letter, but did not know whether the time had been agreed upon and whether she had the right to confirm the service. While the team was restoring correspondence, the client received several alarming messages from different channels.

Upon returning, Andrey created a transfer map: he singled out cases by urgency, appointed one deputy, wrote down promises and deadlines, checked access to work systems and, together with a colleague, conducted a fifteen-minute rehearsal. On the next vacation, the transfer issue was resolved without Andrey’s participation, and the client received one clear update.

Transferring a case does not mean forwarding a chat. It is necessary to convey the context, the right to make a decision, and the moment when a colleague should raise the issue higher.

Andrey — character in the illustrative training scenario

First, determine what really needs to be conveyed.

  • Tourists are already on a trip or leaving while the agent is away.
  • There is a deadline for payment, cancellation, confirmation or issuance of documents.
  • The supplier must respond, and the outcome influences the client's decision.
  • There is an open problem, special arrangement or risk of service change.
  • The client is waiting for a selection, a call or another promised result.
  • A new request can safely wait and only needs a fair response time.

There is no need to transfer the entire archive to a colleague. Only active tasks and the minimum required context are transferred. The remaining requests receive a clear status: closed, waiting for the client, can be continued after returning, or redirected to the general queue.

Three priority levels

  1. Red: tourist on the way, safety, check-in, disrupted service or deadline in the next few hours.
  2. Yellow: payment, documents, change or response from the supplier with a specific deadline during absence.
  3. Green: new interest, scheduled consultation or material without a financial or operational deadline.

Color is not an assessment of the client’s importance, but an instruction for reaction time. For each level, pre-define the channel, expected timeframe, and escalation path. If the situation involves safety, money, legal obligation or compensation, the deputy should not guess authority.

One case transfer card

  • Who is the client and what secure communication channel has been agreed upon.
  • The current stage of the trip or sale and the upcoming event.
  • What is confirmed, what is expected and by whom.
  • All data, amount and promise already announced to the client.
  • Next action, exact date and person responsible.
  • Risk, deal-breakers and acceptable plan B.
  • Supplier contacts and case number without unnecessary documents.
  • Limit of the deputy's decision and the moment of mandatory escalation.

The card should allow the colleague to take action, but not reveal more than necessary. Do not send personal documents to the general chat, do not copy payment information and do not transfer passwords. Use worker roles, approved storage, and least-needed access.

One owner, one deputy, one history channel

The client does not need a group of five people where everyone thinks what the other will answer. Appoint a primary deputy, and for critical cases, a manager or an on-duty channel. Record all decisions and updates in one working system, even if the conversation started in the messenger.

“From August 3 to August 9, my colleague Irina is in charge of your booking. She sees the current status and next steps. For travel questions, write to this chat; response during business hours - up to two hours. In an urgent situation while traveling, use the support number from the documents.”

Message to client before absence

Don't promise round-the-clock availability if you don't have it. Separately indicate working hours, a channel for routine questions, and an actual emergency route. Obtain the client's consent to connect a colleague if your processes and the basis for data processing require it.

72 hour transfer plan

  1. 72 hours in advance: unload active cases, deadlines and trips that overlap with your absence.
  2. 48 hours before leave: check the records, close straightforward tasks and appoint deputies.
  3. 24 hours before leave: review red and yellow cases together, check access and notify clients.
  4. Last business hour: update vendor responses, commit new promises, and enable routing.
  5. After the absence begins: do not conduct a parallel covert channel if the matter has already been accepted by the deputy.

Have a short rehearsal

  • The deputy opens the necessary records with his work access.
  • Understands what will happen in the next 24–48 hours.
  • Can explain the current status to the client in one sentence.
  • Knows what is allowed to confirm, change or pay.
  • Sees unsolved risks and plan B.
  • Knows who and through what channel to escalate a critical situation.

The question “is everything clear?” rarely reveals gaps. Ask a colleague to recount the two most risky cases and name the next action. If the explanation is inconsistent with your picture, correct the card rather than relying on additional verbal disclaimer.

How to manage events while away

  • Each new event receives a time, a source, and a short summary.
  • The client receives one consistent update rather than multiple versions.
  • The decision is separated from the assumption and wish.
  • Changes in price, terms or composition of the service are confirmed before the promise.
  • The critical issue is escalated immediately rather than pent up until the agent returns.
  • The completed action is closed, the next one gets an owner and a deadline.

If Andrey periodically replies from vacation, the deputy loses clarity, and the client again chooses the usual personal contact. Exceptions are allowed only at a predetermined level of escalation. In normal situations, the team should have the right to complete the task without the "secret approval" of the absent agent.

Returning a case is also a transfer

  1. The deputy closes what has been completed and highlights only open questions.
  2. The agent reads the change log before the first contact with the client.
  3. The team agrees on who reports the return and what the next step is.
  4. New promises and changes are transferred to the main card.
  5. A short analysis reveals what data or authority was missing.

“I'm back and taking your booking again. Irina confirmed the late transfer and updated the meeting time; Only the hotel's response regarding the crib remains open. I will return to you with it before 16:00 tomorrow.”

Returning with context rather than a formal “I’m back in touch”

Sustainable service metrics

  • Share of active cases with owner, next action and due date.
  • Number of deadlines missed while away.
  • Average reaction time for red and yellow tasks.
  • Number of situations where the deputy lacked access or authority.
  • Number of conflicting messages to the client or supplier.
  • Proportion of cases returned with a full change log.
  • Recurring gaps turned into new record fields or process rules.

Final check before turning off notifications

  • All trips and financial deadlines for the period of absence have been found.
  • Red and yellow cases are personally accepted by the deputy.
  • Clients know the name, channel and real response time.
  • Access is verified without sharing personal passwords.
  • Authority and escalation points are recorded.
  • The auto-reply does not contain unnecessary personal details.
  • A review of the changes is scheduled for the day of return.

Reliable service is noticeable especially when the usual agent is temporarily unavailable. Clear communication maintains continuity, protects data, and gives the colleague the authority to act within clear boundaries. The client remembers not the absence of a person, but the fact that the XO team continued to respond and deliver on what was promised.