If your Acoustic Campaign organization sends more than 250,000 SMS messages per month and you want to know the send results for each message, you can request a daily report that is based on the previous day's sends. This process may take up to two weeks and requires a one-time configuration before you can access the report on a secure FTP server. To request the daily report, open a support case and provide the information below:
- Acoustic pod
- Organization name or names
- Sender IDs or codes that your organization uses
- Include in your request if you want MTs (mobile terminated or outbound) only or also MOs (mobile originated or inbound) messages. MOs only applies if your organization uses 2-way messaging.
Alternatively, you can get the report from the SMS campaign manager, although sometimes the report does not generate successfully due to a large number of records.
One-time setup
Acoustic sends a notification to your organization's contact when your organization is consistently sending more than 250,000 SMS messages per month. Upon approval, we work with the SMS business partner to configure a dedicated, secure FTP server so you can receive and download a daily SMS message send report.
Availability
The report includes all SMS messages sent from the previous day between 12 AM - 11:59 AM EST. It also includes all delivery receipts between this time frame. The initial report will be delivered between the hours of 4 AM and 10 AM ET (depending on availability) and all subsequent reports will be the same time going forward. If any delivery receipts were not delivered in this time frame, they are not available in the FTP report. You can view this data in the SMS Campaign Manager.
Access the report
To access the report, we provide you with the SFTP server credentials: host site, user name, password, and port. When you connect successfully to the FTP site, you can see the daily report in the local site folder. Right-click the file name and view/edit, download a CSV file, or delete the file.
Make sure that you download the file to your local workstation and then delete it from the SFTP server. This server is not a long-term repository and the system can auto-delete files without advanced notice.
To save server space, the reports are automatically compressed to a ZIP format after 30 days.
Note: In some cases, the files can be compressed earlier or potentially removed if necessary.
View the report
The FTP-based SMS report is a CSV file with a fixed number of columns. When you open the file, order the data by the ID to identify which messages parts belong to a message text and ensure that the messages are correctly grouped.
Note: If you send messages to Greece, only a single Delivery Receipt is provided for multi-part messages. This limitation is for Greek mobile carriers.
- ID: Identifies the parts that belong to a message.
- NUM_PARTS: Determines how many segments are associated with a message text.
- SUB_ID: Identifies the parts of the message. There are three rows for a two-part message.
- 0: The entire message that was sent by the client without any breaks.
- 1: Represents the first part of the message before it was broken into the second part of the message.
- 2: Represents the second part of the message that continues from where the first message was split.
- RECIPIENT or MOBILE_NUMBER: Mobile number of the recipient to whom the outgoing SMS message was sent.
- DATETIME: Date and time when the outgoing SMS message was sent.
- CODE or SHORT_CODE: The long code, short code, or sender ID that is used to send the outgoing SMS messages.
- REAL_CARRIER: The mobile carrier ID.
- ISMT: If a two-way message, this identifies it as an outgoing SMS message or an incoming SMS message.
- MAX_STATUS_CODE: Delivery results from the SMS Gateway. This status code is different from the status code in the SMS campaign manager (called Status). See the Status code definitions table for details.
- MESSAGE_BODY: Message content.
- MESSAGE_TYPE: Use 'SMS'.
- PROGRAM: Text to Join program ID.
- PROGRAM NAME: SMS Text to Join program name that was used for the send.
- ORG_ID: Organization ID.
- ORG_NAME: Organization Name.
Status code definitions
| Status code | Status name | Billable | Status description |
| 5 | Initial Processing | No | The message was received by the prerouter. |
| 6 | Initial Processing | Yes | The message was received by MT Pipeline. |
| 7 | Router Communication Error | No | An internal error. Upon receiving this error, the content provider should wait 5 minutes for the next status notification. If no status notification appears, the content provider should start the retry algorithm. |
| 9 | Successfully Sent to Router | No | The prerouter successfully sent the message to the router. |
| 10 | Processing | No | The router successfully received the message from the prerouter. |
| 13 | Pending Opt-in | No | Awaiting opt-in from user. |
| 15 | No Send | No | Not sending for this recipient (due to inclusion in a no send list or other similar client-specified rule). |
| 18 | Unsubscribe Without Body | No | Final status for unsubscribe messages that do not have a body to send to the handset. |
| 20 | Carrier Processing | No | Carrier is assessing the MT request. |
| 30 | Retry | No | Message queued for entry (only applicable if status receipts are received also). |
| 40 | Carrier Received | Yes | Carrier accepted the message for delivery. In some cases, this status is the last available status from a carrier. |
| 105 | Short Code is Blocked | No | Carrier is blocking traffic on the specified short code. |
| 110 | Carrier Fail | Yes | Carrier returned a failure to deliver message. |
| 120 | Route Fail | No | Error sending to an HTTP endpoint (usually MO or MM7). |
| 121 | Enqueue Fail | No | Internal error – JMS enqueing error. |
| 124 | Retry Router Request Fail | No | The message expired before communication with the router was restored. |
| 126 | Product Not Migrated on QPass | No | This product is marked as migrated for Kaleyra (formerly mGage), but not QPass. |
| 127 | Premium Blocked | Yes | Carrier setting where handset cannot receive premium messages. |
| 128 | Standard Blocked | Yes | Carrier setting where handset cannot receive standard messages. |
| 129 | Carrier Cannot be Resolved | Yes | Carrier is unknown or the MDN is a non-SMS landline. |
| 130 | Split | No | The message was split. |
| 131 | Profanity Blocked | Yes | CleanAIR – Inappropriate word(s) detected and blocked. |
| 132 | Msg Paused for URL Approval | Yes | CleanAIR – URL detected and blocked. |
| 133 | Paused: Profanity and URL found | No | CleanAIR – Inappropriate word(s) and URL detected and blocked. |
| 200 | Carrier Success | Yes | Carrier indicates successful delivery of message to the subscriber's device. |
| 202 | Singlepoint Billing Received | Yes | Singlepoint billing DR. |
| 210 | Carrier Manual Ack | Yes | Response from carrier: manual ack. |
| 220 | No answer | Yes | Response from carrier: no answer. |
| 225 | Line is Busy | Yes | Response from carrier: line busy. |
| 230 | Carrier SIT | Yes | Response from carrier: SIT |
| 240 | Carrier Reorder | Yes | Response from carrier: reorder. |
| 250 | Carrier Expired | Yes | The default period for the SMS (typically 72 hours) passed without successful message delivery. This status typically happens if the subscriber remains out of coverage or keeps their phone turned off for an extended period. |
| 260 | Carrier Deleted | Yes | A manual status that indicates that the message was deleted by the SMSC without delivery. |
| 270 | Carrier Undeliverable | Yes | The message couldn't be delivered. Sometimes carriers' SMSCs accept messages for recipients they don't own because of data roaming agreements, but they can't deliver the message. For example, one reason may be that the subscriber's prepaid credits ran out or the subscriber is not valid. This typically occurs for the SMSCs outside of the United States where data roaming over SMSCs are typical. |
| 275 | Carrier Undeliverable Permanent | No | The message could not be delivered. This error is specific to non-US and non-Canadian destinations, where undeliverable status was received from the carrier or delivery partner. The nature of the error state is a permanent failure, which means this mobile number is not a valid delivery destination and no further delivery attempts should be made. |
| 277 | Carrier Undeliverable Temporary | No | The message could not be delivered. This error is specific to non-US and non-Canadian destinations, where undeliverable status was received from the carrier or delivery partner. The nature of the error state is a temporary failure, which means future delivery attempts can be made. |
| 280 | Carrier Unknown | Yes | The stopgap error code that is generated by the SMSC when no other possible condition exists. |
| 290 | Carrier Rejected | Yes | This status typically happens for carriers outside of the US when a data roaming carrier rejects the particular message. This also includes messages sent to users registered on India's Do Not Disturb (DND) list. |
| 99999 | Unknown | Yes | A delivery receipt/status notification was received outside the carrier-defined or known status receipt codes. |