Freeze the actual version
Review the exact message that will be sent, including links, media and any variable fields. A previously approved draft is not approval for a later edit. Confirm that the audience and sending time still match the purpose. If the platform displays a preview, treat it as one observation rather than a guarantee of every recipient’s device experience.
Check the destination first
A short message can look correct while its linked reference is outdated or unavailable. Confirm that the destination contains the intended current information and does not expose private content. Do not click a live affiliate or other consequential link merely to make a test look complete. Use appropriate controlled checks and keep the result tied to the exact destination version.
Check the people behind the send
Make sure the audience is approved for the proposed use and that an inbox owner will be available. Review exclusions and any recent changes. If a required fact remains unknown, hold the affected send; do not convert a deadline into evidence. A second reviewer can be useful where the consequences justify it, but this guide does not prescribe a universal approval hierarchy.
Keep a short release record
Record purpose, audience basis, message version, intended time, owner and the actual result. Distinguish prepared, scheduled, submitted and observed delivery states. If submission becomes uncertain, reconcile the existing campaign before trying again. A duplicate correction can create more confusion than the original problem.
A compact exception record
If the audience is ready but the linked timetable is stale, hold the affected message and identify the timetable owner. Do not restart unrelated preparation or erase the approved audience record. When the timetable is corrected, recheck the exact destination and message together. The release record should show the resolved exception, not merely a new timestamp.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02