> 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/6-smart-sending.md). # BFCM #6 - Smart Sending Starts Now Shares send-timing tips, based on past Recart campaigns, for standing out during BFCM's crowded inboxes. Even the best campaign can underperform if it hits at the wrong time. During BFCM, timing is everything - especially with overflowing inboxes and intense competition for attention. The good news? A few simple scheduling tweaks can help you stand out and drive better results. ### Timing Tips That Drive Conversions Based on top-performing Recart campaigns from previous seasons: * Avoid top-of-the-hour sends (e.g., 10:00am) - go for off-times like 9:13am or 2:47pm * Space SMS and email sends by 6-8 hours to reduce fatigue * Start sending earlier in the week - build anticipation before BFCM hits * On Black Friday and Cyber Monday, send twice a day - just keep it relevant ### How to Schedule Campaigns in Recart You can easily schedule campaigns in advance and control for delivery timing. [How to schedule SMS campaigns in Recart](/sms/campaigns/run-successful-sms-campaigns-with-recart.md) #### Scheduling Tips: * Schedule key sends at least 72 hours in advance * Double-check time zone settings to avoid misfires * Don’t forget post-sale campaigns: Sunday and Tuesday often perform better than expected! --- # 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/6-smart-sending.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.