Introduction
The SMS Panel is the self-service home for bulk SMS on Splashify. This manual walks every screen in it, in the order you will meet them.
SMS is the oldest messaging channel and still the most reliable one: it needs no app, no data connection and no smartphone. In India it is also the most regulated. Every business that sends commercial SMS must register itself, its sender name and the exact wording of its messages with a government-mandated registry before a single message can leave.
The panel at sms.splashifypro.com is where you do all of that and then send.
This manual, and the API reference
Two documents live on this site. The user manual (you are in it) describes the panel screen by screen and assumes no coding. The API reference documents sending as REST endpoints, for wiring Splashify into your own systems. Registration is panel-only, so the two are not mirror images of each other.
Who the panel is for
The panel is a standalone product for SMS customers. If you signed up at
sms.splashifypro.com, this is your surface, and this manual describes
everything you have access to.
It is deliberately separate from Splashify's other panels. If you use any of those as well, they live in different apps with their own logins, their own wallets and their own docs. Nothing you do here affects them.
The moving parts
Five concepts carry the whole product, and four of them exist because of regulation rather than because of us.
- Entity
Your business, registered on a DLT portal. You get a 19-digit Principal Entity ID. Everything else hangs off it.
- Chain
The declaration on your DLT portal that says which telemarketers are allowed to carry your traffic. This is the step most often missed, and missing it means every message is rejected.
- Sender ID
The six characters the message appears to come from, like
SPLSFY. Also called a header.- Template
The exact wording of a message, with
{"{#var#}"}where the changing parts go. Approved once, then reused. You cannot send text that is not an approved template.- Wallet
Prepaid balance. Messages are charged per part, not per message, which the parts page explains.
The order things happen in
Registration is sequential and each step depends on the one before it. Doing them out of order is the most common reason a first send takes a week instead of a day.
Create your Splashify account
Sign up at the panel and verify your email. See Getting started.
Register your entity on a DLT portal
On Jio, Airtel, Vi or BSNL. You do this directly with them, not through us, and you come back with a 19-digit Principal Entity ID. See Register your entity.
Declare the chain
Add the telemarketer ID shown on your panel's Chain page. See Chain declaration.
Register a sender ID and your templates
On the same DLT portal, then add them to the panel so we can match them. See Sender IDs and Templates.
Add funds and send
See Send a message.
Steps 2 to 4 happen on a DLT portal, not here
Registration is done by you, directly with a DLT operator, because the registry records your business as the sender. We cannot do it on your behalf, and nobody who offers to should be believed. What the panel does is hold the resulting IDs, check them, and use them correctly when you send.
What the panel does not do
Being clear about this early saves a support ticket later.
- It does not register you. DLT registration is yours to do. The panel stores what you registered and sends against it.
- It does not approve your templates. A DLT portal does. The panel's own review is a second check that what you entered matches what was approved, so that a mismatch is caught before it costs you a send.
- It does not decide whether a message reaches a handset. The operator does, and the delivery page explains what the outcomes mean.