Seasonal surges in enquiries: prepare before the inbox starts smoking
Prepare for seasonal enquiries by identifying case types, useful information, routing, necessary data and honest waiting times.
Article language: English

In this article
Before the season, a company puts the finishing touches to its campaign, new offer and photographs. It prepares the inbox in the traditional way: everyone will reply faster. Adrenaline works for the first two days. On the third, a customer sends a second question because the first went unanswered. The inbox begins to create its own demand, as if it decided the campaign had been too modest.
A predictable surge requires preparation for the kinds of cases, the information received and the team's capacity. Better descriptions can prevent some enquiries. Others must quickly reach someone with the right expertise. Still others need an honest indication of the wait. A shared contact address does not itself create more capacity to reply.
Imagine a fictional company supplying equipment for events. Before the autumn season, questions about availability, dates and unusual combinations increase. Not every case needs a designer, but not every one can be closed with a prepared paragraph. Preparation begins by recognising the difference, before the team opens another tab marked urgent.
Count the work the questions actually bring
Look at the previous peak or the most recent comparable period. Separate cases by what an answer needs: simple information, an availability check, agreement on scope or a decision by the responsible person. A division by message subject is not enough if one case in a category takes a moment while another needs three people's input.
GOV.UK guidance on organising support recommends separate estimates of enquiry numbers by channel and of enquiry types, as well as using historical data. This is a useful planning reference. It does not provide a universal headcount for every company: cases differ in scope and difficulty.
For an exercise, assume one hundred messages. Eighty need five minutes each and twenty need half an hour each. The total effort is one thousand minutes: four hundred for the first group and six hundred for the second. A minority of cases accounts for most of the work counted this way. Message count alone does not show which expertise will run short first.
Do not divide those thousand minutes by the number of people in the company without checking. Some may lack the expertise for difficult cases or be delivering work at the same time. Record the time the appropriate people actually have available during the period. Only then can you compare the expected inflow with real response capacity.
This is a simplified calculation of active effort. It excludes waiting for agreements, breaks and parallel work. It still helps ask the right question: who can decide difficult cases, and when? If all of them await one person, moving another employee to replies may not unblock decisions.
Separate case counts from contact counts. One person may submit a form, call and return via chat because they do not know whether the first request arrived. Record that return without multiplying the customer's underlying needs. This helps show whether the peak consists mainly of new cases or uncertainty around cases already started.
Record when enquiries arrive as well. A weekly average can hide a spike after a campaign or just before an order deadline. Compare it with the actual availability of people able to answer. You do not need an advanced tool to see that most questions arrive while the person approving scope is running events outside the office.
Zendesk WFM forecasting documentation describes adjusting expected inflow for special future events such as campaigns. This is a specific feature of that tool and a reminder that past patterns alone do not describe a change the company plans. State your assumptions and compare them with reality later. If you plan to use a model, see testing an AI enquiry forecast over time (in Polish). The comparison should include information available before the forecast period, including the campaign announcement.
Some of the queue forms before the form
Read common questions alongside the offer page. Is the date stated for the right scope? Does “available” mean a set is free or that a proposal can be prepared? Must a customer write merely to discover what materials are needed? These are places where information on the page can reduce uncertainty before contact.
Do not move all support into a long FAQ. Good questions and answers on a service page (in Polish) complement the offer rather than repeating it elsewhere. If almost everyone asks about timing, the information may belong beside service selection, not at the end of thirty expandable answers.
Prepare a seasonal message that names the situation and action. It may state the enquiries accepted and when the stated response time applies. “We will reply within two working days” is not a promise of a completed quote if further agreement is needed. A specific explanation can reduce repeat contacts caused by unclear expectations.
The form should collect information actually needed for the first decision. In our example that means the event date, place and type of set. A full event script is unnecessary if the team must first check basic availability. At the same time, an overly broad “describe your need” field can produce a series of follow-up messages.
Give the customer a way to add information to an existing case, if support offers one. A separate new-enquiry form is not always the right route for correcting a date. Review how the customer recognises an existing request and what the team does with a later message. Without that, a small addition can start a second independent queue.

Walk through a short enquiry. Can the person receiving it identify the next step? If one piece of information is missing, check whether the request for it is visible and understandable. The test should cover the route to the team, not merely field validation. A correctly submitted form with an unhelpful scope still does not speed a decision.
In an internal service catalogue (in Polish), identify who handles each kind of need. The person at intake need not know the whole back office, but should know where to direct a case. At the seasonal peak, guessing who should receive each question can become a full-time job of its own.
Not every case should start again
The team sees a long queue and opens many cases at once. Each gets an initial answer, but few reach a decision. Customers wait, employees return to context and the count of open tasks rises. Too much work in progress (in Polish) helps identify this problem outside enquiry handling too.
Before the peak, define a signal for changing the handling approach. It might be the age of unresolved cases or an inability to meet the promised response stage. A signal alone is not enough: assign responsibility for changing the message, narrowing accepted scope or moving work. Overload then has a recognisable response instead of another appeal for greater effort.
Agree what it means to hand over a case and who confirms receipt. Forwarding a message to a designer should not end the intake person's responsibility if nobody knows whether the task was noticed. The status must distinguish waiting for the customer, an internal decision and an answer ready to send.
Prepare a few working replies, but mark where a decision is needed. A template can list required information and explain the next step. It should not automatically confirm a set's availability or a delivery date. The person replying must distinguish sentences they can send at once from those requiring a check of the case.
Use explicit task-related grounds for priorities. The event date may matter, but not every message containing “urgent” requires the same response. The team should be able to explain the order without a hidden auction won by whoever sends the most reminders.
Be careful with “number of replies per day”. It may reward quick forwarding or closing simple questions while difficult cases age in the background. Review measures that produce unwanted behaviour (in Polish) before the season. Also measure progress toward a useful decision and repeat contact about the same gap.
If considering AI for initial routing, start with tests for classifying enquiries (in Polish). An ambiguous case needs a route to a person. Sending a case quickly to the wrong queue may look like a saving only from the first inbox's perspective.
Compare the change with a simpler option: a clearer description, separation of two question types or a short instruction for the team. The choice between building, buying and manual handling (in Polish) should concern the same work. A seasonal rush is not a good reason to introduce a new system without testing its hardest exception.
At Aeneia Design, a few typical enquiries, the current form and a description of subsequent handling can be a starting point. Page design can remove some uncertainty at intake; decisions about people's availability and how cases are resolved need an owner in the company.
Run a small trial before the large queue starts
Recreate several enquiries arriving close together. Include a simple information request, an unusual scope, an incomplete date and a reminder about an already open case. Check whether the team identifies the need and next action. Do not judge the trial solely by the speed of the first message.
Add a case where a simple answer is on the site but the customer cannot find it. Ask where they looked. A link beside date selection may be needed instead of another FAQ paragraph. Such observations help remove the cause of contact without making the visitor read the entire site.
Include the absence of the person who usually decides exceptions. Is there a substitute or a clear waiting message? If not, name the limit before the campaign. State which questions the substitute can decide alone, which must wait and how the customer recognises that state. Another contact channel cannot provide missing expertise, though it may give that expertise more tasks.
Once the season starts, compare assumptions with inflow and case times. Look for the reason for a change: a new subject, missing information, a longer agreement or more repeat contacts. Each leads to a different correction. A rise in message count alone does not say what to change on the site or in the workflow.
When changing the stated response time, check every active entry point. The site text, form confirmation and team message should refer to the same scope. If the change concerns new enquiries only, say so. Otherwise a customer waiting on an existing case may believe their deadline has just moved too.
After the peak, keep a short note: what relieved support, where decisions stalled and which message prompted questions. Return to it before the next season. The inbox may still be full because the company has plenty of work. It need not also spend time producing its own reminders.








