User GuideDeveloper GuideTechnology Partners
User Guide
BlogLogin

Multi-Vendor Support with Jio Integration

Netcore RCS now supports Jio along with VI as a RCS Vendor

Suggest Edits

Overview

Netcore RCS now supports Jio as a vendor, expanding beyond the earlier VI-only setup—giving you wider reach and better delivery. Take advantage of Google-supported features like rich cards, carousels, quick-reply buttons, and text templates.

Jio API Integration

Send RCS messages via Jio, alongside existing VI support.

Vendor Selection

Use CaseVendor Behavior
DomesticOnly one active vendor at a time (Jio or VI) on a single panel.

Template Management

  • Jio does not require template approvals.
  • Templates must still be created on the Netcore CE dashboard. Status for these templates will be automatically approved.
  • Existing Template APIs remain unchanged.

🧾

Billing and Data Migration

  • Vendor migration such as VI to Jio occurs only at the end of each month.
  • Historical data (templates, reports, billing logs, campaign data) remains accessible on the dashboard post-migration.

User Guide

1. Creating Templates

For Jio, you need to create templates even though no approval is needed. Templates are managed at the panel level. Refer to the given document to create RCS campaign & templates.

2. Sending Messages

  • If Jio is your active vendor, messages will be routed via Jio.
  • No configuration changes are needed from the user side.

3. Vendor Migration Process

Reach out to your Account manager in case you want to migrate. You need to inform us during migration which bots do you want to map where and here you can also set up your NC BOT NAME.

Handled by Netcore's SRE team at the end of the month.

  • No manual intervention required.
  • All existing data remains available in the dashboard and reports.

API Behavior

APIs remain unchanged and are compatible with VI and Jio.

📘

Note

Your Netcore Bot ID remains unchanged even if you migrate from VI to Jio.

Understanding Netcore Bot ID & Bot Name

1. Netcore Bot Name:
This is the bot name you see on the dashboard. It represents your bot in Netcore's interface and is primarily used for easy identification. This will remain same regardless of the vendor.

2. Assistant Name / Business Display Name:
This is the bot name configured on the vendor's panel. It’s what end-users see during conversations.

3. Netcore Bot ID:
This is a unique identifier tied to each bot. If you're managing multiple bots, you must enter the Netcore Bot ID in the Bot ID field in the API , to ensure the right bot is referenced.

4. Where to Configure:
All relevant fields—Netcore Bot Name, Bot ID, and Business Display Name—are available on the CPaaS Settings page.

Updated 1 day ago