Digital Connect: every question a buyer asks

The service that takes a message from your application, by API, and delivers it onto the mobile networks that terminate it, handling the operator connections, sender identities, routing and delivery reporting in between. The gateway is also where the differences between providers live: which operator routes they use, how failures are detected and moved, and what the delivery receipt actually proves.

Yes. REST suits application-generated traffic and is quicker to integrate. SMPP suits sustained high-volume SMS, where a persistent binding is more efficient than per-message HTTP calls. Which one is right depends on your volumes and how your sending system is built.

Yes. WhatsApp, Facebook Messenger, Instagram, website live chat and in-app chat are all handled as conversational channels, not just outbound delivery.

Yes, through the in-app mobile chat SDK, so a support conversation happens inside your application rather than sending the customer to a different channel.

Yes, and it is the traffic class that most deserves attention during evaluation. Ask any CPaaS provider, including this one, about delivery latency and success rates specifically for OTP on each Saudi mobile network, rather than about blended averages across all traffic, and insist on a parallel run against your own traffic before cutover.

By Interkey, as part of onboarding: sender identities are registered before your traffic needs them, with the evidence and approvals that involves handled as administrative work rather than left with your developers. The sender ID registration guide explains the whole process, including what to expect if you are currently sending through a global platform that never registered one.

The ones that shape a deployment: A2P messaging operates under CST (formerly CITC) regulation, sender identities must be registered for traffic to terminate reliably, and message categories are treated differently on the networks. These answers describe the practical consequences rather than restating regulation; for compliance sign-off, put the specific questions to your provider in writing, and Interkey will answer its own the same way.

A fair question with several parts: message content in transit, delivery receipts, and the customer data your integration carries. Ask any provider to answer each part separately and in writing, because they often have different answers. Interkey documents its answer during scoping, and the platform’s own documentation at connect.interkey.com.sa carries the detail.

Since mid-2025, Meta bills WhatsApp Business API messages per message, priced by template category: marketing, utility and authentication templates carry different rates, and service replies inside the customer window are free. Rates change with notice, so treat any specific number, from anyone, as dated. What a provider like Interkey adds is the integration, template management and delivery layer on top; pricing is modelled against your actual traffic mix during scoping.

Six things, and all of them in writing: regulatory position, sender ID responsibility, per-operator OTP evidence, Arabic message economics, support hours against the Saudi working week, and the contracting entity. The vendor qualification checklist on the Digital Connect overview is designed to be taken to every vendor on the shortlist, including this one.