> 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/bfcm/bfcm-2025-8-final-checks-flow-testing.md).

# BFCM 2025: #8 – Final Checks + Flow Testing

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](https://help.recart.com/en/articles/5905247-how-to-test-your-recart-sms-messages)
* 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](https://help.recart.com/en/articles/5905127-sms-character-counting-and-limits)

***

### Missed last week’s update? Catch up here:

[BFCM 2025: #7 – Cut the Clutter, Boost Performance](https://help.recart.com/en/articles/bfcm-2025-7-cut-the-clutter-boost-performance)

If you have any questions, don’t hesitate to reach out. We’re always happy to support you.

Happy Texting,

**Team Recart**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.recart.com/bfcm/bfcm-2025-8-final-checks-flow-testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.