Configure MoEngage
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.
In MoEngage, UDO is added as an RCS connector — configured as a sender rather than as a generic API endpoint, so the fields differ from the CleverTap SMS setup.
Prerequisites
- Access to your Unique Digital Outreach Pvt Ltd dashboard.
- Your RCS Sender ID — the RBM agent or bot ID.
- The API URL and bearer token for your account. Both are issued by the UDO team.
- Admin access to MoEngage, with permission to edit sender configuration.
Unlike the CleverTap setup, two of the values here are issued by us rather than found in your dashboard. Ask for the API URL and bearer token before you start, or you will get halfway through the form and stop.
Configure Unique Digital Outreach Pvt Ltd as an RCS Connector
Five steps. The sender is created once and then selectable on every RCS campaign.
Open sender configuration
In the MoEngage UI, go to Settings → Channels → SMS/RCS → Sender configuration.
Add an RCS sender
On the RCS tab click + Add RCS Sender, then select the Unique Digital Outreach Pvt Ltd tile from the list of service providers.
Complete the Sender Details form
Six fields, four of them required. The table below covers each one.
| Field | What to enter |
|---|---|
| Mark as default | Turn on to make this the default sender for the service provider. Every RCS campaign then uses it unless a different sender is picked while building the campaign. |
| Sender type | Select one:
|
| Sender Name | The readable name your team sees when picking a sender while creating a campaign or alert. |
| Sender ID | The RCS agent or bot ID that RBM uses to send messages to users. |
| API URL | The UDO RCS endpoint your MoEngage account should post to. Issued by the UDO team — it is not the same as your SMS endpoint. |
| Authorization | The bearer token used to authorise the connection. Also issued by the UDO team. |
It determines how the message is classified and routed. Set it to match what you are actually sending — a promotional campaign going out on a transactional sender is a compliance problem, not a labelling one.
Save the sender
Click Save. The sender becomes selectable when building any RCS campaign in MoEngage.
Send us the delivery callback URL
MoEngage generates an Incoming Messages & Delivery Callback URL at the foot of the Sender Details screen. Copy it and email it to the UDO team so we can configure it at our end.
Skipping it is the most common oversight. Without the callback configured, campaigns still send but MoEngage receives no delivery receipts and no customer replies — so reporting looks broken and inbound RCS goes nowhere. Send it before you launch, not after.
Troubleshooting
| Symptom | Most likely cause |
|---|---|
| Sender will not save | A required field is empty. Sender Name, Sender ID, API URL and Authorization are all mandatory. |
| Authorization rejected | Bearer token copied with trailing whitespace, or the SMS key used instead of the RCS token. |
| Campaign sends, no delivery reports | The callback URL never reached the UDO team. See step 5. |
| Customer replies go nowhere | Same cause — the callback carries both receipts and inbound messages. |
| Messages route incorrectly | Sender type does not match the content being sent. |
Still stuck? Contact the team with your sender name and the error MoEngage returns.
