Send message via campaign
Configure template or free-form RCS messages, map Responsys profile fields, and run campaigns in Oracle Responsys Program Designer.
Send personalized RCS messages to contacts on your profile lists using Oracle Responsys Program Designer and the Gupshup RCS app.
Configure the message in the service screen, connect the App block to your audience and schedule, and publish the program. Choose one sending approach per service configuration:
- Template message send — Select an approved Gupshup RCS template and map its placeholders to Responsys profile fields.
- Free-form message send — Compose non-template content when your agent's platform rules allow it.
Template selection and free-form composition are not combined in the same saved instance.
Prerequisites
- Complete Installation and save at least one channel using Channel configuration.
- Create a profile list with a mobile number field. Fields whose names include
phone,mobile, ornumberappear under Send to. - For template sends, obtain approval for your RCS templates in Gupshup and confirm they are visible for the selected channel.
- For free-form sends, confirm your agent's platform and conversation-window eligibility using the free-form rules below. Use an approved template when those rules require it.
Create a program
- In Responsys, open Programs → Create Program.
- Enter a name, folder, and profile list, then create the program.
- Drag an App block onto the canvas, double-click it, and select the Gupshup RCS service. The service may be named Send RCS Message or Gupshup RCS Messaging for Oracle Responsys.
- Click Configure app to open the service configuration screen.
- Set Channel, Send to, and your message using either the template or free-form flow below. Click Save, then close the window.
- Connect the App block to a Scheduled Filter, View, or other entry point and to End. Set the filter and Frequency or schedule, then publish.
Service configuration
Use these controls to configure your send:
| Control | Purpose |
|---|---|
| Channels | Select an RCS channel saved in channel configuration. You must select a channel before templates load. |
| Send to | Select the profile field containing the recipient's phone number, in E.164 format or another format your Gupshup account accepts. |
| Categories | Filter templates by TEXT, RICH CARD, or CAROUSEL. |
| Search | Filter templates by name. |
| Custom Param (optional) | Select a profile field for message metadata. Leave blank if unused. |
For both template and free-form sends, set the channel and recipient field at the top of the configuration screen. After you save, Responsys stores the design. Reopen Configure app on the same instance to edit it.
Template message send
Send an approved RCS template from Gupshup and personalize it by mapping each placeholder to a Responsys profile field.
1. Select a template
- Choose Channel and Send to.
- Optionally filter with Categories or Search.
- Under Select a template, review Template name and Type.
- Click Select on the template you want.
| Type in UI | Typical content |
|---|---|
| TEXT | Text body and optional suggested replies. |
| RICH CARD | Standalone card with a title, description, and media. |
| CAROUSEL | Multiple cards in a carousel. |
2. Map placeholders and preview
- On the template detail screen, use Placeholder values to map each token to a Responsys field. Click the parameter icon to open the field picker.
- Map every placeholder. Save stays disabled until all mappings are filled in.
- Use Preview to check the message with your mapped values.
Templates may use placeholders such as [first_name] or other tokens defined in Gupshup. Map each token to the corresponding profile column.
3. Save template configuration
- Click Save.
- Wait for the success confirmation, then close the configuration window.
- Publish and run the program as described in Run the campaign.
Responsys invokes the service for each qualifying contact. At send time, Gupshup delivers the template message using your mapped field values.
Template tips and troubleshooting
- Only templates for the selected channel appear in the list.
- If the list is empty, confirm the templates are Approved in Gupshup and linked to the same HSM account as the channel.
- Rich card and carousel layouts and media come from Gupshup. In Responsys, you primarily map text placeholders.
Free-form message send
Use Free form message builder for non-template RCS messages (messages that are not registered as Gupshup templates). Free-form messages support session-style follow-ups after a customer engages, such as tapping a suggested reply or sending free text. Availability also depends on your agent's platform rules below.
Choose template or free-form mode for each service instance, not both.
Free-form eligibility
Eligibility depends on how your RCS agent was onboarded.
| Agent platform | Non-template messaging rules |
|---|---|
| Vi | Send non-template messages only within a 24-hour conversation window. The window opens when the user engages, for example by clicking a button or sending a message. Outside that window, use an approved template. |
| Jio | Send non-template messages even outside a 24-hour conversation window. This also applies to agents onboarded for international markets, including the USA, Brazil, and Mexico. |
If you are unsure which platform applies to your agent or market, confirm with your Gupshup account team before relying on free-form sends in Program Designer.
1. Open the free-form builder
- Set Channel and Send to as you would for a template send.
- On the Select a template card, click Free form message builder at the top right. You do not need to select a row from the template table.
2. Choose a message type and compose
| Message type | What you configure |
|---|---|
| Text Message | Body text and optional suggested reply buttons. |
| Rich Card Stand Alone | Title, description, orientation or height, and media. Use an image, video, or PDF through a public URL or upload where supported. |
| Rich Card Carousel | Two to ten cards, each with a title, description, and media. |
To personalize content, type [variableName] in text fields for per-recipient values. Map each token to a Responsys field under variable mappings, using the same field picker as template placeholders.
Use the Conversation panel to review a mobile-style preview as you edit. The interface enforces these limits:
| Content | Limit |
|---|---|
| Message body | Up to 2,500 characters. |
| Card title | Up to 200 characters. |
| Card description | Up to 2,000 characters. |
| Suggestions on text or a standalone rich card | Up to 10. |
| Carousel cards | Two to ten. |
3. Save free-form configuration
- Complete the required fields for your message type.
- Map every
[variableName]you used. - Click Save in the composer.
The saved instance uses free-form mode. At runtime, Gupshup sends content messages built from your composition and field mappings.
When to use free-form versus templates
| Use a template | Use free-form |
|---|---|
| Standard marketing or notification content approved in Gupshup. | Follow-up content after the user engages through buttons or free text. |
| Outbound campaigns outside Vi's 24-hour window, or any send where only templates are allowed. | Session replies when Vi's 24-hour window or Jio's non-template rules apply. |
| Content managed through a template approval workflow. | Rich or text content composed in the builder without a template record. |
If a free-form send fails at runtime, confirm the platform (Vi or Jio), market, and conversation-window eligibility with your Gupshup account team. Use an approved template where required.
Optional: Return to template selection
Click Back in the free-form composer to return to the template list without saving.
To replace a saved free-form design with a template:
- Open Configure app.
- Select a template.
- Map its placeholders.
- Click Save.
Run the campaign
- Connect the App block between your audience step (filter or view) and End.
- Set the filter or view and Frequency or schedule on the entry block.
- Publish the program.
When the schedule runs, Responsys sends profile data to Gupshup for each qualifying recipient using Send to and your variable mappings.
See also
Updated about 4 hours ago
