A support team of four plans its summer. Two people take leave in the same fortnight, which was agreed months ago and is entirely reasonable.
One of the two remaining is ill for three days of it. The last person standing handles a normal week's volume alone, badly, and everything that is not urgent is deferred.
The person returning from leave finds a backlog, a set of unhappy customers and no record of what was promised to whom. The team recovers over three weeks and the same thing happens at Christmas.
Step 1: accept that a small team has no slack
Planning as though four people are always available is what produces the failure, and there is no rota that solves an arithmetic problem.
Step 2: document the answers before you need them
The actual cover. Somebody covering unfamiliar ground needs the answers written down, which is the discipline in training a small support team without a manual.
Step 3: automate the repetitive volume permanently
Not as a holiday measure. A team whose routine questions are handled has considerably more slack every week, not only in August.
Step 4: agree a priority order in advance
What gets answered first when capacity halves, decided calmly beforehand rather than by whoever is most stressed on the day.
Step 5: set a different response commitment for the period
Stated publicly, since a slower promise that is kept is better than a normal one that is missed.
Step 6: brief the rest of the business
Sales, operations and everybody else should know the team is short, so nothing else is added during the same fortnight.
Step 7: keep a record of what was promised
So the person returning inherits commitments rather than mysteries, which is the main cause of the three week recovery.
Step 8: protect the person covering
Explicitly, since somebody working alone through a difficult fortnight without acknowledgement is somebody who leaves.
Step 9: plan for the sickness as well as the leave
Leave is known months ahead and illness is not, and a plan that only survives planned absence is not a plan.
Step 10: handle the weekend and holiday periods separately
Which is the coverage problem in weekend and holiday cover questions.
Step 11: consider coverage across time zones deliberately
Which helps considerably and brings its own issues, as set out in hiring support staff across time zones or not.
Step 12: review what actually happened afterwards
What broke, what held and what was deferred, briefly, while it is fresh, since this is how the next period is better.
Step 13: let the team improve the answers continuously
Since they know where the gaps are, which is the argument in why your support team should help train the chatbot.
Step 14: stagger the leave where possible
Agreeing at the start of the year that two of four cannot be away simultaneously is unpopular and considerably kinder than the fortnight that results from allowing it.
Step 15: make the cover permanent rather than seasonal
An assistant handling the repetitive volume every week means a fortnight with two people away is a busy fortnight rather than a crisis, and the person returning from leave finds a queue rather than a wreckage. Set it up through install the widget and train your bot. Start at try, and the sector view sits under small business.