Sample messages show reviewers what you actually plan to send. Getting them right is a quick win, and getting them wrong is an easy rejection.
Cover every message type
You must provide samples for every type of message you send. If you send both fundraising appeals and transactional messages (donation receipts, event reminders, volunteer scheduling), show both. If you only include the welcome text but forget the year-end appeal text, you are risking a rejection. A good rule: if a supporter could receive it, include a sample of it.
Follow the HELP/STOP framework
Every sample must follow the HELP/STOP framework. Your very first message to a supporter needs to include instructions on how to get help and how to quit. For example:
Welcome to Riverside Food Bank. Up to four messages per month. Message and data rates may apply. Reply HELP for help and STOP to opt out.
That single message does several jobs at once: it names your organization, sets frequency expectations, includes the rates disclaimer, and gives the supporter a clear way to get help or opt out.
Keep your organization visible
Your organization name must be visible in your sample messages. The name is the anchor that holds your entire 10DLC registration together, so it should be obvious in every message a supporter receives, starting with the first one.
A quick checklist for samples
One sample for each message type you send (appeals and transactional)
Organization name visible in every sample
Frequency stated (for example, "up to four messages per month")
"Message and data rates may apply" included
HELP and STOP instructions in the first message
Related articles