CRM Integrations
Introduction
Unique Digital Outreach Pvt Ltd is a mobile engagement and communications provider enabling enterprises to intelligently personalize their two-way marketing and customer care interactions across multiple channels.
UDO can be added as a delivery provider inside the customer engagement platform your team already uses, so your audiences, journeys and reporting stay exactly where they are. The platform hands each message to UDO at the moment it fires, and nothing you have already built needs rebuilding.
Both integrations below are configured entirely from the platform's own settings screen. Neither requires a developer or a code change on your side.
Prerequisites
- Ensure you have access to your Unique Digital Outreach Pvt Ltd dashboard, with credits in your account balance.
- Have the API key for your Unique Digital Outreach Pvt Ltd account.
- Have a fully functional account on the platform you are connecting, with permission to edit channel or sender settings.
- For SMS, complete DLT registration for your sender header and templates. Our team handles this if it is not already done.
A correctly configured integration still fails on an empty account. If a test message does not arrive, check your credit balance before you start re-checking the configuration.
Available Integrations
| Platform | Channel | Where it is configured | Credential |
|---|---|---|---|
| CleverTap | SMS | Settings → Integrate your SMS → Generic | API key |
| MoEngage | RCS | Settings → Channels → SMS/RCS → Sender configuration | Sender ID + bearer token |
| Any HTTP-capable platform | SMS / RCS | Custom or webhook provider setting | API key |
Any platform that can call an HTTP endpoint can send through UDO — that is all the CleverTap integration is underneath, a POST request carrying an apiKey header. If your CRM supports a generic, custom or webhook-based provider, the same endpoint and headers apply. If it does not, tell us which platform you use and we will look at what it would take.
Troubleshooting
| Symptom | Most likely cause |
|---|---|
| Test message never arrives | Empty account balance. Check credits before re-checking configuration. |
| Authentication rejected | API key copied with trailing whitespace, or entered in the wrong header field. |
| Request accepted, SMS not delivered | DLT header or template not yet approved. RCS is unaffected by DLT. |
| 404 or endpoint not found | Endpoint entered as sms without the API base URL in front of it. |
| MoEngage sends but reports nothing | Callback URL was never sent to the UDO team, so no delivery receipts return. |
| Inbound RCS replies go nowhere | Same cause as above — the callback URL carries both receipts and replies. |
FAQs
Which CRMs does UDO integrate with?
UDO has documented integrations with two customer engagement platforms today: CleverTap for SMS and MoEngage for RCS. CleverTap is configured through its Generic SMS provider option using UDO's HTTP API endpoint and your API key. MoEngage is configured as an RCS sender under Channels, using a sender ID and a bearer token issued by UDO. Any other platform that can call an HTTP endpoint with a custom header can also send through UDO using the same endpoint.
Do I need a developer to set this up?
No. Both integrations are configured entirely through the platform's own settings screens, and neither requires writing or deploying any code. What you do need is an administrator account with permission to change channel or sender settings, which on most teams is not the same person who builds the campaigns. Set aside a few minutes with someone who has that access, and have your UDO API key to hand.
Will I have to rebuild my existing campaigns?
No. The integration sits at the delivery layer, underneath everything you have already built. Your segments, journeys, triggers, personalisation and reporting all stay exactly as they are in CleverTap or MoEngage. The only thing that changes is which provider carries the message once the platform decides to send it, so existing campaigns keep running without being touched at all.
Do I still need DLT registration if I send through a CRM?
Yes, for SMS. DLT is a TRAI requirement that applies to the SMS channel in India regardless of which software you send from, so routing through CleverTap does not exempt you. Your sender header and message templates must be registered and approved before delivery will succeed. If your DLT registration is not in place, our team handles it as part of onboarding. RCS is governed separately and does not use DLT.
Where do I get my API key and bearer token?
Your API key comes from your UDO dashboard and is what the CleverTap integration uses to authenticate. The bearer token that goes in the MoEngage Authorization field is issued separately by the UDO team, so request it from us before you begin that setup. Both credentials authorise sending on your behalf, so treat them the way you would treat a password and avoid pasting them into shared documents or support tickets.
Can I use both integrations at the same time?
Yes. They are independent of one another and cover different channels, so running CleverTap for SMS and MoEngage for RCS simultaneously is a perfectly normal configuration. Both sit on the same UDO account and draw from the same balance, which means you get a single consolidated view of what you have spent across both channels instead of reconciling two separate provider invoices.
What does it cost to use an integration?
There is no separate charge for connecting UDO to CleverTap or MoEngage. You pay the standard per-message rate for whatever you send, and the integration itself carries no setup fee, no platform fee and no monthly subscription. Whatever you pay your engagement platform is a separate matter between you and them. For current per-message rates see our pricing page, or ask us for a quote against your actual monthly volume.
Which channels can I send through an integration?
Today the documented integrations cover SMS through CleverTap and RCS through MoEngage. WhatsApp Business API and Voice run on the same UDO account but are used through our own platform or API rather than through these two connectors. If you need WhatsApp or Voice triggered from inside your CRM, talk to us about the API route, which any platform capable of an HTTP call can use.
Tell us which platform your team runs
We will confirm whether it is supported today and walk your team through the configuration on a call, rather than leaving you with a document.
