Service Explicit SMS

Start with verifiable, specific consent

For a service-message use case involving explicit consent, document how the recipient directly agreed to receive communication about a specific ongoing purchase or use of the sender’s products or services. Keep the consent method, purpose, source, date and applicable record available for review. A phone number, general customer relationship or old enquiry should not be presented as explicit consent by itself.

Keep the message within its service purpose

Describe the transaction or service the message facilitates, the recipient, the message content and the reason it must be sent. Keep promotional material out: TRAI’s 2025 amendment says promotional content mixed into a transactional or service message makes it promotional. The category name alone does not determine the correct route.

Confirm the current provider process

The 2026 TCCCPR amendment updates the service-message and explicit-consent definitions, including a stated consent period for this service-message route. Check the applicable commencement date, any later direction and your access provider’s DLT process before sending. MessageIQ currently supports account preparation and assisted activation only; it does not collect consent, register templates, classify traffic or send messages. Start with the Bulk SMS overview and the TRAI/DLT checklist.