Page tree
Skip to end of metadata
Go to start of metadata

Mobile Report shows transactions and content by mobile device for each message with a time and date stamp.

This report can be found in the via the Reporting side menu

What is in Mobile Report?

Mobile report details every mobile transaction through our platform for audit and analysis purposes. Allows you to filter messages on mobile number, message status, application and timeframe. In addition these reports can be automated ­useful for rejected messages. It can be found under Reporting → Mobile Report in the left hand navigation bar

Once generated Mobile Report has multiple columns, some are standard and some can be toggled off before running the report.

  • Message ID - an unique per message identifier. This identifier has a clickable link that will take you through to the Message Detail Report
  • Date and Time - when the message was sent
  • Application* - the Gateway ID that the message was sent through
  • Class* - if the message was an Mobile Originating (MO), Mobile Terminating (MT) or email2text etc
  • Source* - the short code or MSISDN that the message was send from.
  • Destination* - the short code or MSISDN that received the message.
  • Status* - Details on the whether your SMS has ultimately been received at the destination handset, or whether it never reached the handset and why. More details below.
  • Units* - Number of messages associated with the message content. Where messages exceed the maximum number of characters for one message there may be more than one messages involved.
  • Content* - The content of the message that was sent
    • To view content you must be set up with a special permission, the default is that it is not visible. If you have not been granted this permission and believe it is required please contact your support channel
  • Transport Source* - The Mobile Operator that the message was delivered through 

* Optional fields 

With permission to view content:

Without permission to view content:


top of page

What do the Status Mean? 

Different Statuses

There are a number of potential statuses that messages can display in our reporting. The perfect message will show 'Queued' then 'Submitted' then 'Sent' then 'Received'

In Mobile Report, these are displayed (timestamped) in order from the bottom up. Each status is timestamped and shows exactly what happened to the message.

Status Matrix

There are a few 'tips' beneath each status to explain some differences in other countries, or carrier specific quirks.

Queued, Sent and Failed


MT Message Flow Description

MO Message Flow Description


Messages have not left the platform gateway - the application that is sending the message is queuing it in our gateway.

The platform has received the message from the carrier, and routing the message to the customer's application has been completed. 


Messages have been sent from the platform gateway, but not yet acknowledged by the carrier SMSC.

The platform has completed the callback request to your configured MO callback URL.


These are messages that failed to be ‘sent’ to the carrier. This can consist of numbers that have opted out of previous campaigns, messages that ‘failed’ because of invalid formatting, or if there was a connectivity issue, or a system issue preventing the messages leaving our gateway.

If a message Fails enough times it will move to a Frozen status and will not be sent to the carrier.

At the moment we will retry 50 times before freezing the message.


Submitted and Received (and Rejected)

These are statuses generated by the carrier.  The messages have left our gateway. 




Submitted = (in Campaign Manager it's listed as 'Submitted for Delivery')  The total number of messages that have been sent to the carrier. It simply means the carrier has acknowledged they have got the messages from our gateway.

Note: This is not a handset delivery status. This is a system status DLR.  It will only tell you the carrier has received the message.  We do not know what they have done with the message until we receive an updated handset DLR.


Received = is provided by the carrier delivering the message. It means the message was sent to the handset and the carrier has supplied us with a 'Received' status.  

TIP:  In the majority of cases, a RECEIVED status means the handset has got the message, but sometimes it can be handed to us by the carrier if it has been queued or can't be delivered immediately (rare). 


Rejected = is provided by the carrier attempting to deliver the message. It means the message could not be sent to the handset because the number is invalid on the carriers network.

TIP:  This can be caused by an expired number, closed account, a ported number not listed in a number portability look up, a number not on that carriers network, or if the number is international, if the carrier does not support masked messages.  

Rejected messages are counted in volume reports, and they are billed.  This is because we have passed the message to the carrier for delivery, so it is a 'sent' message.  


Pending, Expired and Deficient




Pending is a transitional status. Once the message progresses, a new status is usually provided.   Pending status is provided by the carrier attempting to deliver the message. It means the carrier has acknowledged they have got the messages from our gateway, but have yet to deliver the message to the handset. (ie ‘Received’).

TIP: Messages can remain in the pending status if the carrier is not able to immediately deliver the message because the phone is unavailable (eg: out of range, switched off, load issues on the carrier network etc).

Each carrier has a set of rules for retrying messages.

If the message is still undeliverable after the number of days determined by the carrier, they may send a final status of 'Failed'...   Sometimes they do not.


Expired indicates that the carrier was unable to deliver the MT message within the Validity Period (VP), defined for the message. Not all carriers supply an expired notification.  

The Validity Period can be set to a period of seconds, minutes, hours, days or weeks in varying increments up to one year, and is set for MT messages by the carrier.  Validity period is currently set for each carrier as per below:

2 Degrees: 3 days - 2 Degrees SMS Delivery Retry process

Skinny/Spark: 5 days - Spark and Skinny SMS Retry Patterns

Vodafone: 1 day - Vodafone SMS Retry Patterns

There are a number of reasons why the carrier was unable to deliver the MT message within the validity period set, some of which are detailed below:

  • The handset is not on the network and so is unreachable.
  • The handset is in a low coverage area causing intermittent connectivity to the operator network resulting in messages to the handset to not be correctly delivered. This can also cause handset acknowledgement issues, whereby the notification can either, not be sent or is sent but arrives with delay, by which time the message is entered into, or remains in the retry cycle until the message expires
  • The SMS inbox is full


Deficient = credit limit of your account has been exhausted. This means your account has a cap on the number of SMS that can be sent, for example trial accounts.

top of page

Message Detail Report 

The Message Detail report can be accessed by clicking on the hyperlinked unique Message ID; this page provides more detailed information on the specific message that was selected. 

This page also has permission based content visibility.

top of page

How to Generate a One Off Report

To generate a one off report navigate to Reporting → Mobile Report in the left hand navigation bar

There are several defaults that will auto populate based on the account settings:

  • Company will be automatically selected based on your login. Resellers will get a choice of options based on the companies under their umbrella.
  • Timezone will be automatically based on your Omni account settings.

From here you can generate a report in several ways:

  • By Mobile Number
    • If there is a specific mobile number you would like to see more detail on enter the mobile number under Mobile
    • If there are other critera that are required such as timeframe add these as it will narrow the search results
    • Then press "Search"
  • By Message ID
    • If there is a Message ID you would specifically like to see more detail on enter the Message ID
    • Then press the "Load" button beside the field
  • General Searches
    • If you do not have a specific number or ID you would like to look for you can search by Timeframe, Application or Carrier (or a combination)
    • You can also search by status to see all the messages with a particular status e.g. failed or rejected messages
      • To find out more detail on each status see here

top of page

Creating a Automated Report 

There are two ways the report can be created:

  1. Navigate to Reporting → Mobile Report in the left hand side navigation bar
     a. Select "Automate This"

    b. You will be taken to a page where you can create a new Automated Mobile Report by selecting from the drop-downs. 

2. Navigate to Reporting → Automated Reports in the left hand side navigation bar, then select the Mobile Report tab

a. On this page you can see all automated reports that have already been set up and filter by customer (if you are a reseller).

b. Select "New Report"

c.  You will be taken to a page where you can create a new Automated Mobile Report by selecting from the drop-downs. (same as 1b)

Note: If the automated report is set up to go to an email address that is not a user in the platform the content of the messages will be automatically restricted

top of page

Editing an Automated Report

If the details of an automated report needs to be changed this can be done via Reporting → Automated Reports in the left hand side navigation bar, then select the Mobile Report tab

You can then navigate to the report you would like to amend and choose edit.

This will bring up a page that details the fields you are able to edit along with the events that have occured for this report i.e. when the report was created and each time it has been sent.

top of page

Deleting an Automated Report

If an automated report needs to be deleted this can be done via Reporting → Automated Reports in the left hand side navigation bar,  then select the Mobile Report tab

Once you press the delete button for the relevant report you will get the below confirmation and the report will be removed.

  • No labels