You can find your SMS reports in the 'Reports'  tab under Admin.





SMS reporting format

FieldValuesComments
IdUnique alphanumeric identifier of the SMS
Directionincoming / outbound-api
Typetransactional / promotional'Transactional' if the message matches a transactional template in your account
FromSMS Sender IDLM-XXXXXX for outbound sms and the sending number for inbound sms
ToNumber to which SMS was sent
BodyBody of the message
Statussent / failed / failed-dnd / submittedsent - All is well
failed - Message was not sent
failed-dnd - This happens when a promotional SMS is sent to a number in NCPR (DND list)
submitted - This means that the SMS you have sent has been submitted from our system to SMS Gateway
TimeYYYY-MM-DD HH:MM:SS  
 PriceIn rupees1 sms unit = 160 characters. 
ToCircleThe telecom circle to which the 'To' number belongs tohttps://developer.exotel.com/api/#metadata-phone
DetailedStatusCode
The code of the Detailed SMS statusRefer to the table below for the possible values.
DetailedStatus
The name of the Detailed SMS statusRefer to the table below for the possible values.
DltEntityIdThe numeric identifier for DLT platform in India as configured on Exotel dashboard or passed in the API request.NOTE: This column would only be populated if your Exotel account is domestic (India specific)

If this is empty or incorrect, DLT platform will fail your SMSes. You can configure this via Exotel Dashboard Settings (link)
DltTemplateIdThe numeric identifier for DLT Template in India as configured on Exotel dashboard or passed in the API request. A single quote (') would be added at the end to allow this to be readable in Excel. 
NOTE: This column would only be populated if your Exotel account is domestic (India specific)

If this is empty or incorrect, DLT platform will fail your SMSes. Refer to this knowledge base to learn more on Template scrubbing compliance.



List of possible DetailedStatus and DetailedStatusCode-


DetailedStatusCode

Nature of Detailed Status Code

Status

DetailedStatus

What it means

21010

Intermediate, may change in future

queued

PENDING_TO_OPERATOR

The message is is being processed by Exotel.

21015

Intermediate, may change in future

sending

SENDING_TO_OPERATOR

The message has been processed by Exotel and is en-route to the operator.

21020

Intermediate, may change in future

submitted

PENDING_ON_OPERATOR

The message has been successfully Submitted to the operator and is pending delivery. In India, Promotional SMS may be in this state if submitted outside permitted time (9AM to 9PM).

20005

Final

sent

DELIVERED_TO_HANDSET

We know with confidence that the message has been delivered to recipient's handset.

20006

Final

sent

DELIVERED_TO_OPERATOR

The message has been delivered to operator. In some regions and routes, handset delivery status (DELIVERED_TO_HANDSET) is not available and hence this is the best we can ever report about the delivery status.

23005

Final

failed_dnd

FAILED_REJECTED_DND

The message has been rejected as the end user is a subscriber of DND (Do Not Disturb) services.

23010

Final

failed

FAILED_INVALID_DESTINATION_NUMBER

The destination number is incorrect, not SMS-enabled or is a PSTN landline.

23015

Final

failed

FAILED_SPAM_DETECTED

One of the most common reasons for SMS delivery failure is carrier level spam filters. Carriers have added systems and algorithms that detect spam content and then block these messages. Unfortunately, these filters are hidden, subject to carrier preferences, vary from carrier to carrier, and can be changed without notice.

23020

Final

failed

FAILED_REJECTED_BLACKLIST

You tried to send a message to a blacklisted phone number. That is, the user has already sent a STOP/DND opt-out message and no longer wishes to receive messages from you.

24990

Final

failed

FAILED_UNKNOWN_ERROR

Delivering your message failed for reasons that are unknown to us and to our carriers. If you notice too many of these cases, please reach out to us.

23030

Final

failed

FAILED_UNAVAILABLE_ROUTE

The carrier and fallback carriers were not able to deliver the SMS message because no route was available.

23035

Final

failed

FAILED_SUBSCRIBER_UNAVAILABLE

This message was not delivered because subscriber was temporarily unavailable. For example, the receiving handset was out of coverage or switched off. This is a temporary failure, but a message sent to the same subscriber at a later point in time may get delivered.

23040

Final

failed

FAILED_SUBSCRIBER_UNKNOWN

Subscriber is unknown to the operators or no longer active.

23050

Final

failed

FAILED_EXPIRED

The message was sent to the operator and may have been retried several times within the default network SMS expiration duration. The message request has now expired.

23060

Final

failed

FAILED_REJECTED

For a number of reasons, the message was rejected by Exotel or the operator.

24105

Final

failed

FAILED_HANDSET_ERROR

The message was not delivered to the subscriber due to handset failure

24110

Final

failed

FAILED_OPERATOR_ERROR

The message failed due to an issue at the operator end

23070

Final

failed

FAILED_INVALID_MESSAGE

The message was rejected by the operator as Invalid. While Exotel will automatically split messages longer than 160 GSM 7-bit characters, or 70 unicode 16-bit characters into multipart SMS, Messages exceeding the allowed character limit of 2000 characters may also end in this state. Any request error related to the message, say unindentified character, may also fall under this bucket.

In India, if DLT related parameters are not set like Entity ID, your SMS may fail with this error code.

23072

Final

failed

FAILED_INVALID_SENDER_ID

 

The message failed due to invalid or unregistered Sender ID. In case of India, if your Sender ID (header) is not registered with operator DLT platform, you may receive this error.

24010

Final

failed

FAILED_SYSTEM_ERROR

SMS failed while processing within Exotel system.

24120

Final

failed

FAILED_SUBSCRIBER_ERROR

All subscriber or recipeient issues that are unrelated to the handset (For ex - Receiver does not have enough mobile balance to receive the SMS) may fall under this bucket.

23080
FinalfailedSENDER_BLOCKED_BY_DLT
Applicable only for SMSes sent to Indian destination numbers via domestic lines. Sender ID (Header) is blocked or failed at DLT due to mismatch, non-registration etc.    
23081
FinalfailedENTITY_BLOCKED_BY_DLT
Applicable only for SMSes sent to Indian destination numbers via domestic lines. Entity (DLT Entity ID) is blocked or failed at DLT due to not being set, mismatch etc.    

23082
FinalfailedTEMPLATE_BLOCKED_BY_DLT
Applicable only for SMSes sent to Indian destination numbers via domestic lines. Template (Template ID) is blocked or failed at DLT due to not being set, mismatch, non-registeration etc.    

23083
FinalfailedFAILED_DLT_SCRUBBING_ERROR
Applicable only for SMSes sent to Indian destination numbers via domestic lines. SMS is blocked or failed at DLT even after registration due to explicit blocking of the Sender ID due to spam, issues with consent or any other technical issues with DLT platform.

23084-24000
FinalfailedRESERVED FOR FUTUREThese statuses will not be populated right now but are reserved for future for any other detailed status scenario related to SMS.