# Setting up Your Own Mask ID for SMS

This guide will help you configure and use a **custom Mask ID** for SMS communications (OTP, order updates, and marketing campaigns) on the UrbanPiper Meraki platform.

### Register & Approve SMS Templates on the DLT Portal

* Log in to your **DLT portal** (Vodafone, Jio, Airtel, etc.).
* Create all required **SMS templates** under your registered entity.
* Submit templates for approval.
* Once approved, note down:
  * **Template ID**
  * **PE ID (Principal Entity ID)**

📌 These details are provided by TRAI after approval.

### Complete the PE–TM Bonding

To link your entity with UrbanPiper’s SMS service provider (**Gupshup**):

* Log in to your DLT portal.
* Bond your **PE ID** (Principal Entity ID) with the following **Gupshup Telemarketer IDs**:

| Operator | Gupshup TM ID |
| -------- | ------------- |
| Vodafone | (provide ID)  |
| Jio      | (provide ID)  |
| Airtel   | (provide ID)  |

📌 This **PE–TM bond is mandatory** before templates can be whitelisted on Gupshup’s platform.

### Share Approved Templates with UrbanPiper Support

* Once bonding is complete, email **<support@urbanpiper.com>** with:
  * Your **PE ID**
  * List of all **approved templates** (with Template IDs)
* UrbanPiper Support will configure the templates in the backend.
* The team will initiate the whitelisting process with Gupshup.

### Gupshup Whitelisting

* UrbanPiper Support will coordinate with Gupshup to whitelist your templates.
* Once approved, your **custom Mask ID** will be active.
* You can now send all SMS (OTP, order updates, campaigns) via Meraki using your Mask ID.

### Important Reminders

* ✅ **PE–TM bonding is compulsory** before template whitelisting can begin.
* ✅ SMS content **must exactly match** the approved DLT template. Any mismatch can lead to **delivery failures**.
* ✅ Keep your **Template IDs and PE ID** safe — you’ll need them for support and future updates.