A merchant goes into peak with a support inbox that normally receives forty messages a day. In the third week of November it receives three hundred.
She reads them all. The overwhelming majority ask where an order is, whether something will arrive before a particular date, or why a code did not work. Perhaps a dozen need her judgement.
She spends the most commercially important month of her year typing tracking numbers, and the twelve messages that needed her attention wait behind two hundred that did not.
The first failure: the volume is predictable and the preparation is not
Every merchant knows peak is coming and most prepare stock, marketing and logistics while leaving support to be handled by working harder in the moment.
The second failure: order status dominates everything
The single largest category by a wide margin. Every one of those answers exists in a system, and almost none of them are exposed anywhere a customer can reach.
The third failure: the delivery deadline is not published prominently
Order by this date for arrival before the holiday. Its absence generates enormous anxious contact and, worse, orders placed in hope that turn into complaints.
The fourth failure: the deadline is published once and forgotten
It needs to appear on the product page, the cart, the confirmation and in every answer given during December, rather than in a single banner nobody reads twice.
The fifth failure: discount codes multiply the problem
Peak promotions create exclusions, minimums and expiry questions at exactly the moment support is least able to answer them, which is the ground in discount code questions and why they backfire.
The sixth failure: carrier delays become your problem
Customers contact the merchant rather than the carrier, and during peak the delays are constant. Having a stated position on this prepared in advance saves hours a day.
The seventh failure: temporary staff arrive too late
Hiring, onboarding and training take weeks. Somebody starting in mid November is competent in December and gone in January, which is a poor return on considerable effort.
The eighth failure: the product questions still arrive underneath
Fit, compatibility and suitability do not stop during peak, and they are the ones that actually convert, which is the pattern in product question volume that never reaches you.
The ninth failure: the returns wave is not planned for
January arrives immediately afterwards with a different high volume category and a team that has just worked a month of long days.
The tenth failure: the gift questions are ignored
Gift receipts, extended returns for presents, delivery to a different address and whether the price will be visible. Predictable, seasonal and rarely answered anywhere.
The eleventh failure: nothing is captured for next year
The same questions will arrive in eleven months, and almost nobody records the list while it is in front of them.
The twelfth failure: the merchant does the work herself
The owner spending peak on tracking numbers rather than on trading is the real cost, which is the seasonal pattern in holiday season enquiry surge.
The fix: expose the answers before the volume arrives
An assistant that states the delivery deadline, explains despatch times and where the tracking email comes from, sets out the discount terms that usually explain a failed code, and answers the gift and returns questions handles most of the two hundred so the merchant can handle the twelve. It does not see live order data, so a specific order still comes to her, but it arrives with the order number already attached. That preparation is exactly what the black friday inbox problem and how to plan for it describes. Start at try, see the integrations, features, and the sector view sits under ecommerce.