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 SMS 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;
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 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 MMS 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 (Rich Communication Service)
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.
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.
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 RCS traffic to the Platform, and
ii. receive inbound traffic from the Platform (if applicable);
c. Ensure that an appropriate opt-in 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 RCS (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 RCS Particulars
“Chargeable Event” or „MT Chargeable Event“ means RCS sent by CLIENT to SMSC Network which is successfully delivered by SMSC Network to the End-User;
“MO Chargeable Event” shall mean RCS 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;
“Rich Communication Services” is a communication protocol between mobile-telephone carriers and between phone and carrier which enables to transmit messages containing multimedia content, rich text and other capabilities which may vary depending on the Operator(s);
“Rich SMS” means the message sent to and from telephones whose content comprises words, numbers, rich text, multimedia or other;
“Successful Submit” means SMSC Network accepts the RCS message sent from the CLIENT and validates the RCS message before submitting it for onward routing. SMSC Network shall return Successful Submit to the CLIENT to register RCS message has been successfully submitted for routing and then delivered by Network Operator to End-User. Any RCS message which does not pass SMSC Network’s validation tests is rejected and error message returned to the CLIENT. Such RCS message is not charged.
WhatsApp Business Platform
1. Service description
SMSC Network Services features a solution that shall enable CLIENT to deliver mobile terminated messages to the WhatsApp Platform through the SMSC Network Platform.
SMSC Network Services include:
Connectivity between CLIENT’s information system and the SMSC Network Platform;
Configuration of the SMSC Network Platform to receive WhatsApp traffic generated by CLIENT and the handling and routing of such WhatsApp traffic to the WhatsApp Platform;
Billing of such WhatsApp traffic processed by SMSC Network.
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route WhatsApp traffic generated by CLIENT to the WhatsApp Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage all contractual relationships with WhatsApp to ensure the operability of the SMSC Network Services.
Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route WhatsApp traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of WhatsApp Users receiving each message processed by SMSC Network;
Ensure under no circumstances to send unsolicited messages (SPAM) to the messaging Platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfil all its payment obligations
The SMSC Network WhatsApp service entails two different options in terms of hosting senders that CLIENT will be able to choose from prior to sender registration:
SMSC Network hosting – sender/service will be provided via WhatsApp On-Premises API, hosted by SMSC Network, within SMSC Network’s systems either on SMSC Network’s own hardware infrastructure or in virtual resources on a public cloud providers’ infrastructure (Microsoft Azure);
Cloud hosting (beta) – sender/service will be provided via WhatsApp Cloud API, hosted by Meta.
Sender can be migrated to another hosting option, if agreed so with the client.
2. Chargeable event and other WhatsApp Particulars
“Chargeable Event” means any and all messages sent through the WhatsApp Business API and which will be charged on a per conversation basis. WhatsApp defines a conversation as a fixed 24-hour session of unlimited messaging between a person and a business sender. The 24-hour conversation session begins when:
A business-initiated message is delivered to a user, outside of a 24 hour customer-care window (business-initiated conversation)
A business reply to a user message is delivered within the 24 customer-care hour window (user-initiated conversation)
In both cases, the conversation session begins when the business’ message is delivered. When businesses initiate messages to users (templated messages), this will initiate a conversation, regardless of whether users reply to that message within the next 24 hours. There is no limit on the number of messages a business and a user can exchange in a single 24-hour conversation session.
“Customer Support Window (CSW)” means period of 24 hours starting from the last WhatsApp MO message received by the CLIENT through SMSC Network Platform, sent by WhatsApp User using WhatsApp App;
“Free Form Message (FFM)” means any message sent by the CLIENT to WhatsApp User using WhatsApp App over SMSC Network Platform. during Customer Support Window;
“Highly Structured Message (HSM)” means a message template the CLIENT shall use when initiating conversation with End User. Every HSM shall be approved by WhatsApp before it can be used;
“Monthly Active User (MAU)” means each WhatsApp User using WhatsApp App which has received HSM or FFM sent by the CLIENT using SMSC Network Services in one calendar month;
“Monthly Hosted sender fee” means monthly fee for sender provided via WhatsApp OnPremises API, whose instalation is hosted, managed and upgraded by SMSC Network.
“Monthly Cloud sender fee” means monthly fee for sender hosted by Meta in Cloud API.
“Network Operator” means WhatsApp as defined below;
“WhatsApp” shall mean WhatsApp Inc., a limited liability company incorporated in the United States of America and whose principal place of business is at 1601 Willow Road, Menlo Park, CA 94025, United States;
“WhatsApp App” shall mean a mobile first, platform developed by WhatsApp that consists of a VoIP system, messaging service, groups and other means of interaction which can be installed on mobile devices;
“WhatsApp Platform” shall mean the server, hardware, software and other equipment that WhatsApp uses in connection with performance or the Services;
“WhatsApp MO Message” means each message sent by the WhatsApp user using WhatsApp App through SMSC Network Platform to the CLIENT;
“WhatsApp Traffic” shall mean the CLIENT Services provided to CLIENT’s WhatsApp Users via the WhatsApp Platform and WhatsApp App;
“WhatsApp User” shall mean an End-User who has downloaded the WhatsApp App to his/her device and has expressed its consent to receive WhatsApp Traffic from Client. Each WhatsApp user is defined by the MSISDN used to register in WhatsApp App.
WhatsApp Terms of Use:
CLIENT also accepts and acknowledges the below terms as issued and amended from time to time by WhatsApp and to be also applied to CLIENT’s usage of the WhatsApp Service under this Agreement.
WhatsApp Business Solution Policy (found at https://www.whatsapp.com/legal/business-solution-policy/)
WhatsApp Business Solution Terms (found at https://www.whatsapp.com/legal/business-solution-terms/)
WhatsApp Pricing Terms:
The pricing terms for WhatsApp services shall be as provided in Business proposal in corresponding Schedule of the Master Services Agreement.
Any form of reselling of the WhatsApp Service shall be allowed exclusively if prior written consent from SMSC Network is obtained.
Viber
1. Service description
SMSC Network Services (as defined in the Agreement) features a solution that shall enable CLIENT to deliver mobile terminated Service Messages to the Viber Platform through the SMSC Network Platform.
SMSC Network Services include:
Connectivity between CLIENT’s information system and the SMSC Network Platform;
Configuration of the SMSC Network Platform to receive Viber traffic generated by CLIENT and the handling and routing of such Viber traffic to the Viber Platform;
Billing of such Viber traffic processed by SMSC Network; and
Technical support
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route Viber traffic generated by CLIENT to the Viber Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage all contractual relationships with Viber to ensure the operability of the SMSC Network Services.
Without prejudice to the obligations of the CLIENT , CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route Viber traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of Viber Users receiving each Service message processed by SMSC Network;
Ensure under no circumstances to send Unsolicited Service Messages (SPAM) to the messaging Platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfil all its payment obligations
2. Chargeable event and other Viber Particulars
“Chargeable Event” means Viber Messages sent by CLIENT to SMSC Network which is subject to successful delivery by SMSC Network to End -User.
“Session Chargeable Event” means each session initiated by the End-User within CSW. Viber defines a conversation as a fixed 24-hour session during which CLIENT can send up to 60 Session type messages. Only session-based message types will be billed per conversation rate once a session is in progress. All other message types can still be used within a session but will be billed at a regular rate.
“Customer Support Window (CSW)” means period of 24 hours starting from the last Viber MO message received by the CLIENT through SMSC Network Platform, sent by Viber User using Viber App;
“Minimal Monthly Commitment fee (MMC)” means a fee applied to the CLIENT in a month, per each active sender (Service ID), for which the CLIENT will pay a prescribed monthly fee. In case the CLIENT sends more messages than included in the minimum monthly consumption, CLIENT will only be charged for the delivered messages.
“Viber” shall mean Viber Media S.a.r.l., a limited liability company (societe a responsabilite limitee) incorporated in the Grand Duchy of Luxembourg under number B184956 and whose principal place of business is at 2, rue du Fosse, L-1536 Luxembourg, Grand Duchy of Luxembourg;
“Viber App” shall mean a mobile first, platform developed by Viber that consists of a VoIP system, messaging service, groups and other means of interaction which can be installed on a mobile, tablet or desktop devices;
“Viber Platform” shall mean the server, hardware, software and other equipment that Viber uses in connection with performance or the Services;
“Viber Traffic” shall mean the CLIENT Services provided to CLIENT’s Viber Users via the Viber Platform and Viber App;
“Viber User” shall mean an End-User who has downloaded the Viber App to his device and has expressed its consent to receive Viber Traffic from Client.
“Network Operator” shall mean Viber as defined above.
CLIENT agrees and acknowledges specific traffic limitations may be imposed from time to time by Viber and, in turn, SMSC Network must apply the same to CLIENT in respect of the Viber Traffic. SMSC Network shall notify CLIENT about the same as soon as reasonably possible which notice shall be accompanied by a formal Viber document confirming the limitations.
At SMSC Network’s request, CLIENT shall submit to SMSC Network appropriate confirmation and evidence that any and all documentation such as agreements or other compliance materials requested by SMSC Network has been duly signed and executed by the CLIENT, particularly before access to the Service was given to Third Parties – such as, but not limited to Viber’s warranty letter, Data Processing Agreement, EULA or otherwise.
Messenger
1. Service description
SMSC Network Services features a solution that shall enable CLIENT to deliver mobile terminated Standard and Subscription Messages to the Messanger Platform through the SMSC Network Platform as well as processing messages received from Messenger Platform. Usable solely as an integral part of SMSC Network’s SaaS product portfolio, as opposed to being offered as a standalone product which is not an option.
SMSC Network Services include:
a. Connectivity between CLIENT’s information system and the SMSC Network Platform
b. Configuration of the SMSC Network Platform to receive Messenger traffic generated by CLIENT and the handling and routing of such traffic to the Messenger Platform
c. Billing of such Messenger traffic processed by SMSC Network; and
e. 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 SMSC Network Platform is tested and operational;
b. Route Facebook traffic generated by CLIENT to the Messenger Platform;
c. Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
d. Manage connectivity with Messenger to ensure 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 and contractual forms provided by SMSC Network
b. Ensure that its own information systems are properly configured to route Messenger traffic to the SMSC Network Platform;
c. Create and maintain at its own expense a database of Messenger Users receiving each Service and Subscription message processed by SMSC Network;
d. Ensure under no circumstances to send Unsolicited Service Messages (SPAM) to the messaging Platform;
e. Announce a larger volume of traffic within 5 business days in advance.
f. Fulfill all its payment obligations
2. Chargeable event and other Facebook Particulars
“Active User” means any End User which has been subject to Successful Receipt of at least one notification from CLIENT via the Services under this Agreement in a reference month;
“Chargeable Event” means Active User;
“Network Operator” means Facebook as defined below;
“Facebook” shall mean Facebook Inc, a company incorporated in the United States and whose registered office is situated at 1 Hacker Way, Menlo Park, California 94025;
“Successful Receipt” means notifications sent from CLIENT to SMSC Network and validated before submitting to the Facebook Platform that have been confirmed as delivered to the end-user’s handset;
“Messenger Platform” means the platform and associated systems, network connection and interfacing capabilities used and operated by Facebook;
Telegram
1. Service description
SMSC Network Services features a solution that shall enable CLIENT to deliver mobile terminated Standard and Subscription Messages to the Telegram Platform through the SMSC Network Platform as well as processing messages received from Telegram Platfrom. Usable solely as an integral part of SMSC Network’s SaaS product portfolio, as opposed to being offered as a standalone product which is not an option.
SMSC Network Services include:
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route Telegram traffic generated by CLIENT to the Telegram Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage connectivity with Telegram to ensure operability of the SMSC Network Services.
Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route Telegram traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of Telegram Users receiving each Service and Subscription message processed by SMSC Network;
Ensure under no circumstances to send Unsolicited Service Messages (SPAM) to the messaging Platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfill all its payment obligations
2. Chargeable event and other Telegram Particulars
“Active User” means any End User which has been subject to Successful Receipt of at least one notification from CLIENT via the Services under this Agreement in a reference month;
“Chargeable Event” means Active User;
“Network Operator” means Telegram as defined below;
“Successful Receipt” means notifications sent from CLIENT to SMSC Network and validated before submitting to the Telegram Platform that have been confirmed as delivered to the end-user’s handset;
“Telegram” shall mean Telegram Messenger LLP, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ 5;
“Telegram Platform” means the platform and associated systems, network connection and interfacing capabilities used and operated by Telegram;
Google Business Messages
1. Service description
SMSC Network Services features a solution that shall enable CLIENT to deliver mobile terminated messages to the Google Business Messages Platform through the SMSC Network Platform as well as processing messages received from the Google Business Messages Platform.
SMSC Network Services include:
Connectivity between CLIENT’s information system and the SMSC Network Platform;
Configuration of the SMSC Network Platform to receive Google BM traffic generated by CLIENT and the handling and routing of such Google BM traffic to the Google Platform;
Billing of such Google BM traffic processed by SMSC Network; and
Provide technical support
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route Google BM traffic generated by CLIENT to the Google Business Messages Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage all contractual relationships with Google to ensure the operability of the SMSC Network Services.
Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route Google BM traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of Google BM Users receiving each message processed by SMSC Network;
Ensure under no circumstances to send unsolicited messages (SPAM) to the messaging platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfil all its payment obligations
2. Chargeable event and other Google BM Particulars
“Chargeable Event” means Active User;
“Network Operator” means Google Business Messages platform as defined below;
“Google” shall mean Google LLC, a limited liability company incorporated in the United States of America and whose principal place of business is at 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States;
“Google BM App” shall mean any mobile, desktop or web-based application developed by Google that enables the usage of Google Business Messages Services.
“Google Platform” shall mean the server, hardware, software and other equipment that Google uses in connection with performance or the Services;
“Google BM Traffic” shall mean the CLIENT Services provided to CLIENT’s Google BM Users via the Google Business Messages Platform and Google Appa;
“Google BM User” shall mean an End-User who is using any of the Google Apps and has expressed its consent to use the Google BM Service.
“Google Policies” shall mean the then in-effect terms and conditions and/or policies which apply to any user or entity using the Google Apps and available at google.com.
CLIENT agrees and acknowledges specific traffic limitations may be imposed from time to time by Google and, in turn, SMSC Network must apply the same to CLIENT in respect of the Google BM Traffic. SMSC Network shall notify CLIENT about the same as soon as reasonably possible which notice shall be accompanied by a formal document confirming the limitations.
Apple Business Chat
1. Service description
SMSC Network Services features a solution that shall enable CLIENT to deliver mobile terminated messages to the Apple Business Chat Platform through the SMSC Network Platform as well as processing messages received from the Apple Business Chat Platform.
SMSC Network Services include:
Connectivity between CLIENT’s information system and the SMSC Network Platform;
Configuration of the SMSC Network Platform to receive Apple Business Chat traffic generated by CLIENT and the handling and routing of such Apple Business Chat traffic to the Apple Business Chat Platform;
Billing of such Apple Business Chat traffic processed by SMSC Network; and
Provide technical support
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route Apple Business Chat traffic generated by CLIENT to the Apple Business Chat Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage all contractual relationships with Apple to ensure the operability of the SMSC Network Services; and
Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route Apple Business Chat traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of Apple Business Chat Users receiving each message processed by SMSC Network;
Ensure under no circumstances to send unsolicited messages (SPAM) to the messaging platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfil all its payment obligations
2. Chargeable event and other Apple Business Chat Particulars
“Chargeable Event” means Active User;
“Network Operator” means Apple Business Chat platform as defined below;
“Apple” shall mean Apple Inc., a limited liability company incorporated in the United States of America and whose principal place of business is at One Apple Park Way, Cupertino, CA 95014, United States;
“Apple App” shall mean any mobile, desktop, tablet or web-based application developed by Apple that enables the usage of Apple Business Chat Services.
“Apple Business Chat Platform” shall mean the server, hardware, software and other equipment that Apple uses in connection with performance or the Services;
“Apple Business Chat Traffic” shall mean the CLIENT Services provided to CLIENT’s Apple Business Chat Users via the Apple Business Chat Platform and Apple Apps;
“Apple Business Chat User” shall mean an End-User who is using any of the Apple Apps and has expressed its consent to use the Apple Business Chat Service.
“Apple Policies” shall mean the then in-effect terms and conditions and/or policies which apply to any user or entity using the Apple Apps and available at apple.com.
CLIENT agrees and acknowledges specific traffic limitations may be imposed from time to time by Apple and, in turn, SMSC Network must apply the same to CLIENT in respect of the Apple Business Chat Traffic. SMSC Network shall notify CLIENT about the same as soon as reasonably possible which notice shall be accompanied by a formal document confirming the limitations.
Kakao
1. Service description
SMSC Network Services (as defined in the Agreement) features a solution that shall enable CLIENT to deliver mobile terminated Service Messages to the Kakao Platform through the SMSC Network Platform.
SMSC Network Services include:
Connectivity between CLIENT’s information system and the SMSC Network Platform;
Configuration of the SMSC Network Platform to receive Kakao traffic generated by CLIENT and the handling and routing of such KakaoTalk traffic to the KakaoTalk Platform;
Billing of such KakaoTalk traffic processed by SMSC Network; and
Technical support
In the provision of the SMSC Network Services, and in addition to the provisions set forth under the Agreement, SMSC Network shall:
Ensure that connectivity between CLIENT’s information system and the SMSC Network Platform is tested and operational;
Route Kakao traffic generated by CLIENT to the Kakao Platform;
Invoice CLIENT for all SMSC Network Charges relative to the provision of the SMSC Network;
Manage all contractual relationships with Kakao to ensure the operability of the SMSC Network Services;
Without prejudice to the obligations of the CLIENT, CLIENT further undertakes to:
Provide all the configuration information through the proper completion of all technical and contractual forms provided by SMSC Network;
Ensure that its own information systems are properly configured to route Kakao traffic to the SMSC Network Platform;
Create and maintain at its own expense a database of Kakao Users receiving each message processed by SMSC Network;
Ensure under no circumstances to send unsolicited messages (SPAM) to the messaging platform;
Announce a larger volume of traffic within 5 business days in advance.
Fulfil all its payment obligations
2. Chargeable event and other Kakao Particulars
Kakao solutions are offered as three separate messaging services: Notification Talk (Alim Tog) and Friends Talk (Chingu Tog) for transactional and promotional messages which are charged per delivery, while Consultation Talk (Sangdam Tog) for chat consultations is charged per session.
“Chargeable Event” for Notification and Friends Talkmeans Service Messages sent by CLIENT to SMSC Network which is subject to Successful Delivered by SMSC Network to Kakao User;
“Chargeable Event” for Consultation Talk means each Kakao Session initiated by the End –User within the time range.
“Service Message” means the message sent through the Kakao App to a Kakao User which has opted in with CLIENT to receive such message.
“Kakao” shall mean Kakao Corp., a company registered in Republic of Korea and whose principal place of business is at 242 Cheomdan-ro, Jeju-Si, Jeju-do, South Korea;
“Kakao App” shall mean a mobile first, platform developed by Kakao that consists of a VoIP system, messaging service, groups and other means of interaction which can be installed on a mobile, tablet or desktop devices;
“Kakao Platform” shall mean the server, hardware, software and other equipment that Kakao uses in connection with performance or the Services;
“Kakao Traffic” shall mean the CLIENT Services provided to CLIENT’s Kakao Users via the Kakao Platform and Kakao App;
“Kakao User” shall mean an End-User who has downloaded the Kakao App to his device and has expressed its consent to receive Kakao Traffic from Client.
“Network Operator” shall mean Kakao as defined above.
CLIENT agrees and acknowledges specific traffic limitations may be imposed from time to time by Kakao and, in turn, SMSC Network must apply the same to CLIENT in respect of the Kakao Traffic. SMSC Network shall notify CLIENT about the same as soon as reasonably possible which notice shall be accompanied by a formal Kakao document confirming the limitations.