Black Friday customer support: a staffing and returns plan

Your Black Friday plan has enough agent hours on paper. By mid-afternoon, chat is backed up, nobody can approve an address change before dispatch, and the refund owner is off shift. The total headcount was only part of the plan.

Black Friday–Cyber Monday customer support planning should connect the sales forecast to human work, schedule that work when it arrives and make decisions available across support, fulfillment and finance. It also needs to cover the delivery and return waves after the promotion ends.

A recent Shopify Community preparation discussion raises promotion testing and address changes before parcels leave. The thread includes service-provider perspectives, not verified industry statistics. Use those questions to examine your own operation rather than copying its assumptions.

What data should drive the staffing forecast?

Use your own order volume, human case volume, arrival times and handling effort. Distinguish a case from a message: one customer issue can produce several replies. Decide whether follow-up work is included in the case’s handling time so it does not disappear or get counted twice.

Break out work that does not track orders closely, such as presale compatibility questions or an existing technical backlog. Segment by channel, language and complexity where those differences change staffing.

Gorgias describes a forecasting approach based on orders, contact volume and actual team capacity. The useful principle is to connect demand and capacity. Its example benchmarks are not a substitute for measuring your products and team.

Use a recent ordinary period and a relevant peak. A new product, shipping region or promotion can change the case mix, so show a range of assumptions instead of treating last year’s ratio as guaranteed.

A worked example: orders to handling hours

For order-related work, start with forecast orders × human cases per order + existing cases to clear. Multiply by active handling minutes per case and divide by 60 to get handling hours. Add separately forecast work, such as presale questions, if it is outside that case ratio.

All numbers below are hypothetical planning inputs, not industry benchmarks, CXharbor results or staffing recommendations. The example estimates human handling work across a four-day promotion.

Input or calculation	Illustrative value
Forecast orders	1,400
Human cases per order	0.30
New human cases	1,400 × 0.30 = 420
Existing cases to clear in this period	60
Total cases to handle	480
Total active handling time per case	12 minutes
Required active handling hours	480 × 12 ÷ 60 = 96

The 0.30 assumption counts work that needs a human after genuinely completed self-service. The 12 minutes includes reading, replies, notes and related follow-up. It excludes passive time waiting for a customer. If your reporting counts these differently, adjust the inputs before using the calculation.

Measure presale demand separately if it is not represented in the ratio. Likewise, identify return work likely to arrive after these four days; do not assume it has been staffed just because the original order is in this forecast.

How do handling hours become shifts?

An eight-hour shift does not provide eight uninterrupted hours of case handling. Allow for breaks, training, meetings and necessary availability between contacts.

For illustration, assume 25% of each shift is unavailable for queue work and plan active handling for 80% of the remaining time. These are chosen assumptions, not recommended industry targets:

8 hours × 0.75 × 0.80 = 4.8 planned handling hours per shift.

The example needs 96 ÷ 4.8 = 20 shifts, averaging five shifts per day across four days. That is a workload estimate. It does not establish that five people can cover every hour, language or live-channel service target.

Check sensitivity. If the human-case ratio becomes 0.40 with other assumptions unchanged, the plan contains 620 cases, requires 124 handling hours and rounds up to 26 shifts. A relatively small change in an assumption can materially change the roster.

Map the shifts onto actual arrival times. Review language coverage, product skills, breaks and supervisor availability. Phone and live-chat demand require additional attention to simultaneous contacts and waiting; a daily average cannot establish a service level.

Which decisions need coverage as well as agents?

A queue can stall even when frontline capacity is available. Name the decision owner, executor and backup for the events most likely to cross team boundaries.

Event	Decision or handoff to prepare
Promotion behaves differently from the published offer	Who confirms the intended terms and authorizes correction
Address-change request before dispatch	Who checks whether fulfillment can still stop or edit the shipment
Promised shipment cannot be made	Who approves the applicable customer options and communication
Returned hardware needs inspection	Who receives it and supplies findings to the case owner
Refund exception or dispute needs action	Who decides and who executes within the relevant deadline

Have each owner state when they are available and how a replacement is reached. Give the customer a useful update time that the team can control, not an invented delivery or approval promise.

For covered US transactions, the FTC’s merchandise-order rule requires a reasonable basis for advertised shipment timing and consent to a shipping delay or a refund for unshipped merchandise when the promise cannot be met. This is about shipment obligations; do not automatically apply the same description to every carrier delay after dispatch.

When should Black Friday support planning start?

Work backward from the first customer-facing promotion. Leave time to collect demand data, confirm capacity, prepare the knowledge pack and rehearse complete cases. If you need a new provider or language team, include selection and onboarding before rehearsal. Use those dependencies to set your start date; a universal number of weeks cannot account for an untrained team or an unresolved return route.

What should you test before the promotion?

Walk through the actual offer, its product restrictions and customer messages. Have support explain a failed discount, an out-of-stock choice, a cancellation request and a delivery question using approved information.

Check whether the person changing fulfillment can act before the parcel leaves. Check whether the return instructions send an item to a location that can actually process it. These are useful rehearsals even if you have no new software to launch.

Use the outsourcing onboarding checklist for temporary or external agents. Confirm what they have been trained to handle before assigning them to a peak queue. Put the AI handoff conditions through the same rehearsal if automation is involved.

Plan the return wave before reducing coverage

Keep a forecast for post-promotion delivery enquiries, setup questions and returns. Many of those delivery enquiries can be prevented with proactive order-status updates. Separate each platform’s deadlines from your internal targets. Our guides to TikTok Shop return clocks and Shopify return settings explain why a single generic refund timer is insufficient.

During the event, review arrivals against the forecast, unresolved waiting, missed commitments and the cases blocked on another team. Adjust the roster and decision coverage together. Faster acknowledgment alone will not clear a stalled inspection queue.

Afterward, compare the original assumptions with actual case mix, handling time and repeat work. Keep the version of the forecast you used so the next campaign starts from what happened, rather than another guess at how many agents feel sufficient.

If you need external peak coverage, discuss the workload with CXharbor using your promotion dates, forecast range, channels and coverage gaps. Include the return period in the same brief.