CleverTap

​

Part A — Create the provider and configure RCS and SMS fallback

1

Create the provider

In CleverTap, go to Settings → Channels → SMS, add a provider, and set Provider to Generic RCS Provider. Give it a clear nickname.

2

Set the messaging endpoint

Field	Value
Request Type	POST
HTTPS Endpoint	https://ct.onex-aura.com/rcs/send
Authentication	No Authentication
Headers	Key apikey → your OneXtel API key

Authentication is set to none because the API key travels as a header, not as an auth scheme CleverTap manages.

3

Set the RCS sender and body parameters

Set RCS Sender ID to your OneXtel RCS sender profile, or to a pool. If you use a pool, only templates assigned to that pool will resolve. If your account has more than one sender profile, you can also choose the profile per campaign with an optional sender_id pair — see Part C.

Sending from several senders through one provider. CleverTap fixes the RCS Sender ID on the provider, not on the campaign, so by default one provider sends from one profile. If you run several brands or senders on one CleverTap project, put a placeholder of the form <brand>_onextel_rcs in RCS Sender ID instead of a real profile — for example acme_onextel_rcs.OneXtel reads any sender ID in that shape as a placeholder rather than a real sender, and takes the actual profile from the sender_id key-value pair on each campaign. That pair stops being optional and becomes required: a campaign that omits it is rejected rather than sent from the placeholder.The same applies to SMS, with <brand>_onextel_sms and the SMS provider’s Sender ID. One provider and one endpoint then serve every sender on the account.

Under RCS Body Parameters, add these key-value pairs. The $$ syntax tells CleverTap to fill the value from the campaign’s custom params.

Key	Value
message_type	$$message_type
template_id	$$template_id

4

Enable SMS fallback

Turn on SMS Configuration / Enable Fallback SMS and set SMS Sender ID to your OneXtel SMS sender ID.Under SMS Body Parameters, add:

Key	Value
type	$$type
templateId	$$templateId
unicode	$$unicode
entityId	$$entityId
fallback_id	$$fallback_id

5

Save, then copy both callback URLs

Save the provider, then reopen it. Under Callback Config you will find two read-only URLs. Copy both — you paste them into OneXtel in Part D.

URL	Used for
Delivery Report Callback URL	Delivery reports, clicks, and SMS fallback reports
Inbound Message Callback URL	Inbound replies — carries a providerId parameter

The Inbound URL only appears after you reopen the saved provider; immediately after the first save you may see only the Delivery Report URL.

​

Part B — Add templates in CleverTap (optional)

​

Part C — Build the campaign and personalize it

1

Create the campaign

In CleverTap, create a new campaign. Under From, select the provider you created in Part A. Under Who, choose your audience. Under What, choose the Text Free Form type and enter a message body — or, if you added templates in Part B, pick one of those.When the campaign sends a OneXtel template through template_id, the body you enter here is only what CleverTap shows while you build. The recipient receives the OneXtel template.

2

Add the RCS key-value pairs

Key	Example	Notes
message_type	Transactional	Promotional or Transactional
template_id	payment_success_onex	The OneXtel template to send. Omit to send the composer output instead
sender_id	Acme_1	Optional — only when your account has more than one sender profile. Names the profile to send from; omit it to use the provider’s RCS Sender ID. Required, not optional, when the provider’s RCS Sender ID is a <brand>_onextel_rcs placeholder. The template_id template must belong to this profile
custom_param1	@Profile - Name | default: "Customer"	One pair per template variable. The key is the placeholder name from the OneXtel template, without the square brackets. The value is a CleverTap personalization token
any other key	—	Passed through to OneXtel as a template placeholder value

To personalize a template variable, add a key-value pair for it here, in the campaign’s What section — not in the provider setup. Type @ in the value field to open CleverTap’s personalization menu, choose the user or event property, and set a default for recipients who do not have it. CleverTap resolves the token for each recipient at send time and the connector passes the resolved value to OneXtel under the same key.If the OneXtel template reads Hi [custom_param1], the key is custom_param1. A key that does not match the bracketed name character for character leaves the placeholder unfilled on the handset.

For the token syntax and defaults, see CleverTap’s RCS Message Editor and Personalize Message.

3

Add the fallback SMS block

Toggle on Fallback SMS, enter the fallback text, and add:

Key	Example	Notes
fallback_id	4f2005fa-…	The fallback configuration ID from your OneXtel account
templateId	Your DLT template ID	Required for Indian sends
entityId	Your DLT entity ID	Required for Indian sends
type	SI	Must match the DLT template’s registered category
unicode	0	1 if the body contains non-ASCII characters

4

Save the campaign as a draft

Save the campaign, but do not publish it yet. Set up the callbacks in Part D first, so the delivery reports, replies, and clicks from the very first send reach CleverTap.

​

Part D — Configure the callbacks before you send

​

Part E — Send and validate

​

Personalize a template

{
  "templateMessage": {
    "templateCode": "ct_var1",
    "customParams": "{\"custom_param1\":\"Kabir Sethi\"}"
  }
}

​

Buttons and templates

• Template previews will not match the real message. CleverTap renders through its own composer, so what you see when building is not what the recipient receives. Confirm with a test send.
• Fallback failures are silent. An incomplete SMS block does not raise an error in CleverTap.
• Composer templates cannot use saved OneXtel templates directly — use template_id.
• CleverTap’s {{1}} placeholder values are not passed to OneXtel. Personalize through a campaign key-value pair named after the OneXtel placeholder instead — see Personalize a template.
• RCS failure codes are coarse. Every failure reaches CleverTap as 910 or 914; the operator’s own code is in OneXtel reporting.