Use Case Sample Messages
What are Sample Messages?
Under 10DLC requirements, organizations must submit two unique sample messages when applying for a Use Case. We collect these messaging samples for you and send them to The Campaign Registry. The intention is that each unique use case for each organization would have its own examples that the carriers can reference.
How to submit Sample Messages
Admins and account owners will be prompted to enter two sample messages below their selection when submitting a use case.
You will want your sample messages to reflect the kinds of messages you will send with that particular use case. It is important to note that each sample needs to be unique. (Sample messages 1 and 2 cannot match each other.) They also cannot match what has been entered into another ThruText account.
Tips on writing your Sample Messages
Make sure your sample messages include who you are. Carriers want to see that you will be identifying your organization to your message recipients.
Match your samples to your use case
If you are applying for the "Charity" use case, that should be reflected in your samples. For example, you would not want to use a potential political message as your "Charity" Sample Message.
How to use variables
If you are sending Sample Messages with a variable, wrap it in box brackets. Carriers know that what is inside the brackets will be variables when you go to send a message.
For example, "Hi [name], this is [sender name]..."
NOTE - Box brackets are only used in Sample Messages. When you're writing the messages you will send in ThruText, you will use this guide.
End with an opt out message
Carriers love to see that you'll be following their best practices. (We have already built their best practices into initial message scripting.) You will want to include an opt out message in your samples, like "STOP to opt out" to show that you'll follow their directions.