Black Friday Customer Support for Shopify Stores: 2026 BFCM Plan

Do not build your BFCM staffing plan from a generic ticket forecast. Your own store data gives you a better starting point.

Pull the same sales period from last year if you have it. Review orders and tickets. Check first response time, handle time, and hourly demand.

Group tickets by reason. Use simple ticket groups. Include order status, discounts, payments, shipping, returns, cancels, and damaged items.

Then look for the hours when demand changed. Email may rise after a campaign. Chat can rise during active shopping hours.

If this is your first BFCM, use another busy sales period. A product launch or major sale can provide a useful baseline.

Your forecast does not need to be perfect. It should expose a staffing gap before the rush.

Use your contact rate to forecast demand

A simple planning formula is:

Planned support contacts = planned orders × past contact rate

Suppose you expect 4,000 orders. Past data may show a 12% contact rate. That gives you about 480 contacts.

Next, forecast the work behind those contacts:

Required handling hours = planned contacts × average handle time ÷ 60

If average handle time is six minutes, the work takes 48 handling hours. That is not your full staffing schedule.

You still need room for breaks and team updates. Add time for handoffs, live channels, and follow-up work. Add that room based on your setup.

Do not use one average for every channel. Use channel data when demand differs. Chat and phone need more immediate staffing than email.

The safest plan starts weeks before Black Friday. A rushed setup often creates more work during the sale.

Eight weeks before BFCM

Pull last year's ticket and order data. Build your demand forecast and list the support gaps.

Confirm which channels matter most during the sale. Do not add a new channel just because BFCM is coming.

Decide whether your current team can cover the expected hours. If not, start arranging overflow or outsourced staffing now.

Review your highest-volume ticket reasons. Those groups should shape your macros, help center, training, and ticket views.

Four weeks before BFCM

Lock the rules that shoppers and agents need. Support cannot work from rules that marketing is still changing.

Confirm discount rules, shipping cutoffs, return windows, exchange rules, and cancel limits. Add stock and backorder guidance too.

Write clear answers for offer exclusions and discount stacking. Decide what agents can fix without asking a manager.

Confirm holiday schedules with your warehouse, vendor, and 3PL. Agents need to know when each partner can answer a handoff.

If you use an outside support partner, complete the main briefing now. Give them time to learn the offer and test access.

Two weeks before BFCM

Run scenario-based training. Do not limit training to reading a policy page.

Practice a discount that fails at checkout. Test an address change after an order enters shipping.

Practice a sold-out item and delayed parcel. Add a damaged order and refund request. Include one case that needs a manager.

Test every tool agents will use. Test Shopify and your helpdesk. Test tracking tools, returns apps, and 3PL systems.

Check permissions before the sale. Agents need the right access. A reply without an order fix creates more back-and-forth.

Seventy-two hours before Black Friday

Freeze nonessential support changes. Avoid major helpdesk changes before BFCM. Rebuild views or routing only when there is a clear need.

Confirm the final sale details with marketing. Confirm shipping and fulfillment schedules with operations.

Send the final roster and handoff contacts to the team. Make ownership clear for each shift and channel.

Check your saved replies and self-help answers one last time. Remove anything that conflicts with the live offer.

BFCM support problems often start outside the inbox. A vague sale or shipping promise can create many avoidable questions.

Shopify recommends updating store policies before seasonal sales. Your support team should work from the same rules shoppers can see.

Start with the offer itself. Agents need the exact discount, dates, and exclusions. They also need stacking rules and affected products.

Then confirm shipping promises. State order cutoffs and packing times. Add delivery forecasts and known limits by region.

Review returns and exchanges next. A BFCM offer may need different terms from your normal setup.

Make order-change rules clear too. Define when agents can cancel an order. Set rules for address and item changes too.

Finally, define stock rules. Decide what happens when an item sells out after purchase or becomes delayed.

Keep these rules in one source agents can trust. Keep the answer in one place. Do not make agents search Slack, email, and old macros.

For a broader process, see our support SOP guide.

A BFCM queue should not treat every ticket as equal. Some issues can block a sale or create a time-sensitive order problem.

Create a small set of priority groups. Keep them simple enough for agents to use under pressure.

Level 1: action needed now

Use this group for time-sensitive issues. A delay can make the problem harder to fix.

Examples include checkout failures and broken discount codes. Payment issues during the sale also belong here. Include urgent order edits before shipping begins.

A suspected payment-security issue also belongs here. Route it to the right person. Do not make the shopper repeat the story.

Level 2: order or delivery problem

Use this group for orders that need investigation. Examples include missing parcels, damaged items, wrong items, and stalled shipping.

Give agents a clear path to your vendor, warehouse, or 3PL. Include the details that partner needs to act quickly.

Order number and SKU can reduce wasted messages. Tracking numbers and screenshots can help too. Build those fields into the handoff process.

Level 3: common questions

Use this group for questions that often have a standard answer. Common examples include WISMO, return rules, product details, and shipping forecasts.

These tickets are strong candidates for self-help, macros, or safe rules. Keep a human path available when the standard answer does not fit.

Shopify agents often need to own shipping, refunds, and replacements. They may also own order edits and tracking.

Put that ownership in your BFCM runbook. Agents should know which actions they can take without approval.

There is no useful universal rule for tickets per agent during BFCM. Store complexity, channels, tools, and policy limits change the answer.

Start with your team's actual capacity. Use handled tickets and average handle time. Check resolution quality from normal busy periods too.

Then compare that capacity with your forecast. If demand exceeds that limit, split the gap. Remove safe repeat work with rules and add people where needed.

Do not wait until the queue grows to make that choice. Short-term staffing still needs access, training, and clear rules.

Check your normal work days against the BFCM campaign. A weekend sale may need weekend support.

That does not mean every channel needs full staffing all day. Match staffing to expected demand and the promise shown to shoppers.

Need flexible capacity? Read how to scale Shopify support without a full-time hire.

You can also review our Shopify support outsourcing service for managed staffing options.

Macros should save time without turning replies into scripts. Start with the questions your forecast says will repeat most.

Useful BFCM macros may cover:

• Discount code troubleshooting.
• Sale exclusions.
• Shipping cutoffs.
• Order status and tracking.
• Address changes.
• Cancel requests.
• Return and exchange rules.
• Damaged or missing items.
• Backorders and stockouts.

Write the decision rule before the reply. Agents need clear rules for each macro. They should know when it does not apply.

Add the next action inside the process. A WISMO reply may need a tracking check before the agent sends anything.

A refund macro may need an order-status check first. A cancel macro may depend on whether shipping has started.

Keep the shopper message short and specific. Remove team rules language that shoppers do not need.

Never hide uncertainty with a confident template. If an agent needs a 3PL answer, explain the next step. Give the shopper a realistic update point.

Self-help works best when it removes a real reason to contact support. It should not make a shopper hunt for help.

Shopify recommends clear policies and support tools before BFCM sales. Use that guidance to reduce avoidable contacts.

Make shipping, return, exchange, and sale rules easy to find. Update your help center before the campaigns start.

Make order tracking easy to reach. A shopper should not need an email to find a working link.

Use automation for simple, safe tasks. Examples include tagging, routing, and acknowledgements. You can also surface a relevant help article.

Do not automate a judgment call just because volume is high. Refund edge cases, angry shoppers, and unusual delivery cases may need a person.

The best setup removes repeat work while protecting the human path. That gives agents more time for cases that need judgment.

If you use Gorgias, see our Gorgias support operations page. Zendesk users can review our Zendesk support page.

A handoff does not end with a Slack message. Someone must own the next action and the follow-up.

Name an owner for each key issue. Cover payments, large refunds, and shipping. Add chargebacks and checkout problems.

Give each path a backup contact. BFCM exposes weak handoffs quickly when the usual person is unavailable.

Set the details required for each handoff. This reduces the chance that a partner replies with another question.

Use internal notes so the next agent can see what happened. Do not make shoppers explain the same issue again.

For shipping problems, connect support with the people who can act. That may be a 3PL, vendor, warehouse, or operations lead.

For delivery problems, use a consistent investigation process. Our failed delivery tracking guide covers that workflow.

For payment disputes, use a separate evidence process. See our refund and chargeback workflow guide.

During BFCM, the team needs a short operating rhythm. Long meetings take agents away from shoppers.

Set fixed check points during each busy day. Opening, midpoint, and closing reviews can work well for many teams.

At each check, review the same small set of signals:

• Open ticket count by level.
• Oldest unanswered ticket.
• First response time by key channel.
• Checkout or discount issue volume.
• WISMO and delivery issue volume.
• Refund and cancellation volume.
• Handoffs waiting on another team.
• Any product, stock, or shipping pattern.

Do not watch a dashboard without acting on it. Each alert should connect to a decision.

If promo-code tickets rise, check the offer before adding more agents. If WISMO jumps, verify tracking and carrier data first.

If one queue grows faster, move trained agents there. If a macro causes repeat contacts, fix the answer.

Keep a short event log for major issues and choices. That record makes the post-BFCM review much more useful.

Track quality as well as speed. Our QA and CSAT reports guide explains a simple review process.

Cyber Monday ends the sale. It does not end the support work created by those orders.

Shopify reports a 79% average ticket spike during the first week of December. Ticket volume can stay above normal into early January.

That makes post-sale staffing part of the BFCM plan. Do not remove extra help before the delivery and return wave appears.

Watch unfulfilled orders first. Find orders that miss your normal packing window. Do this before shoppers start asking.

Then watch tracking exceptions and failed deliveries. Proactive checks can prevent some repeat contacts and refund pressure.

Prepare for returns and exchanges as deliveries land. Make the process easy to find and keep BFCM rules consistent.

Review refunds, disputes, and chargebacks too. A sale can look successful. Unresolved post-purchase issues can still create later losses.

Keep your 3PL and vendor handoff channels active. Support cannot close a delivery issue without an answer from operations.

Do not wait until next October to study what happened. Run a short review after the main delivery and return wave settles.

Compare forecasted contacts with actual contacts. Note where your forecast was wrong and why.

Review the top ticket groups. Identify which questions grew because of unclear offers, rules gaps, stock, or shipping.

Check response times and resolution quality by channel. A fast first reply is not enough. It fails if shoppers need three more contacts.

Review handoffs that stalled. Fix the owner, process, or required details before the next sale.

Update the help center and macros from real tickets. Remove answers that created confusion.

Save the final BFCM runbook with your results. Next year's team should start with evidence, not memory.

Before BFCM starts, confirm:

• Demand forecast uses your own order and support data.
• Staffing matches expected hours and channels.
• Sale rules are final and visible.
• Shipping and order cutoffs are clear.
• Returns, exchanges, and cancellations have clear rules.
• BFCM macros match the live offer.
• Help center and tracking pages are current.
• Test priority queues and routing.
• Agents can access every tool they need.
• Name handoff owners and backups.
• Confirm warehouse, vendor, and 3PL contacts.
• Live report checks have an owner.
• Schedule post-Cyber Monday staffing.
• Set a post-event review date.

Overflow support helps when your forecast shows a short-term capacity gap. It works best when you document the setup first.

An outside agent still needs product context and clear rules. They also need system access and handoff paths. Adding people without that setup can add more handoffs.

Bring outside support in before the peak. Give agents time to practice. Use the same cases they will handle during BFCM.

Keep agent decision limits clear. Show what they can solve. Then show what needs approval and who gives it.

If your team needs BFCM staffing, contact Virtual Freelance Solutions. We can review your current support setup and expected BFCM load.