SMS-based authentication makes it easier for the customers to login to the help center without using their username or password. A two-step quick login involves:
Companies can invite their customers to sign up for their help center by sending them an invitation link via SMS. This simplifies the onboarding process; customers can create an account and start using the help center to submit support tickets, initiate a discussion in the community, and refer to the knowledge base.
Sometimes, customers find it difficult to remember the login credentials for the help center. They can use the SMS-based authentication system to access the help center quickly.
By offering both invitation-based registration and verification-based login through SMS based authentication, organizations can reduce risks caused due to:
Note:
- SMS-based authentication is available only for accounts that have single help centers or unique user bases.
For a multi-branded help center, only those accounts that have a unique user base can use SMS-based authentication. - If SMS-based authentication is enabled for one help center in a portal, then all the help centers must be enabled with SMS authentication.
Other authentication methods like SAML, JWT, and Federated login will not be used even if they are enabled.

Setting up SMS-based authentication
Prerequisites:
Register as a Sender on the DLT Portal: To enable SMS-based authentication, users must first register as a sender on the DLT portal. After completing the registration, users should make a note of the essential sender ID details, which include the Sender name (Sender ID/Header), PEID (the unique 19-digit Entity ID), Entity name, Sender unique ID, and the telecom provider used for registration.
- Download SMS templates: Along with the sender ID details, users must also register the content template and download the required SMS templates (invitation and verification code templates) from the DLT portal.
Setting up SMS-based authentication involves the following steps:
- Provide company and sender ID details
- Adding Zoho as telemarketer aggregator in the DLT portal
- Compliance with TRAI (India only)
- Purchasing SMS Credits
- Uploading SMS templates
Provide company details: Provide the necessary basic information about the organization to enable SMS-based authentication. This includes:
- Legal company name: The officially registered name of the organization.
- Brand name: The name under which the organization operates or is publicly recognized.
- City: The city where the organization is registered or headquartered.
- State/region: The state or region of the organization’s registration or operation.
- Postal code/ZIP code: The postal or ZIP code corresponding to the organization’s registered address.
- Country of registration: The country where the organization is legally registered.
Provide sender ID details: Enter the sender ID details required for using the SMS-based authentication service. These details vary by country according to the rules and guidelines set by telecom authorities. The required details on the sender ID page will adjust based on the organization’s country of registration. Below are the Sender ID details:
- Sender name (Sender ID/Header): A unique alphanumeric header registered with DLT under TRAI’s regulations for transactional communication.
- PEiD (Portable Executable Files): A unique 19-digit entity ID assigned to your organization on the registered DLT portal.
- Entity name: The name of the entity as registered in the DLT portal.
- Sender unique ID: The unique Header ID provided by DLT.
- Sender ID status: Indicates whether the sender ID is verified or unverified.
- Registered by: The telecom service provider used to register for the sender ID.
Compliance with TRAI for India: For organizations operating in India, compliance with the Telecom Regulatory Authority of India (TRAI) is mandatory. TRAI enforces Distributed Ledger Technology (DLT) to ensure that only legitimate SMS are sent to customers. SMS-based authentication messages must be sent through an Indian Sender ID registered with DLT.
To set up SMS notifications
- Navigate to Setup > Channels > Help Center > User Authentication.
- Choose SMS Based Authentication and click Enable.
- Click Continue.
- On the Company Info tab, provide the following details:
- Legal Company Name
- Brand Name
- City
- State/Region
- Postal Code/Zip Code
- Country of registration
- Click Next.
- On the sender ID Details tab, provide the following details:
- Sender Name (Sender ID/Header)
- PEID
- Entity Name
- Sender Unique ID
- Sender ID Status
- Registered By
- Click Save.
Adding Zoho as telemarketer aggregator in the DLT portal
After setting up SMS-based authentication , the next step includes adding Zoho Corporation as the telemarketer aggregator in the DLT (Distributed Ledger Technology) portal. This step is necessary to ensure the successful delivery of SMS messages for authentication purposes.
To add Zoho as a telemarketer aggregator
- Log in to the DLT portal.
- Go to the Chains section and create a new chain.
- In the Telemarketer section, search for Zoho Corp using the telemarketer ID 1102631350000082951 or the name ZOHO CORPORATION PRIVATE LIMITED.
- Add ZOHO CORPORATION PRIVATE LIMITED as the Telemarketer Aggregator.
- Click Submit.
- Create another chain for fallback delivery to ensure SMS messages are sent even if the primary route is unavailable. This guarantees delivery during network issues.
Purchasing SMS Credits
In this step, the organizations must purchase SMS credits from the Credit Details tab to activate SMS-based authentication and send invitation and verification code SMS to customers.
Admins can monitor their credit usage and remaining balance in the credit details tab to keep track of consumption and ensure they have sufficient credits for SMS-based authentication.
Under the Credit Details tab, users can:
- View the available credit balance.
- Check the credit usage analysis, which can be filtered by weekly, monthly, quarterly, or a custom date range. For example, if users check their credit usage for the entire month (e.g., January 1 to January 31), they can monitor how their credits are being consumed and identify any unexpected spikes in usage. To manage this effectively, users can set a monthly credit limit to prevent overspending, and if usage approaches the limit, they can adjust their messaging volume or purchase additional credits.
- Purchase additional credits if needed.

Note: SMS messages will only be sent if sufficient credits are available in the Desk account. When the credit is exhausted, an email notification is sent to the administrator.
Info: Pricing Details:
- INR - The cost per SMS is 0.0020 credits when sent to Indian phone numbers using DLT-registered sender IDs.
- USD - The cost of 1 credit is $1 USD. So, 1 credit allows sending 500 SMS messages to the customers.
To buy SMS credits
- Navigate to Setup > Channels > Help Center > SMS-Based Authentication > Credit Details.
- Click on Buy Credits.
- In the Recharge SMS Credits window, enter the required number of credits.
- Click Make Payment.
Uploading SMS templates
Once the SMS-based authentication feature is enabled and credits are purchased, the next step is to upload the DLT verified SMS templates.
To upload SMS templates
Click Submit DLT files.
- Upload the Verification code template downloaded from the DLT portal and click Next.
- Upload the Invitation code template downloaded from the DLT portal and click Next.
- Map the uploaded templates accordingly and click Save.
Once the template is uploaded, it will be submitted for approval to DLT. After receiving approval, users can successfully enable SMS-based authentication for their help center.
Disabling the SMS based authentication
There might be scenarios where SMS-based authentication needs to be disabled, such as when a user wants to implement an alternative authentication mechanism or simply decides not to use SMS-based authentication going forward.
Once SMS-based authentication is disabled, all data related to the SMS regulatory authority, including brand details, sender information, and templates, will be permanently removed, with only the credit balance being retained. Upon re-enabling the existing credit balance can be reused, however the company information and sender ID details need to be re-entered.
To disable the SMS based authentication
Go to Setup > Channels > Help Center > SMS Based Authentication.
- Click Disable.