The short answer
- Templates first: recurring messages go out from templates approved by your team and by Interkey, which keeps wording consistent.
- Permission levels: admins and users get different rights, and the platform login uses two-factor authentication with a verification code sent by email.
- Scheduling: set when a campaign goes out, instead of sending the moment it is ready.
- Reports: see performance and delivery results, and export reports for your own records.
How a team works in the platform
| Step | What happens | Who usually does it |
|---|---|---|
| 1. Set up access | Users are given admin or user permission levels and sign in with two-factor authentication | Your platform admin |
| 2. Prepare templates | Each recurring message is written once as a template, then approved by your team and by Interkey before use | Content owner, with compliance input; then Interkey |
| 3. Manage contact lists | Recipient lists are managed in the platform; include only customers who agreed to hear from you | Marketing or CRM team |
| 4. Schedule | A campaign is scheduled for the time you choose | Campaign owner |
| 5. Report | Performance and delivery results are reviewed and exported | Campaign owner, operations |
Messages your systems trigger, such as passcodes and order updates, are sent through the API rather than by hand, and are covered by the same delivery reporting, with a delivery receipt for each message.
Approved templates: write once, send consistently
A template is a fixed message with a few fields that change for each recipient, such as a name, an order number or a date. Approving templates in advance protects you from two common problems: a promotional line slipping into a service message, and a typo going to thousands of customers.
Examples of a template set
| Purpose | Type | English example | Arabic example |
|---|---|---|---|
| Passcode | Transactional | {code} is your verification code. Do not share it with anyone. | رمز التحقق الخاص بك: {code}. لا تشاركه مع أي شخص. |
| Order update | Transactional | Your order {order_no} has been shipped and will arrive on {date}. | تم شحن طلبك رقم {order_no} ويصل بتاريخ {date}. |
| Appointment reminder | Transactional | Reminder: your appointment at {branch} is on {date} at {time}. | تذكير: موعدك في {branch} يوم {date} الساعة {time}. |
| Payment reminder | Transactional | Your bill of {amount} SAR is due on {date}. | فاتورتك بمبلغ {amount} ريال تستحق في {date}. |
| Offer | Promotional | {brand}: {offer} until {date}. To unsubscribe: {opt_out}. | {brand}: {offer} حتى {date}. لإلغاء الاشتراك: {opt_out}. |
Tips for a template library:
- Keep service and promotional templates separate. A shipping update with a discount line generally becomes a promotional message, with stricter consent and timing rules.
- Write the Arabic and English versions as two templates, not one translated on the fly. Each should read naturally in its own language.
- Check length before approval. Arabic text fits fewer characters per SMS segment than English, so a template that is one segment in English can be two in Arabic.
- Name templates by purpose and language, for example "order-shipped-ar", so users pick the right one.
- Review the library regularly, and retire templates for offers that have ended.
In Digital Connect, every template is approved by your team and by Interkey before it is used, so the wording that reaches customers has been checked on both sides.
Check a template's length in the SMS segment calculator
Campaign scheduling
Campaigns can be scheduled to go out at the time you choose, instead of being sent the moment someone presses a button. Use scheduling to:
- Send within permitted hours. Promotional messages in Saudi Arabia are expected to respect restricted hours; schedule campaigns inside the window your compliance team has confirmed.
- Split a large list into several scheduled sends, so delivery and your customer service team are not overwhelmed at once.
- Prepare in working hours, send at the right hour, for example a campaign approved on Thursday that should go out on Saturday evening.
Transactional messages such as passcodes and order updates should not wait for a schedule: send them when the event happens.
Reports on performance and delivery
The platform reports on performance and delivery results, with a delivery receipt for each message, and reports can be exported. After each campaign, check:
- How many messages were delivered and how many failed.
- Which numbers keep failing, so you can clean the list before the next send.
- Opt-out requests your team has received since the last send, so they are removed from the list before the next one.
For delivery status inside your own systems, use the API and its delivery report states.
Delivery report states, explained for developers
Access: permission levels and two-factor login
The platform login uses two-factor authentication with a verification code sent by email, and users work at admin or user permission level, so a campaign assistant does not need the same rights as the person who manages templates and users. Your systems connect to the API from whitelisted IP addresses or over a VPN connection.
Security and access controls in Digital Connect
How Digital Connect fits
- Business SMS from one platform: campaigns from the web platform, and system-triggered messages through the API.
- Account protection: fraud protection, country blocking and spending limits.
- Interfaces for your applications: REST, SMPP for high-volume SMS, or SOAP where an existing business system requires it.
- Sender name registration with the regulator and the operators, handled during onboarding.
- Support from Riyadh on the Saudi working week, in Arabic and English.
- Pricing is quoted for your volumes.
When it is not a good fit: if almost all of your recipients are outside Saudi Arabia, or you send only a few hundred messages a month.
Questions teams ask about the platform
Can a user send a message without a template?
The platform supports pre-approved templates for the messages your team sends regularly. Agree inside your team which messages must always go from an approved template, and ask us during onboarding how this is set up for your users.
Who approves our templates?
Templates are approved by your team and by Interkey before they are used. Agree inside your team who signs off a new template before it goes to Interkey.
Can we schedule a campaign for later?
Yes. Campaigns can be scheduled to go out at the time you choose. Send transactional messages such as passcodes when the event happens, not on a schedule.
Can we export reports?
Yes. Reports on performance and delivery results can be exported.
Can we use the platform and the API together?
Yes. Your team can run campaigns in the platform while your systems send passcodes and alerts through the API, with one set of delivery reporting for both.