Holiday FAQ: The Questions Visitors Ask Before Black Friday
Hannah Feld -
A shopper has a jacket in the cart. The price is right. She wants to know if it arrives before the weekend and what happens if the size is wrong. Neither answer is on the cart page. She opens the FAQ in a new tab, scrolls, loses the cart tab, and buys somewhere else.
This is the page problem of the holiday weeks: the answers exist, but they sit two clicks away from the moment the question appears.
Three weeks, and a calendar that does not move
Black Friday falls on Friday, November 27, 2026, the day after US Thanksgiving on November 26, and Cyber Monday lands on November 30. From today, November 6, that leaves about three weeks of work. Enough for a small shop, if the list is short.
What visitors are really asking
The questions are not exotic. Baymard Institute's list of cart abandonment reasons, based on US online shoppers who were not just browsing, includes several that are answered by a sentence on your site.
In Baymard's list, extra costs (shipping, tax, fees) too high: 40%. Delivery too slow: 20%. Returns policy unsatisfactory: 13%. Total order cost not visible or calculable up front: 12%. The page does not state the survey year or sample size, so treat the numbers as a rough order of importance, not as a forecast for your shop.
A FAQ cannot make shipping cheaper or a policy kinder. What it can do is remove the surprise: the visitor learns the cost, the date and the return rule before the checkout, not at the last step.
The fix: answers next to the button
Most small shops keep these answers on a FAQ page, far from the order button. Move them.
- Collect the real questions. Open the last month of emails and chat messages. Write down every question about delivery, returns, order changes and payment. Keep the visitor's wording.
- Rewrite the first sentence of each answer. "Orders placed before your real cut-off time ship the same day" says more than "We process orders promptly." Use your real cut-off times and your carrier's real dates, and fill them in only after you have confirmed them.
- Put a three-line block under the order button. One line each for delivery, returns and total cost. Link every line to the full FAQ answer.
- Show the total early. If shipping is added at checkout, say what it is, or say how it is calculated, on the product page.
- Add a holiday note on top of the FAQ. The last order date for delivery by the holiday, any longer return window, and the support hours over the weekend. Put the date in the sentence.
A made-up example of the block, for the shape only:
Delivery: ordered by [your cut-off date], arrives by [date]. Returns: [number] days from delivery. Total: shipping shown before you pay.
Fill the brackets from your own policy. Do not copy a number from another shop.
A calendar for the three weeks
The week of November 9 is about words. The week of November 16 is about placement and a phone test. The week of November 23 is only about checking: a wrong date during a sale costs more than a missing answer.
Check that it works
Hand a phone to someone who has not seen the shop. Ask three things: when would this arrive, can I send it back, what is the total? Count taps from the product page. Each answer should take zero taps, since it sits under the button, or one tap to the full text.
During the sale, read every new question that arrives. Each one is a gap. Put the answer on the FAQ by the next morning, and add it to the block if it comes up twice.
This will not change a price, a delivery speed or a return rule, and it will not win back a shopper who finds the policy itself unacceptable. It makes sure the shopper who would have stayed is not lost to a missing sentence. For a layout that shows the answer before a tap, see the FAQ page examples.