> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/holiday-playbooks/bfcm/9-survive-crunch-week.md). # BFCM #9 - Survive Crunch Week Like a Pro Shares five quick reminders for staying on plan and testing sends during BFCM's busiest week. Whether you're launching early or riding the Black Friday wave head-on, this is the moment we've all been preparing for. To help you stay ahead (and avoid last-minute chaos), here are five quick reminders to carry you through the week. ### Top 5 Crunch Week Tips 1. **Don't panic-send** Stick to your planned calendar — last-minute campaigns often underperform. 2. **Test before every send** Double-check your links and SMS character count. 3. **Avoid overlapping sends** Space out SMS and email by 4–6 hours to reduce fatigue and avoid confusion. 4. **Monitor your performance** Watch key metrics like unsubscribe rate, clicks, and delivery status — tweak only if needed. 5. **Have your support contacts ready** Know exactly how to reach us if something goes wrong (see below). ### How to Reach Recart Support Through the BFCM period we run extended support hours and keep a closer watch on accounts, so you can reach someone quickly when it matters most. If something looks wrong, use whichever of these is fastest for you: * Your dedicated Slack channel, if your account has one * Your CSM, directly * Email us at * Live chat from your [Recart dashboard](https://app.recart.com/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.recart.com/holiday-playbooks/bfcm/9-survive-crunch-week.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.