Sales continuity during holidays and time off

Two days before the August shutdown at an equipment supplier. A deal that has been open since June finally clears the customer's approval committee, and the procurement manager writes at 4:40 on Thursday afternoon: send the revised quote today and we can sign Friday morning. The rep who built that quote left at lunchtime; the auto-reply points to a date nine days out and the phone is off. He is the only person who knows how the pricing was assembled and which line still had room in it. Two colleagues open the record, cannot find the latest draft, and reply that someone will pick it up after the break. The answer, nine days later, is one line: we went with another supplier.

Continuity through holidays and time off is not about selling on days nobody works. It is about seeing the doors that open on those days before they close again. What follows covers the real cause of deals lost over a break, how to run a pre-leave risk scan, what belongs in a handover file, which coverage model fits which situation, what to tell the customer and when, why most out-of-office replies do damage, how to reset notifications and automations, the rule for contacting someone on leave, how to set targets and forecasts around the period, and why the handover on the way back matters more than the one on the way out.

1Calendar2Risk scan3Handover file4Coverage5Return handover

Absence is not what loses the deal

Work on an absent rep's desk does not stop on its own; it only becomes invisible. Most of the loss comes not from the days nobody worked but from the records nobody could see on those days. The customer does not wait on your calendar — they move on theirs, and when a decision window opens they turn to whoever can answer. The continuity question is therefore not how many people are working but which decisions are visible.

The distinction bites harder in small teams. On a team of ten, one person's absence does not remove a tenth of the portfolio; it closes off everything that person carries. The stage of a deal may well be written in the system, but why the customer is hesitating, who is quietly blocking it internally and where the quote still has flex usually lives only in the rep's head. How to build shared visibility and a clean handover is covered in team collaboration in the CRM.

The pre-leave risk scan: which records to check

Rather than reconstructing the handover list from memory, build it from four queries run a week before the leave starts. First, deals whose expected close date falls inside the period. Second, open deals with activity in the last fourteen days — recent movement is the best available signal that a decision is near. Third, quote expiry dates and contract renewals that land in the window. Fourth, open support tickets and collection reminders coming due.

Every record those four queries surface goes into one of three boxes: hand over, park, or close. Closing is the box teams skip, yet the last week before a break is a natural moment to honestly close deals that have not moved in months, and it visibly shrinks the pile to be handed over. A checklist for deciding what is genuinely still open sits in pipeline hygiene.

The number that comes out of the scan surprises most teams: for a one-week absence, the records that genuinely need covering rarely exceed five. Everything else can wait. Knowing that number in advance turns the handover meeting into a half-hour job; not knowing it leads either to handing over everything or to handing over nothing.

What belongs in the handover file

Holding a handover meeting without writing anything down is close to holding no handover at all; what was said evaporates within two days. The file should not be a separate document — it belongs on the deal record itself, where the covering colleague will actually look. Keep it to seven headings and it gets both written and read.

• Decision map: Who signs, who holds the budget and who argues for the project internally. Write attitudes and positions, not a list of job titles.
• Reasoning behind the last quote: How the price was built, which line can move and which cannot, and why. Without this the stand-in either freezes or concedes far more than needed.
• Next step and its date: What the next contact is and when it happens. A vague note saying following up tells the person taking over nothing at all.
• Red lines: How far the stand-in may go alone and which decisions must wait. If the boundary is not written, the deal either stalls or someone promises something that cannot be walked back.
• Open commitments: Promises already made to the customer and not yet delivered, with dates. A small forgotten promise is the most expensive conversation waiting after the break.
• Communication preference: Which channel, what time of day and what tone this customer expects. The wrong channel delays even the right message.
• The fragile point: Whatever is most at risk in this relationship right now — a fresh competitor conversation, an unhappy end user, a late delivery.

Rather than writing this from scratch every time, tie it to a template. Without one, handover quality varies by person, and experience says the sloppiest handover lands on the most critical account. The method for turning individual knowledge into a shared standard is in process documentation and SOPs; a leave handover is the shortest and most concrete application of that idea.

Coverage models: buddy, pool, or watch only

Who takes over gets debated far more than what gets written down, and the debate usually starts from the wrong question. The right question is not who is available but what decision could arrive on this account within a week. If a decision is likely, you need someone with authority; if not, someone watching is enough. The five models below cover most teams, and each has its own breaking point.

Model	Works best when	Breaking point
Named buddy	Few large, relationship-driven accounts	The buddy is off the same week
Shared pool	Many small and similar deals	Everyone looks, nobody advances it
Manager covers	Short absences, critical deals	The manager's own queue stops moving
Watch only	Long-cycle, currently static deals	Urgency arrives with nobody able to decide
Deliberate pause	Periods when the market is closed too	Trust erodes if the customer was not told

Once the model is picked, one technical job remains: the stand-in has to be able to see and to write. Someone without access cannot advance a deal even after reading the handover file — no notes, no resending the quote, no messaging the customer from the record. Granting temporary access for the period and revoking it on return should be a written rule on the roles and permissions side, not a favor asked of the manager before every holiday.

What to tell the customer, and when

The cheapest part of continuity is a single message sent to the customer in time, and it is also the part most often skipped. Before the leave begins, every customer with something open gets three sentences: I am away between these dates, this colleague is covering your account and knows your file, and here is how to reach them if something is urgent. Those three sentences pre-empt most of what would otherwise go wrong during the break.

The message should do more than name dates. If a decision is pending, say when it will land; if it will slip, give the new date outright. What frustrates customers is rarely the delay itself — it is discovering the delay on their own. How the language of promising and delivering works in practice is covered in managing expectations, and a holiday period is where that language gets tested hardest.

Why most out-of-office replies do damage

The standard advice is simple: set an out-of-office before you go. In practice most auto-replies do harm rather than good, because they tell the customer exactly one thing — nobody is here for nine days. A buyer whose decision window is open does not wait after reading that; they look for an alternative or shelve the project. The problem is not the auto-reply itself. It is what the auto-reply says.

A damaging reply describes an absence. A useful one describes a route: who the topic falls to, through which channel, within what response time, and how urgent is defined. On instant channels such as WhatsApp this matters even more, because tolerance for waiting there is far below what email allows; the reply should work on an hourly basis and state clearly at what point a human takes over. Setup details are in WhatsApp auto-reply.

Describe the route, not the absence

A practical test: if your return date appears before the covering colleague's name, the message is written wrong. The customer is not wondering when you come back; they are wondering when their own work moves. The same rule applies internally — the note to your team should not read I am on leave but if a decision lands on these three accounts, go to this person. The second version carries information. The first is only an excuse.

What notifications and automations do while you are away

Leave periods are when automations quietly break. Rules that assign tasks to the absent person keep firing, reminders stack up, and two hundred notifications wait on the return day — with the three genuinely urgent records buried inside them. Worse, some customer-facing flows go unanswered: the system offers an appointment, nobody sees the reply, and the customer works out they were talking to a robot.

Three things need adjusting. First, the assignment rule for tasks falling inside the period: if tasks are assigned to a role rather than a person, coverage happens by itself. Second, customer-facing sequences either pause against the holiday calendar or route replies to the stand-in. Third, a single catch-up task placed on the return date; without it, the first day back disappears into the inbox. The logic of generating tasks from templates automatically is covered in task templates.

When is it fair to call someone on leave?

A leave plan does not schedule someone's absence; it schedules which decisions will refuse to wait for them.

Every team has an unwritten rule about this, and because it is unwritten it does not work: nobody wants to intrude, so either nobody calls or everybody calls about everything. Make the rule concrete. Which size of deal, at which stage, for which class of customer earns a call to the person on leave, through which channel, and with what expected response time. Everything else waits or gets decided by the stand-in.

Written down, the rule relieves both sides. The stand-in does not hesitate, because the legitimate cases are known, and does not sit on something for three days out of politeness. The person on leave does not have to re-enter work every time the phone buzzes. If you want the same logic enforced by the system rather than by manners, escalation automation handles who steps in and when.

Setting targets and forecasts around the period

The first instinct is to lower the target. In most teams that becomes a self-fulfilling prophecy: the month is declared dead, the team behaves accordingly, and the month duly dies. Shifting the calendar works better than shifting the number. Pull the activity load of the affected weeks forward, push close expectations past the period, and keep the quarter total intact. The team then prepares for a compressed month rather than an empty one.

There is an unexpected but defensible choice here: concentrating leave usually costs less than spreading it. Running six weeks at half strength loses more opportunities than closing entirely for one week, because a half-staffed stretch produces uncertainty that neither the company nor the customer can plan around, and nobody quite knows which work is still moving. Picking a single week when the wider market slows too, and having everyone off at once, gives customers one closed window they can plan around.

The forecast needs its own correction. If close dates on deals falling inside the leave period are not pushed out as a group, the quarterly forecast inflates and the period ends in an unavoidable argument about variance. Pulling close dates back to reality is not the same as lowering the target: one makes the forecast honest, the other lowers what you expect of the team.

The return handover, and making the plan stick

The most skipped step is the return. The handover on the way out gets a meeting; the handover on the way back usually gets nothing. The rep dives into the inbox and learns in fragments, over several days, what the stand-in did. Yet the return handover matters more, because that is where the new promises, the changed stages and the freshly learned facts are.

A practical rule: the first two hours of the return day go to reading the handover, not to customer contact. If the stand-in left a one-line note for every contact made during the period, two hours are plenty. If they did not, two days will not be enough. Defining that note-leaving habit as part of the handover file is the cheapest investment available in making returns painless.

To make the plan stick, close every leave period with three questions: which work could not wait but had to, which piece of information was missing from the file, and which notification was noise. Fold the three answers into the template and the next leave plan improves without anyone redesigning it. The same logic applied to key-person risk and larger disruptions is covered in the business continuity plan.

One warning from the other direction: a team whose continuity rests on one person's willingness to stay reachable has not really granted the leave. A rep who keeps the phone on through the holiday does not rest, comes back slower, and the bill for that arrives mid-quarter. How motivation survives sustained pressure is covered in burnout in sales teams; a well-built leave plan is the cheapest preventive measure available.

Continuity through time off is, at bottom, about knowledge living on the record rather than in a person. When deal notes, handover details, task templates, permission settings and customer messages all sit on the same record, a stand-in taking over an account does not start from zero. Rocketly keeps them in one place — open a free account and build your own coverage plan.