Set up DLT-approved SMS templates
Mirror an approved DLT template exactly, add its template ID, and map each positional variable to StoreMink notification data.
Register the SMS wording on the DLT portal before adding it to StoreMink. StoreMink mirrors that approved record; it does not register or change the portal template.
Test this on your own account first. Before using a mirrored template for customer messages, send it once to a number you own and have consent to use through your own Twilio account. Confirm StoreMink's initial log, Twilio acceptance, handset receipt, exact DLT text and variable order, sender, and segment count.
Add a template to a notification
- Open Settings → Notifications.
- Open the event that should send SMS.
- Find the SMS template section.
- Enter the approved DLT template ID.
- Paste the approved body exactly, using the StoreMink DLT variable marker at every approved variable position.
- Map each position to an allowed event value.
- Save and send a test when available.
Why exact wording matters
Indian carriers compare the sent text with the registered body. Changed punctuation, extra words, a different variable count, or the wrong sender can be dropped even when Twilio accepted the API request.
Variable order
DLT variables are positional rather than named. The first marker must map to the first portal variable, the second to the second, and so on. StoreMink refuses a mapping whose number of values does not match the body.
Editing and removal
Changing the StoreMink copy does not change the DLT portal record. Register the new wording first, then update its ID and exact body. Removing the StoreMink template stops that event from using SMS but does not delete the portal registration.
Was this article helpful?