Service Description – Reliable Bulk SMS Services Provider

Introduction

This document lists SMSC Network’s services and defines their chargeable events.

Disclaimer

SMSC Network does not warrant the availability of listed Channels in each country. Geographic coverage of Channels by country shall be agreed upon separately between the Infobip representative and the Customer.

Channels / communication services

SMS

1. Service description

SMSC Network Services include a solution that shall enable the CLIENT to deliver mobile terminated SMS (SMS MT) and receive mobile originated messages (SMS MO) from the End Users of multiple mobile Network Operators worldwide through the Platform.

SMSC Network Services include:

a. Connectivity between CLIENT’s information system and the SMSC Network Platform;

b. Configuration of the Platform to receive traffic generated by CLIENT and the handling and routing of such SMS traffic, as well as traffic received from the Network Operators for the CLIENT (if applicable);

c. Billing of such SMS traffic processed by SMSC Network; and

d. Technical Support.

In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:

a. Ensure that connectivity between CLIENT’s information system and the Platform is tested and operational;

b. Route SMS traffic generated by CLIENT to available Network Operators;

c. Route SMS traffic originating from the Network Operator End Users to the CLIENT’s information system (if applicable);

d. Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;

e. Manage all contractual relationships with Network Operators to ensure the operability of the SMSC Network Services.

Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:

a. Provide all the configuration information through the proper completion of all technical forms provided by SMSC Network;

b. Ensure that its own information systems are properly configured to:

i. route SMS traffic to the Platform, and

ii. receive inbound traffic from the Platform (if applicable);

c. Ensure that an appropriate Service Request shall first have been received from the End User;

d. Create and maintain at its own expense an updated database containing respective Service Requests as well as OPT OUT/STOP Requests for End Users receiving each message processed by SMSC Network, and

i. Retain for the necessary period under the applicable law evidence that each message sent to that End User was sent in response to a Service Request that had been subject to proper validation;

ii. Provide such evidence to SMSC Network upon written request giving 5 days’ notice;

e. Ensure under no circumstances to send Unsolicited SMS (SPAM) to the messaging Platform;

f. Announce a larger volume of traffic within 5 business days in advance.

g. Fulfill all its payment obligations.

2. Chargeable event and other Particulars

“MT Chargeable Event” means SMS sent by CLIENT to SMSC Network which is subject to Successful Submit by SMSC Network to destination Network Operator;

“MO Chargeable Event” shall mean SMS sent by the End User which is successfully accepted by SMSC Network Platform;

“Network Operator” means any company operating a GSM or CDMA-based mobile telephony network, offering mobile telephony services to its subscriber base;

“Successful Submit” means SMSC Network accepts the SMS sent from the CLIENT and validate the SMS before submitting SMS for onward routing. SMSC Network shall return Successful Submit to the CLIENT to register SMS has been successfully submitted for routing and then delivered by Network Operator to End-User. SMS which does not pass SMSC Network’s validation tests is rejected and error message returned to the CLIENT and SMS not charged.

MMS

1. Service description

SMSC Network Services include a solution that shall enable the CLIENT to deliver mobile terminated MMS messages (MMS MT) and receive mobile originated MMS messages (MMS MO) from the End Users of multiple mobile Network Operators worldwide through the Platform.

SMSC Network Services include:

a. Connectivity between CLIENT’s information system and the SMSC Network Platform;

b. Configuration of the Platform to receive traffic generated by CLIENT and the handling and routing of such MMS traffic, as well as traffic received from the Network Operators for the CLIENT (if applicable);

c. Billing of such mms traffic processed by SMSC Network; and

d. Technical Support.

In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:

a. Ensure that connectivity between CLIENT’s information system and the Platform is tested and operational;

b. Route MMS traffic generated by CLIENT to available Network Operators;

c. Route MMS traffic originating from the Network Operator End Users to the CLIENT’s information system (if applicable);

d. Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;

e. Manage all contractual relationships with Network Operators to ensure the operability of the SMSC Network Services.

Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:

a. Provide all the configuration information through the proper completion of all technical forms provided by SMSC Network;

b. Ensure that its own information systems are properly configured to:

i. route MMS traffic to the Platform, and

ii. receive inbound traffic from the Platform (if applicable);

c. Ensure that an appropriate Service Request shall first have been received from the End User;

i. Retain for the necessary period under the applicable law evidence that each message sent to that End User was sent in response to a Service Request that had been subject to proper validation;

ii. Provide such evidence to SMSC Network upon written request giving 5 days’ notice;

e. Ensure under no circumstances to send Unsolicited MMS (SPAM) to the messaging Platform;

f. Announce a larger volume of traffic within 5 business days in advance.

g. Fulfill all its payment obligations.

2. Chargeable event and other Particulars

“MT Chargeable Event” means MMS sent by CLIENT to SMSC Network which is subject to Successful Submit by SMSC Network to destination Network Operator;

“MO Chargeable Event” shall mean MMS sent by the End User which is successfully accepted by SMSC Network Platform;

“Network Operator” means any company operating a GSM or CDMA-based mobile telephony network, offering mobile telephony services to its subscriber base;

“Successful Submit” means SMSC Network accepts the MMS sent from the CLIENT and validate the MMS before submitting MMS for onward routing. SMSC Network shall return Successful Submit to the CLIENT to register MMS has been successfully submitted for routing and then delivered by Network Operator to End-User. MMS which does not pass SMSC Network’s validation tests is rejected and error message returned to the CLIENT and MMS not charged.

RCS

1. Service description

SMSC Network Services include a solution that shall enable the CLIENT to deliver mobile terminated RCS and receive mobile originated messages from the End Users of multiple mobile Network Operators worldwide through the Platform in form of free text, images, suggestion (postback of the message degined within the MT), location (latitude, longitude) a file or otherwise.

SMSC Network Services include:

a. Connectivity between CLIENT’s information system and the SMSC Network Platform;

b. Configuration of the Platform to receive traffic generated by CLIENT and the handling and routing of such RCS traffic, as well as traffic received from the Network Operators, Google or other RCS enablers, for the CLIENT (if applicable);

c. Billing of such RCS traffic processed by SMSC Network; and

d. Technical Support.

In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:

a. Ensure that connectivity between CLIENT’s information system and the Platform is tested and operational;

b. Route RCS traffic generated by CLIENT to available Network Operators, Google or other RCS enablers as required;

c. Route RCS traffic originating from the Network Operator End Users to the CLIENT’s information system (if applicable);

d. Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network Service;

e. Manage all contractual relationships with Network Operators, Google or other RCS enablers to ensure the operability of the SMSC Network Services.