> 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/8-final-checks.md). # BFCM #8 - Final Checks and Flow Testing Provides a final audit checklist for testing flows, links, and offers before your BFCM campaigns go live. We’re nearly there — and this week is all about finalizing your setup. Before the floodgates open, take time to **double-check everything** so you can launch with confidence. No last-minute scrambling. No broken links. No missing messages. #### Final Audit Checklist Here’s what to test and confirm this week: * All **automated flows** are live and targeted * All **buttons and links** in messages work and lead to the correct pages * Offers and **discount codes** are up to date and tested * **Popup timing** and display logic is correct (especially on mobile) * SMS content is **short, accurate, and approved** #### Test Your Flows + Campaigns Even if your setup looks good — test everything manually. It’s worth it. * Send yourself every SMS to preview the experience * [Learn to test messages here](/sms/getting-started/test-recart-sms-messages.md) * Double-check VIP or early-access targeting rules * Check for typos, outdated CTAs, or awkward timing * Make sure you did not copy/paste any special characters * [Learn more about character counting here](/sms/writing-messages/sms-character-counting-and-limits.md) --- # 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/8-final-checks.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.