Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Query on SMS campaign delivery receipt



User would like to receive an acknowledgement when SMS gets delivered to target audience.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

Not Applicable


The following explanation is provided in response to the user query on how to receive an acknowledgment on SMS:

  • "Request delivery receipt" option is available when you click on the deliver channel used in the SMS campaign created in the campaign builder.
  • By default, this option is unchecked i.e. notification request is off.
  • This option needs to checked in order to receive delivery status of SMS being sent to customers.
  • After this SMS campaign has been scheduled, a Task Group can be scheduled as often as is required to process the status of the SMS inbox.
  • SMSC stores the delivery receipts in the designated inbox on successfully delivery of the message to handset (Only if the "Request delivery receipt" option is checked).
  • These delivery receipts / reports are read by CMD by running the SMS inbox either in batch or task group.
  • During the inbound process, CMD will read the delivery receipts and updates the communication tables. CMD also logs all the delivery receipts details in the SPI_PROC*.log file corresponding to the inbound process.
  • Note that the SMSC / MMSC administrator may turn the delivery receipts indicator off if the center traffic is very busy due to which one may not receive SMS delivery receipts.
The flow of a message and its delivery status in CMD and SMSC is as described below:
  1. When outbound SMS campaign is run with request for delivery receipt, CMD will send SMS to SMSC and the following CMD tables will be populated as below:
This table will be populate with all the details and DELIVERY_STATUS_ID will be set to '4' which indicates the messages are 'Enroute'.
COMM_STATUS_ID will be set to '0' which indicates that the messages are delivered, irrespective of whether the messages are physically delivered or not.
A record will be inserted in this table with COMM_STATUS_ID as '0' and COMM_QTY, TREAT_QTY equal to number of customers targeted in the campaign.
- Then the SMS will be sent to Mobile hand sets by SMSC. Depending upon the delivery, the delivery status of the messages will be received by the SMSC. If the messages sent by SMSC are delivered immediately, the message delivered status will be returned else if the messages sent fail immediately, then failed delivery status will be returned to the SMSC.
  1. At the same time if the CMD inbound process for the corresponding SMSC inbox is running, the following updates will be made in the CMD tables:
  • DELIVERY_RECEIPT.DELIVERY_STATUS_ID will be updated with corresponding values as below:
1 Accepted
2 Deleted
3 Delivered
4 Enroute
5 Expired
6 Rejected
7 Undeliverable
8 Unknown
9 Retrieved
10 Expired
11 Rejected
12 Unrecognised
13 Deferred
COMM_STATUS_ID will be updated to '2', if the message is undelivered. Else if the message is delivered the COMM_STATUS_ID will not be changed which was initially set as '0' ('0' means delivered).
COMM_QTY will be reduced by '1' and a new record will be inserted with COMM_STATUS_ID set to '2', when a undelivered receipt is received.
- Hence the CAMP_COMM_OUT_DET.COMM_STATUS_ID will be set to '0' and DELIVERY_RECEIPT.DELIVERY_STATUS_ID will be set to '4' until the delivery receipt is not received by the SMSC.

Published September 26, 2017 - Updated December 2, 2021

Was this useful?

50% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us