Skip to main content
Customer Support

Black Friday Customer Support Checklist for Small Shops

Prepare your small shop for Black Friday with a shared offer sheet, realistic checkout tests, clear handoffs and a plan for questions after the sale.

The Zorachat Team5 min read
Black Friday Support Checklist beside a checklist with green ticks, an indigo chat bubble and a green price tag.

A Black Friday customer support checklist should cover five jobs: confirm the offer, test what shoppers see, agree who handles exceptions, staff the busiest periods and retire expired answers. Start with a one-page offer sheet. Give your team and your chat assistant the same approved facts, then run through a few awkward scenarios before the sale opens.

This checklist is for small online shops answering questions through website chat, WhatsApp, Instagram DMs or Facebook Messenger. You can use the same plan for a weekend sale or a short product launch.

1. Write one offer sheet with an expiry time

Give the sheet an owner and a last-checked time. Keep a single editable copy and link to it from the team’s shift notes. Include the details people need to answer a shopper in one reply.

  • Offer window: Start and end dates, local time and time zone. Say whether the code or basket must be submitted before the deadline.
  • Eligibility: Included products, excluded variants, minimum spend, regions and whether codes can be combined. Spell out whether delivery counts towards the threshold.
  • Delivery: Where you ship, when parcels are expected to leave, and which estimates depend on a postcode or destination. Keep dispatch and arrival in separate fields.
  • After the sale: Link to your published returns information and note any advertised seasonal extension. Give staff a named contact for conflicting terms or requests that need approval.

Turn the approved details into short FAQ answers your chatbot can use. Put common exclusions on the offer page as well. Someone who arrives from a shared Instagram post should be able to find the same terms as someone who comes through your homepage.

2. Test the offer with baskets that should pass and fail

Pick one colleague to play the shopper. Ask them to open the sale link on a phone, build a basket, enter the code and check what the checkout actually shows. Use a test environment for any scenario that would place an order or charge a card.

  • Try an eligible basket and one just below the minimum spend. Add delivery and check whether the result matches the offer sheet.
  • Swap an included product for an excluded size or variant. Try a second code if your terms say codes cannot be combined.
  • Check a local and an international destination if you serve both. Compare the delivery options and estimates with the answers your team plans to give.
  • Send the same question from two customer channels. Check that the replies agree on the condition that determines the outcome.

For example, suppose a fictional stationery shop offers 15% off selected notebooks when eligible items total £30 before delivery. A £28 notebook basket with £4 delivery should fail. A useful reply would be: “The offer applies once eligible notebooks total £30 before delivery. Your notebooks currently total £28. You can check which items qualify on the offer page.” If that same basket meets the threshold and still fails, send it to the person who can inspect the promotion settings.

3. Decide what the team can answer and what needs a check

Use approved answers for offer terms, standard delivery estimates and published return instructions. Assign a person to check conflicting discounts, orders with a confirmed payment but no confirmation, and promises about a specific delivery date that require fulfilment to verify.

Write one handoff rule for each exception. Include who owns it, what they need and when they’ll update the customer. A checkout note could read: “Eligible notebooks total £34 before delivery. Code rejected at 18:20 UK time on mobile. Customer hasn’t placed the order. Sam to reproduce the issue and update the customer by 19:00 UK time.” Use a response window your team can cover, and keep card details out of the chat. The guide to handing a chat to a human covers what to pass along so the customer can pick up where they left off.

If two shoppers report the same unexpected error, have one person reproduce it and maintain a shared status note. Other teammates can acknowledge the issue and use the same update while the owner investigates.

4. Cover launch, closing time and dispatch

Schedule around the work. The start of the sale is a good time to have someone with access to promotion settings available. Near closing, make sure someone can verify time-sensitive checkout problems. When dispatch starts, keep a fulfilment contact available for missed scans or orders that need checking.

If one person covers chat and packs orders, agree when they’ll check messages and who takes over if packing runs long. Set the customer-facing reply expectation to a window the team can meet. During each support shift handover, list unresolved cases with an owner and a promised update time. Pay particular attention to a customer who reported a checkout problem before the offer ended. Keep the time and facts so the next person can make a decision.

5. Remove expired answers and keep order help available

At closing, replace promotional saved replies, FAQ entries and any assistant instructions that still describe the offer as active. Keep the original terms available for staff handling orders placed during the sale. Test an old campaign link and ask chat, “Can I still use the code?” The reply should give the current position and an appropriate next step for someone who already ordered.

After dispatch, review a small batch of chats with the team. Sort them by what could have prevented a second message: clearer offer wording, a checkout fix, a more accurate delivery estimate or an earlier handoff. Assign the most common issue to someone who can fix it before the next campaign.

Once your offer sheet is ready, see how to train Zorachat on your FAQs and policies so the assistant can answer routine sale questions from your approved information.

Black FridayEcommerce SupportCustomer Support

Keep reading

Ready to deploy AI support that never clocks out?

Answer visitors 24/7, capture leads, and hand off to your team with full context.

Build your assistant

No credit card required · Live in about 3 minutes