Text Projects - Tips & Tricks

1. When changing the link in COS, you only need to edit the script in the Introduction and click save. This will immediately update the script when sending out to the universe, saving you time and eliminating the need to change the "Question" portion as well.
2. Avoid using the same message group repeatedly to send texts. At some point, carriers will start flagging the phone numbers being used and heavily reject the texts, regardless of the universe size or presence of a link.
3. For large texting projects, create 2-3 different message groups so you can switch between them midway through. When adding phone numbers, divide the total universe by 300 to determine the required number of phone lines. Never add more than 30 numbers at a time. Be cautious when searching for numbers - stick to the same geographic area as the text recipients.
4. Sending texts is an active process - you must constantly monitor the project sending status and error codes. Carrier violations and other errors can accumulate quickly if you're not vigilant. Always internally test the script before sending, and wait for client approval before initiating a test send.
5. Check the start/end date and time before sending texts. For billing, document the number of segments and whether there is a MMS in the Manager Notes of the PO. Use the TextMagic tool to confirm the character/segment count if needed, and inform the client if the script exceeds one segment.
6. When sending texts with a screenpop, rigorously test to ensure it's functioning properly. The formula is {$COLUMNHEADERNAME} - verify the column header formatting. For easier reporting, include the remap responses in the PO details of cOS.
7. Aim for 100% goal saturation on most texting projects, unless the client specifies a stop number. Continuously refresh the cOS report as you send. If you see a high "Text Transmitted" count, pause sending. The best practice is to send texts slowly to avoid system congestion.