Plug InterConnect Into Your CRM and Stack
Keep your segmentation, journeys and triggers where they already live. InterConnect handles the delivery.
InterConnect Solutions is the messaging layer behind your CRM: your platform decides who receives which message and when, and InterConnect delivers it over SMS, WhatsApp, Viber, Telegram, RCS or voice, with cascade fallback between channels and delivery receipts returned over webhooks. Customer.io and Planfix connect without custom development; any other system connects over HTTP API or SMPP.
Which CRMs connect out of the box?
Customer.io and Planfix connect to InterConnect without custom development — a campaign step on their side fires a message on ours, and delivery events flow back.
Customer.io
A campaign or journey step in Customer.io fires a message through InterConnect the moment a player enters the segment — a deposit reminder, a bonus drop, a reactivation nudge from your playbooks. The message travels down your configured cascade, for example Viber → WhatsApp → SMS, and delivery events flow back so your journey logic can branch on what actually arrived.
Setup in three steps:
- Create an API key in the InterConnect client portal.
- Add InterConnect as a webhook destination in your Customer.io campaign action.
- Map recipient and message fields, choose a cascade, and send a test message.
Planfix
A Planfix process rule triggers the send: when a task reaches a stage or a contact matches a filter, Planfix calls InterConnect and the message goes out over the channel chain you configured. Delivery receipts come back over webhooks and can update the task or contact record, so managers see delivered-or-failed status without leaving Planfix.
Setup in three steps:
- Create an API key in the InterConnect client portal.
- Add an outgoing API call to InterConnect in your Planfix process or automation rule.
- Map contact and message fields, choose a cascade, and run the rule on a test task.
How do the API, SMPP & webhooks work?
You send over HTTP API or an SMPP bind, and InterConnect pushes delivery receipts back to your endpoint over webhooks — the same interface for promo traffic and OTP.
API/SMPP/HTTP option
Send with a single REST call or a classic SMPP bind — whichever your backend already speaks, no stack changes required.
Webhooks & reporting
Per-message delivery receipts pushed to your endpoint, including which cascade step actually delivered and was billed.
Opt-in/out flows
Consent is captured on the way in and suppression lists are checked automatically before every send, on every channel.
Short-link tracking
Trackable short links inside messages, so clicks — and the deposits behind them — attribute back to the exact campaign.
DND handling
Quiet hours and do-not-disturb rules are applied per player and per GEO before a message ever leaves the queue.
Audit-ready unsub portal
A hosted unsubscribe portal where every opt-out is logged with a timestamp — evidence you can show a regulator.
Sending a message with a cascade
POST /v1/messages
Content-Type: application/json
{
"to": "+447700900123",
"text": "Your weekend bonus is live. Claim it here: {short_link}",
"sender": "YourBrand",
"cascade": ["telegram", "viber", "sms"],
"callback_url": "https://crm.example.com/webhooks/interconnect"
}Delivery receipt pushed to your webhook
POST https://crm.example.com/webhooks/interconnect
Content-Type: application/json
{
"message_id": "msg_7f2a91",
"to": "+447700900123",
"status": "delivered",
"channel": "viber",
"billed_channel": "viber",
"timestamp": "2026-07-18T14:32:07Z"
}These examples are illustrative — field names are simplified for readability. The full API reference, SMPP connection details and sandbox credentials are available in the client portal.
What compliance is built in?
Opt-out enforcement, an auditable unsubscribe portal and DND windows are part of the platform — not features you have to build around it.
Opt-out enforced everywhere
When a player opts out on any channel, the suppression applies across all of them. Your CRM does not need to synchronize unsubscribe lists per channel — InterConnect checks every send against the current suppression state before delivery.
Unsubscribe portal with audit trail
Every opt-out lands in a hosted unsubscribe portal with a full audit trail: who opted out, when, and from what. If a regulator or platform asks how a complaint was handled, the evidence is already recorded.
DND windows
Do-not-disturb handling holds messages outside permitted hours, so a journey triggered at 3 a.m. does not become a complaint at 3 a.m. Rules are applied at the delivery layer, whatever time your CRM fires.
We process personal data only to deliver messages on the operator's behalf, and a GDPR data processing agreement is available as part of onboarding. See our privacy policy for how data from this site is handled.
Go live in days, not sprints
Tell us what your stack looks like — Customer.io, Planfix, an in-house engine over HTTP or SMPP — and we will map the fastest route to your first delivered cascade, with pricing quoted per GEO.