Before You Begin

Getting Ready for Onboarding

Welcome to mobile messaging and all of the possibilities it presents to help you communicate with your audience. We're eager to work with you to help you reach your goals.

The first step is getting signed up and onboarded. By onboarding we mean setting up your account to use the messaging products and services you need. If you haven't yet signed up with us, reach out via our Contact Form to get started.

Onboarding checklist

The following table provides an onboarding checklist to help you gather the information we'll need to create and configure your account. Also provided is information about how to get help when you need it from our Technical Support team.

Item	Details
Who in your organization should we contact for these functions: Billing –— the person(s) responsible for receiving and paying invoices Reporting –— the person(s) who need access to the reports we provide Support –— someone from your technical support team Technical –— one or more people from your IT or development team Provide this info here.	For the Reporting contact(s), you may have just one person or multiple. One user will have permission to manage access across all of the reports available to you. Other users will be given access to the reports and data visualizations pertinent to their function. For more information about our reports, see the Reporting section of our docs site.
Which products do you intend to use? SMS Branded Messaging MMS RCS Mobile Engagement Platform	SMS overview and API docs Branded Messaging MMS overview and API docs RCS overview and API docs Mobile Engagement Platform
If you're using SMS, which integration method will you use? HTTP (you can use either JSON or XML) SMPP –— you'll need to give us IP addresses for all environments that will connect to OpenMarket. Note that for security, you'll need to set up VPNs if your environments do not support TLS 1.2.	HTTP Overview SMPP Overview
If you're using MMS, which integration method will you use? HTTP –— recommended for most customers MM7 –— best for experienced customers	HTTP Overview MM7 Overview
Which countries will you send messages to?	SMS Coverage map RCS Coverage Map
Will your messaging be: One-way — involves you sending a message to your audience but not expecting any replies (e.g., a basic appointment reminder) Two-way — involves sending messages to your audience and expecting replies (e.g., an appointment reminder with confirmation request)	Mobile network operators in the US and Canada consider all messages to be two-way. If you're using our Global SMS HTTP API, we need at least one endpoint from you so you can receive messages texted in by your end users. One-way and two-way messaging Receiving messages from end users
What source numbers (originators) will you use to send messages? Depending on where your end users are located and other requirements, you can use short codes, alphanumeric codes, and 10-digit long codes. We can advise you on this if you need further details.	Overview of source numbers Visit our Industry Guidelines page for information about regulations and policies specific to mobile operators in the US and Canada
How do you want to receive SMS delivery receipts? Many mobile network operators send us delivery receipts, which contain information about the status of your messages. You'll want to receive these, so we need to know how to send them to you. Here are the options: Provide us with one endpoint that we'll configure on your account. All delivery receipts will go to this one endpoint. Include an endpoint in the message request operation. This is the way to go if you have multiple messaging applications and you want receipts delivered to different endpoints. A hybrid of #1 and #2, where you have a default endpoint for your account but override that by including a different endpoint in the message request. Request that we configure a separate 'account' for each application or environment, and an endpoint for each one. This means delivery receipts can be sent to different endpoints without you needing to include the endpoint in the message request.	Find information on what information delivery receipts contain here: HTTP - receive a delivery receipt SMPP - receive a delivery receipt

Item

Details

Who in your organization should we contact for these functions:

Billing –— the person(s) responsible for receiving and paying invoices
Reporting –— the person(s) who need access to the reports we provide
Support –— someone from your technical support team
Technical –— one or more people from your IT or development team

Provide this info here.

For the Reporting contact(s), you may have just one person or multiple. One user will have permission to manage access across all of the reports available to you. Other users will be given access to the reports and data visualizations pertinent to their function.

For more information about our reports, see the Reporting section of our docs site.

Which products do you intend to use?

SMS
Branded Messaging
MMS
RCS
Mobile Engagement Platform

SMS overview and API docs

Branded Messaging

MMS overview and API docs

RCS overview and API docs

Mobile Engagement Platform

If you're using SMS, which integration method will you use?

HTTP (you can use either JSON or XML)
SMPP –— you'll need to give us IP addresses for all environments that will connect to OpenMarket. Note that for security, you'll need to set up VPNs if your environments do not support TLS 1.2.

HTTP Overview

SMPP Overview

If you're using MMS, which integration method will you use?

HTTP –— recommended for most customers
MM7 –— best for experienced customers

HTTP Overview

MM7 Overview

Which countries will you send messages to?

SMS Coverage map

RCS Coverage Map

Will your messaging be:

One-way — involves you sending a message to your audience but not expecting any replies (e.g., a basic appointment reminder)
Two-way — involves sending messages to your audience and expecting replies (e.g., an appointment reminder with confirmation request)

Mobile network operators in the US and Canada consider all messages to be two-way. If you're using our Global SMS HTTP API, we need at least one endpoint from you so you can receive messages texted in by your end users.

One-way and two-way messaging

Receiving messages from end users

What source numbers (originators) will you use to send messages?

Depending on where your end users are located and other requirements, you can use short codes, alphanumeric codes, and 10-digit long codes. We can advise you on this if you need further details.

Overview of source numbers

Visit our Industry Guidelines page for information about regulations and policies specific to mobile operators in the US and Canada

How do you want to receive SMS delivery receipts?

Many mobile network operators send us delivery receipts, which contain information about the status of your messages. You'll want to receive these, so we need to know how to send them to you. Here are the options:

Provide us with one endpoint that we'll configure on your account. All delivery receipts will go to this one endpoint.
Include an endpoint in the message request operation. This is the way to go if you have multiple messaging applications and you want receipts delivered to different endpoints.
A hybrid of #1 and #2, where you have a default endpoint for your account but override that by including a different endpoint in the message request.
Request that we configure a separate 'account' for each application or environment, and an endpoint for each one. This means delivery receipts can be sent to different endpoints without you needing to include the endpoint in the message request.

Find information on what information delivery receipts contain here:

HTTP - receive a delivery receipt
SMPP - receive a delivery receipt