Communication integrations

SMS CRM integration with no gateway to sign up for

Setting up the SMS CRM integration means adding the DLT details you already registered with your telecom operator — your entity id, sender header and approved templates — because DigiPix Flow sends text messages itself. From then on every text is checked against them, comes back with a delivery status, and gets its replies on the same thread.

  • No SMS account, API key or gateway to set up
  • Your DLT entity id and templates copied in once
  • Replies and STOP messages come back to the thread
An example of the DigiPix Flow Settings page for SMS — India DLT, with the Principal Entity (PE) id, the Refuse unmatched SMS switch, the SMS sender ID RAOINT and a registry of DLT templates, beside a panel of recent SMS. The PE id is pasted in and saved, the template site_visit_reminder is registered and goes Active, an SMS to Priya Sharma matching that template shows Delivered, and her STOP reply is recorded as an opt-out.
SMS accounts or API keys to set up
0
characters in a DLT sender header for +91 numbers
6
characters allowed in each template variable
30

What SMS setup is made of

  • Principal entity idFrom your DLT portal registration
  • Sender IDThe name a handset shows as the sender
  • DLT templatesTemplate id, header, category and wording
  • Matching ruleRefuse texts that fit no active template
  • Delivery statusDelivered, or failed with its code
  • Inbound keywordReplies and STOP back on the thread
THE PROBLEM

Where business texting usually goes wrong

See how it's fixed
  1. A second login just to send a text

    Most teams open an account with an SMS company, buy a package, generate an API key and wire it into their CRM before a single reminder can go out. Then someone has to watch the balance, rotate the key and chase support when messages stop.

  2. Texts dropped for a single word

    Indian operators check every commercial SMS against the template registered on the DLT portal. Change one word, send under the wrong header or use the wrong category, and the message is quietly discarded. The rep only hears about it when the customer says nothing arrived.

  3. Replies that land nowhere

    A customer answers the delivery reminder, or texts STOP, and the message sits in a portal nobody on the sales team opens. The question goes unanswered, and the next campaign reaches someone who has already asked you to stop.

NOTHING TO CONNECT

SMS is ready without a provider account

There is no SMS company to sign up with and no API key to paste. DigiPix Flow sends text messages itself, so the SMS channel is available the moment your workspace exists. Setup is only the part the Indian rules ask of you: the entity id, sender header and templates you registered with your operator.

  • Sent by DigiPix Flow, with no gateway or key to manage
  • Three things to add: entity id, sender ID and templates
  • Trial workspaces can try up to 50 messages a month
  • A monthly SMS allowance for every workspace
An example of the SMS channel in DigiPix Flow for Rao Interiors: SMS is ready and sent by DigiPix Flow with no provider account or API key, a note that a monthly SMS allowance applies, and a checklist of what to add for India, with the entity id and sender ID done and DLT templates still to register.
ENTITY & SENDER ID

Your entity id and the name customers see

Paste the Principal Entity (PE) id from your DLT portal registration into Settings → Communication. Then set the SMS sender ID, the name a handset shows at the top of the message. It can be up to 11 letters or digits, but messages to Indian (+91) numbers need exactly six letters, and the field tells you plainly when a sender ID won't be used for them.

  • Principal Entity (PE) id from your DLT registration
  • A sender ID of up to 11 letters or digits
  • Exactly six letters for Indian (+91) numbers
  • A plain note when a sender ID won't work for India
An example of the SMS — India DLT settings in DigiPix Flow: the Principal Entity (PE) id field filled in from the DLT portal, the SMS sender ID set to RAOINT with the rule that it can be up to 11 letters or digits and Indian numbers need exactly 6 letters, and a longer sender ID flagged as not used for +91 numbers.
REGISTER TEMPLATES

Copy your approved DLT SMS templates in, word for word

You register templates on your DLT portal with your operator; DigiPix Flow keeps a copy so it can check every text against them. Add each one with its name, DLT template id, six-character sender header and category, then paste the approved content exactly as the portal shows it. An insert button places each {#var#} for you, and the form counts the variables as you go.

  • Name, DLT template id and six-character sender header
  • Transactional, Service (implicit), Service (explicit) or Promotional
  • Approved content pasted exactly, with {#var#} inserted in a click
  • Each variable accepts up to 30 characters
An example of the Register DLT template form in DigiPix Flow: the name site_visit_reminder, a DLT template id copied from the portal, the six-character sender header RAOINT, the Service (implicit) category chosen from four, the approved content pasted with two variable placeholders and an Insert variable button, a note that each variable accepts up to 30 characters, and the Active box ticked.
TEMPLATE REGISTRY

A template registry that keeps its history

Every registered template sits in one list with its DLT id, header, category and wording, and a count of its variables. Templates you no longer use are switched to inactive rather than deleted, so an old message can always be traced to the wording it was sent under. Every change to the registry is written to the audit log with who made it.

  • Name, DLT id, header, category and content in one table
  • Active or inactive, with inactive templates hidden by default
  • Deactivated when retired, never deleted
  • Every change recorded in the audit log
An example of the DLT template registry in DigiPix Flow: five templates with their DLT ids, sender headers, category chips from Transactional to Promotional and variable counts, four ticked Active and one deactivated rather than deleted, shown because Show inactive is on, above an audit trail of who registered, updated and deactivated templates.
MATCHING

Refuse the texts an operator would drop

When a rep writes an SMS to an Indian number, DigiPix Flow matches the wording against your active templates and shows which one it fits. Switch on Refuse unmatched SMS and a text that fits none is stopped before it is queued, instead of vanishing at the operator. If the switch is on while no template is active, Settings warns you that every SMS to India would be refused.

  • Composer wording matched to an active template
  • Refuse unmatched SMS, switched on when you're ready
  • A warning when refusal is on with no active templates
  • Numbers must be in +91… international format, or the send is refused
Explore WhatsApp and SMS
An example of DLT matching in DigiPix Flow: the Refuse unmatched SMS switch is on, an SMS composer to Neha Patil at +91 98450 21763 shows its wording matched to the active template site_visit_reminder, a second draft that fits no template is refused before it is queued, and a warning explains that with refusal on and no active templates every SMS to an Indian number would be refused.
PROMOTIONAL HOURS

Promotional SMS kept to 10:00–21:00 IST

Indian rules only allow promotional texts during the day. A message sent under a template in the Promotional category outside 10:00 to 21:00 IST is held and goes out when the window opens, whether it came from a sequence, a workflow or a rep. Transactional and service templates aren't held by this rule, though automated sends still wait out your workspace's quiet hours.

  • Promotional templates held outside 10:00–21:00 IST
  • Released when the window opens, not dropped
  • Transactional and service templates not held by this rule
  • Automated texts also respect your quiet hours
Explore sequences
An example of DigiPix Flow holding promotional SMS outside 10:00 to 21:00 IST: at 22:10 a day timeline shows the promotional window, two monsoon_offer texts from a sequence are held until 10:00 IST, while a transactional payment receipt sent earlier in the evening and a hand-typed service reminder went out.
DELIVERY

Delivered, or failed with a reason

Every SMS comes back marked delivered or permanently failed, and a failure carries the code the network returned, so a rep can tell a mistyped number from an opted-out one. When the number is dead — invalid, unreachable or opted out — DigiPix Flow also stops the sequence or workflow that sent the text, so it doesn't keep trying the same number.

  • Delivered or permanently failed on every message
  • The failure code shown on the message
  • A dead number stops the sequence that texted it
  • Workflows that sent the SMS stop too
Explore the unified inbox
An example of SMS delivery status in DigiPix Flow: three texts marked delivered and one to Rohan Desai permanently failed with the code for an unreachable number, and because the number is dead, the New enquiry follow-up sequence that sent it has been stopped for him.
REPLIES & STOP

Replies and opt-outs come back to the right thread

Replies arrive on a shared two-way number. An answer from someone your workspace texted goes back to your workspace and onto the conversation. Customers who text first start with your keyword — Settings shows them the exact line to use. A STOP reply withdraws SMS consent and START undoes only what that STOP changed, while consent, do-not-contact and quiet hours keep applying to every send.

  • Replies routed back to the workspace that last texted the number
  • A keyword for customers who text you first
  • STOP withdraws consent; START undoes only that STOP
  • Hand-typed replies go straight out; automated texts wait out quiet hours
Explore consent and opt-outs
An example of SMS replies in DigiPix Flow: the Inbound replies setting with the keyword RAO and the line Customers text RAO your message to +91 80 6911 4420, and an SMS thread with Priya Sharma where her reply to a site visit reminder comes back to the same conversation, followed by her STOP message, which withdraws her SMS consent, with a note that START would undo only that change.
HOW IT WORKS

From DLT registration to a delivered text, in five steps

  1. STEP 01

    Register with your operator

    Register your entity, sender headers and templates on the DLT portal.

  2. STEP 02

    Add your entity and sender ID

    Paste the PE id and set the sender ID in Settings → Communication.

  3. STEP 03

    Copy in your templates

    Register each approved template with its id, header, category and wording.

  4. STEP 04

    Decide how strict to be

    Switch on Refuse unmatched SMS once your active templates are in.

  5. STEP 05

    Send and hear back

    Texts show delivered or failed, and replies land on the thread.

THE DIFFERENCE

SMS in DigiPix Flow vs a separate SMS portal

What it coversA separate SMS portalDigiPix Flow
Getting startedSign up, buy a package, generate an API keyNothing to connect; add your DLT details
DLT template checksFound out when texts go missingWording matched to your active templates before sending
Retired templatesDeleted, with no record of the old wordingDeactivated, with every change audited
Promotional timingSent whenever someone presses the buttonHeld outside 10:00–21:00 IST
Failed messagesA report to download and read laterThe failure code on the message, and the sequence stopped
Customer repliesKept in the portal's own inboxBack on the thread, next to the record
STOP requestsCopied to a spreadsheet by handSMS consent withdrawn automatically
INTEGRATIONS

The other channels you can set up

SMS goes out through DigiPix Flow's own sending, so there is nothing to connect. The other communication channels set up alongside it, and their conversations share the same inbox.

SMS setup questions, answered

Do I need an account with an SMS company?

No. DigiPix Flow sends SMS itself, so there is no provider account, API key or gateway to set up. What you do need for Indian numbers is your DLT registration: your entity id, sender headers and approved templates, which you add in Settings → Communication.

Does DigiPix Flow register our templates on the DLT portal?

No. Your business registers its entity, headers and templates on the DLT portal with your telecom operator, as Indian rules require. Once they are approved, you copy the IDs and wording into DigiPix Flow so every text can be checked against them before it goes out.

What sender ID can we use?

The SMS sender ID can be up to 11 letters or digits. Messages to Indian (+91) numbers need exactly six letters, which is also the length of a DLT sender header, and Settings tells you when a sender ID won't be used for them.

What happens if a message doesn't match a template?

DigiPix Flow matches the wording of a text to an Indian number against your active templates. With Refuse unmatched SMS switched on, a text that fits none is stopped before it is queued. If the switch is on while no template is active, Settings shows a warning, because every SMS to India would be refused.

Can we delete a DLT template we no longer use?

Templates are deactivated rather than deleted, so a message sent months ago can still be traced to the wording it went under. Inactive templates are hidden from the list by default, and every change to the registry is recorded in the audit log.

When do promotional texts go out?

A text under a Promotional template is sent between 10:00 and 21:00 IST. One queued outside that window is held and released when it opens. Transactional and service templates aren't held by this rule, although automated messages still wait out your workspace's quiet hours.

How do we know a text was delivered?

Each message is marked delivered or permanently failed, and a failure shows the code the network returned. If the number is dead because it is invalid, unreachable or opted out, the sequence or workflow that sent the text is stopped as well.

Where do customer replies go?

Replies come in on a shared two-way number. A reply from someone your workspace texted is routed back to you and lands on that conversation. Customers who text first start their message with your inbound keyword, and Settings shows the exact line to give them.

How many texts can we send?

Each workspace has a monthly SMS allowance, and trial workspaces can try SMS with 50 messages a month. Every text still passes consent, do-not-contact and quiet-hours checks, and numbers must be written in international format, starting +91 for India.

Something we haven't covered? Talk to an expert

Start texting customers without another account to manage

Talk to an expert — bring your DLT entity id and approved templates, and see a text go from registry to delivered to reply.

  • A real person, not a bot
  • Bring your DLT entity id
  • See a reply land on the thread
Talk to an expert