Technical Document || Whatsapp Integration (Gupshup)

What is expected to be done?

Trigger notification messages whenever FDR (failed delivery reason) events occur, clients would have the option of using an Eshopbox account integrated with Gupshup to trigger notifications or using their own account for triggering notifications.

How would it be implemented?

Open

ALL GCP PROJECT IDS AND REPOS:

DATA MODEL:

Tables and columns to be introduced to achieve the following are as follows:

1. Table: eshopbox_wms_production.poe_channel_notifications: columns to be added “isWhatsappEnabled” (values 0 or 1), “whatsappTemplateId” (eg. 567787) (can be different for the different account)

2. Table: eshopbox_wms_production.poe_channel_settings: columns to be added “whatsappSenderConnectionId”

3. Table “whatsapp_status_logs”

1. A new table name (whatsappTemplateVariables) to be added for saving predefined variables would be used in template creation by clients. Note: No other variable be used.

Logic:

Type of FDR:

APP & INTEGRATION

For the Eshopbox application, it will be by default present and if clients want their own Gupshup app then they will perform the following else this isn’t required

1. New Whatsapp will be integrated into the platform where the client would be installing the application in the very first place

2. As soon as the app is installed client would be prompted to enter the credentials, credentials would save in the integration database credentials and table reference integration db table name ie_appinstall_connection – App&Integration team

CUSTOMER PORTAL:

– GCP Service for the following steps (poe-setting), repo name Poe-setting-service, GCP Project poe-backend-prod

1. Project Integration Engine service name: default, call API - “/connection/start“ (apps and integration) from which we will fetch the connection ids of apps installed

2. We would save the same connection ids in poe_channel_settings.whatsappSenderConnectionId

3. Configuration of application by default eshop app would be installed and templateId would be saved for that default account column to be added in DB.

4. If the client chooses other apps than eshop then we update templateId and set it as the user will input the template id for their account also we will verify each template ID with the following Gupshup API:

   1. https://api.gupshup.io/sm/api/v1/template/list/O5kHYP3DQ4SPczX2jIMciKnN

      response from API { "status": "success", "templates": [ { "appId": "4844b1fa-37ff-4ec8-b477-3940dfc48fc1", "category": "UTILITY", "createdOn": 1684235643193, "data": "Hello {{1}}!\n\nYour {{2}} order ID {{3}} having {{4}} items couldn't be delivered as your number ({{5}}) was unreachable. Please provide an alternate contact number for better connectivity.\n\nItem(s) included in the order:\n\n- {{6}} \n\n- {{7}} \n\n- {{8}} \n\nPlease choose your desired action | [Add alternate number] | [Select new delivery date] | [Raise a concern]", "elementName": "customer_unreacheable", "externalId": "1011900396485097", "id": "2fc7189a-0e52-47e8-a426-0315883adca2", "internalCategory": 0, "internalType": 0, "languageCode": "en", "languagePolicy": "deterministic", "modifiedOn": 1684235643193, "namespace": "aca1de90_c55c_4eb4_ab7b_41b915bcfe07", "priority": 1, "quality": "UNKNOWN", "retry": 0, "stage": "NONE", "status": "APPROVED", "templateType": "TEXT", "wabaId": "108133288928594" }, { "appId": "4844b1fa-37ff-4ec8-b477-3940dfc48fc1", "category": "UTILITY", "createdOn": 1684235643166, "data": "Hello {{1}}!\n\nYour {{2}} order with ID {{3}}, consisting of {{4}} items, could not be delivered as the address provided by you is incomplete or incorrect. Please update your delivery address.\n\nItem(s) included in the order:\n\n- {{5}} {{6}}\n\nDelivery address:\n\n{{7}}\n\nPlease choose your desired action | [Update my address] | [Raise a concern]", "elementName": "fdr_address_issue", "externalId": "1329870350939574", "id": "71baa9a9-a4f2-4e97-a6dd-c83747575157", "internalCategory": 0, "internalType": 0, "languageCode": "en", "languagePolicy": "deterministic", "modifiedOn": 1684235643166, "namespace": "aca1de90_c55c_4eb4_ab7b_41b915bcfe07", "priority": 1, "quality": "UNKNOWN", "retry": 0, "stage": "NONE", "status": "APPROVED", "templateType": "TEXT", "wabaId": "108133288928594" }, { "appId": "4844b1fa-37ff-4ec8-b477-3940dfc48fc1", "category": "UTILITY", "createdOn": 1684235643176, "data": "Hello {{1}}!\n\nYour {{2}} order ID {{3}} having {{4}} items couldn't be delivered as your number ({{5}}) was unreachable. Please provide an alternate contact number for better connectivity.\n\nItem(s) included in the order:\n\n- {{6}} {{7}}\n\nPlease choose your desired action | [Add alternate number] | [Select new delivery date] | [Raise a concern]", "elementName": "customer_unreacheable_final", "externalId": "277537501285510", "id": "77f8e4da-16e8-4cbe-90e8-c3f0201a047f", "internalCategory": 0, "internalType": 0, "languageCode": "en", "languagePolicy": "deterministic", "modifiedOn": 1684845477592, "namespace": "aca1de90_c55c_4eb4_ab7b_41b915bcfe07", "priority": 1, "quality": "UNKNOWN", "retry": 0, "stage": "NONE", "status": "APPROVED", "templateType": "TEXT", "wabaId": "108133288928594" }, { "appId": "4844b1fa-37ff-4ec8-b477-3940dfc48fc1", "category": "MARKETING", "createdOn": 1683023020984, "data": "You will no longer receive messages", "elementName": "opt_out_message", "externalId": "938521787469597", "id": "8f361040-b8e9-4fd6-84d0-394c347580ba", "internalCategory": 0, "internalType": 0, "languageCode": "en", "languagePolicy": "deterministic", "modifiedOn": 1684235643201, "namespace": "aca1de90_c55c_4eb4_ab7b_41b915bcfe07", "priority": 1, "quality": "UNKNOWN", "retry": 0, "stage": "NONE", "status": "APPROVED", "templateType": "TEXT", "wabaId": "108133288928594" }, { "appId": "4844b1fa-37ff-4ec8-b477-3940dfc48fc1", "category": "UTILITY", "createdOn": 1684235643158, "data": "Hello {{1}}!\n\nYour {{2}} order ID {{3}} having {{4}} items couldn't be delivered \n as you refused to accept it.\n\nItem(s) included in the order:\n\n- {{5}}{{6}}\n\nPlease choose your desired action | [Reattempt delivery] | [Cancel my order] | [Raise a concern]", "elementName": "fdr_rejected_by_the_customer", "externalId": "619361626878781", "id": "992b7ece-3217-4134-a161-ebd6ffd91cd9", "internalCategory": 0, "internalType": 0, "languageCode": "en", "languagePolicy": "deterministic", "modifiedOn": 1684235643158, "namespace": "aca1de90_c55c_4eb4_ab7b_41b915bcfe07", "priority": 1, "quality": "UNKNOWN", "retry": 0, "stage": "NONE", "status": "APPROVED", "templateType": "TEXT", "wabaId": "108133288928594" } ] }

      – GCP Service for the following steps (default), repo name Poe-backend-service, GCP Project poe-backend-prod

5. For clients there would be a toggle option to choose and turn on or off the WhatsApp notifications setting if the client chooses to turn the notification off it would be saved in db in table “poe_channel_notification”.

6. By default the setting will be set as “0” because other services Eshopbox provide are free of cost and Whatsapp isn’t so it will be by default in the off state.

7. Clients would be prompted to choose the application if they have installed their own application they would choose their else by default Eshopbox application would be selected from the dropdown.

8. We need to create a new table in wms prod db where various variables will be saved for use in the template

9. To trigger the FDR message we first receive an event from GCP Project - ESB-platform-prod, service name - notification where we have published the event for shipment the same will be subscribed by our service and FDR events look like this:

   { "resource": "shipment", "eventType": "PUT", "eventSubType": "failed_delivery", "accountSlug": "vitaminplanet", "accountId": null, "actor": "SYSTEM", "version": "v1", "request_data": [], "response_data": { "customerOrderNumber": "4980116095129", "orderSiteID": "", "vendorOrderNumber": "#98079", "externalShipmentID": "4980116095129-90758", "externalWarehouseID": "Gurgaon_FC", "externalChannelID": "CH1299", "externalWmsChannelName": "SCITRON_SHOPIFY_VITAMINPLANET_AGGN_2295", "external_wms_channel_id": 2295, "channelLabel": "Scitron Shopify", "integrationType": "7", "vendorPartyID": null, "partner_as2_id": null, "defaultWarehouseCode": "Gurgaon_FC", "facilityLabel": "Gurgaon (AGGN)", "facilityType": "auperator", "orderDate": "2023-06-05 16:58:58", "portal_id": 27, "paymentType": "Cash on Delivery (COD)", "expectedShipDate": "2023-06-06 12:00:00", "dispatchAfterDate": null, "externalManifestNumber": null, "channelManifestNumber": null, "order_id": 48884718, "channel_id": 1299, "warehouse_id": 650, "channel_account_id": 0, "account_id": 379, "connectionId": 482, "locationId": "67070591129", "region": "Zonal", "isMetro": "0", "isSpecialplace": "0", "shippingConnectionId": 0, "picklistCode": null, "invoiceNumber": "INVVITHZ42616", "boxType": "UNKNOWN", "isPriorityShipment": "0", "isGift": "0", "invoice_url": "https:\/\/storage.googleapis.com\/invoicefiles-prod\/invoice\/4980116095129-90758-1685964612847.pdf", "invoiceDate": "2023-06-05 17:00:09", "label_url": "https:\/\/storage.googleapis.com\/eshopbox_wms_uploads\/myntraLabel\/20230605210903274917906.pdf", "labels": "", "shippingInfo": [], "boxAdditionalRecommendation": [], "dimension_length": "26", "dimension_width": "16", "dimension_height": "20", "weight": "1550", "trackingID": "1704612602165", "trackingDomain": "track.scitron.com", "packageID": "", "barcode": "", "taxAmount": 0, "shipChargeAmount": 0, "courierName": "Delhivery", "cp_id": 4, "created_at": "2023-06-05 16:59:09", "updated_at": "2023-06-06 19:49:23", "status": "failed_delivery", "remarks": "code verified cancellation", "warehousePincode": "122503", "thirdPartyShipping": false, "customerName": "Aman Verma", "customerContactNumber": "7891971009", "email": "Amitv12330@gmail.com", "channelSlug": "vitaminplanet90", "status_updated_at": "2023-06-08 16:06:16", "status_log": { "created": "2023-06-05 16:59:09", "accepted": "2023-06-05 17:00:08", "picked": "2023-06-05 17:30:14", "packed": "2023-06-05 21:09:05", "out_for_pickup": "2023-06-06 16:46:12", "dispatched": "2023-06-06 19:49:23", "intransit": "2023-06-08 10:13:42", "out_for_delivery": "2023-06-08 12:09:06", "failed_delivery": "2023-06-08 16:06:16" }, "status_log_first_occurrence": { "failed_delivery": "2023-06-08 16:06:16", "out_for_delivery": "2023-06-08 12:09:06", "intransit": "2023-06-07 00:16:22", "dispatched": "2023-06-06 19:49:23", "out_for_pickup": "2023-06-06 16:46:12", "packed": "2023-06-05 21:09:05", "picked": "2023-06-05 17:30:14", "accepted": "2023-06-05 17:00:08", "created": "2023-06-05 16:59:09" }, "status_log_count": { "created": 1, "accepted": 1, "picked": 1, "packed": 1, "out_for_pickup": 1, "dispatched": 1, "intransit": 7, "out_for_delivery": 1, "failed_delivery": 1 }, "status_log_id": "124953537", "orderExternalCreatedAt": "2023-06-05 16:59:05", "shippingAddress": { "customerName": "Aman Verma", "addressLine1": "Sadafal kunj", "addressLine2": "Arjun club road ward num 26", "city": "churu", "state": "RAJASTHAN", "postalCode": "331403", "countryCode": "IN", "countryName": "INDIA", "contactPhone": "7891971009", "email": "Amitv12330@gmail.com" }, "warehouseAddress": { "addressLine1": "MJ Logistics Private Limited, Seabird Marine Services Pvt Ltd", "addressLine2": "Village Babra Bakirpur, Pataudi Road Near Adani Logistic Park, ICD Patli, Gurgaon, Haryana(122503)", "city": "Gurgaon", "state": "Haryana", "postalCode": "122503", "gstin": "06AAFCB0498R2Z2" }, "id": 17148471, "isCOD": "1", "track_payload": { "clickPostTrackData": { "location": "Sardarshahr_IndustrialArea_D (Rajasthan)", "additional": { "courier_partner_edd": "2023-06-09", "destination_hub_inscan_ts": null, "order_id": "4980116095129-90758", "latest_status": { "status": "RT In Transit", "clickpost_status_description": "FailedDelivery", "clickpost_status_bucket": 5, "reference_number": "4980116095129-90758", "clickpost_status_bucket_description": "Failed delivery", "remark": "Code verified cancellation", "timestamp": "2023-06-08T14:58:41Z", "location": "Sardarshahr_IndustrialArea_D (Rajasthan)", "clickpost_city": null, "clickpost_status_code": 9 }, "is_rvp": false, "ndr_status_code": 14, "ndr_status_description": "OTP-based cancellation", "account_code": "ESB_Delhivery_Forward_500g_Express", "npr_status_code": null, "npr_status_description": null }, "status": "RT In Transit", "clickpost_city": null, "clickpost_status_code": 9, "clickpost_status_description": "FailedDelivery", "cp_id": 4, "remark": "Code verified cancellation", "account_code": "ESB_Delhivery_Forward_500g_Express", "waybill": "1704612602165", "timestamp": "2023-06-08T14:58:41Z" } }, "account_slug": "vitaminplanet", "packed_date": "2023-06-05 21:09:05", "items": [ { "order_item_id": 31200595, "lineItemSequenceNumber": 12566731260057, "orderItemID": "4980116095129-31200595", "itemID": "45162317217945", "sku": "06REP3HBCN3", "asin": "", "productName": "Advance Whey Protein with 20 Vitamins & Minerals", "quantity": 1, "orderItemCreatedAt": "2023-06-05 16:59:05", "customerPrice": 2099, "lineItemTotal": 1889.0999999999999, "invoiceTotal": 1889.0999999999999, "cashOnDeliveryCharges": 0, "discount": 209.90000000000001, "taxRate": 0, "taxAmount": 0, "inventoryItemCode": "G-IB1735411", "giftMessage": "", "isGift": "0", "giftLabelContent": "", "lineItemOrderStatus": "", "orderItemIDs": [ "4980116095129-31200595" ], "productImageUrl": null, "productAdditionalInfo": { "size": "Kulfi \/ 1KG \/ Gloves" }, "expectedDeliveryDate": "2023-06-09", "shippingCharges": 0, "productUrl": null, "originalOrderItemId": null, "isVirtualKit": "1", "component": [ { "inventoryItemCode": "G-IB1665164", "productAdditionalInfo": "", "whOrderItemID": "4980116095129-31200595\/1", "esin": "63MYP3HA5I0" }, { "inventoryItemCode": "G-IB1735411", "productAdditionalInfo": "", "whOrderItemID": "4980116095129-31200595\/2", "esin": "75V0P3HA6O1" } ], "onhold": "0", "cancellationAdditionalReason": "", "cancellationReason": "", "customerOrderItemID": "", "recallBlockedInventoryUsed": "" } ] }, "previous_data": [], "resource_type": "shipment.update", "account_slug": "vitaminplanet", "custom": [] }

    

10. From the above event, we fetch and store the required details in WhatsappDataDto on our system

11. After confirmation of the above (as we received the FDR event) we verify is the event valid

12. We verify the above we check if poe_setting.isWhatsappEnabled flag is enabled or not on the basis of user account_id (we implement caching here to store the user setting)

13. For all the cases of FDR refer to the heading “Type of FDR” where all the reasons and templates exist and the message will trigger the following way:

    1. for eg. we take the case of “Customer Unreachable” After confirmation of the above we trigger Gupshup API:

    2. curl: curl --location 'http://media.smsgupshup.com/GatewayAPI/rest' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'send_to=9650186697' \ --data-urlencode 'msg_type=Text' \ --data-urlencode 'userid=2000226232' \ --data-urlencode 'auth_scheme=plain' \ --data-urlencode 'password=MkTfyQjA' \ --data-urlencode 'method=SendMessage' \ --data-urlencode 'v=1.1' \ --data-urlencode 'format=json' \ --data-urlencode 'msg=Hello {{1}}! Your {{2}} order ID {{3}} having {{4}} items couldn'\''t be delivered as your number ({{5}}) was unreachable. Please provide an alternate contact number for better connectivity. Item(s) included in the order: - {{6}} - {{7}} - {{8}} Please choose your desired action' \ --data-urlencode 'isTemplate=true' \ --data-urlencode 'msg_id=testLakshay' ---- msg_id can be configured here in params here various parameters that are send which are as follows (mandatory fields): 1. userid (HSM account id) fetched from connection ids 2. password 3. send_to (customer_number) 4. msg: here we fetch the template (registered template) here we need to pass the variables as well variables like customer_name, order details 5. isTemplate

        

    3. As the message is triggered we receive DLR (delivery report) with each status if the status is delivered, seen the DLR events are received on our webhook (/api/_ah/v1/message)
       
       

       {"response": "[{\"srcAddr\":\"TESTSM\",\"channel\":\"WHATSAPP\", \"externalId\":\"4921687316728868875-376937873247896673\", \"cause\":\"SENT\",\"errorCode\":\"025\", \"destAddr\":\"919650186697\", \"eventType\":\"SENT\", \"eventTs\":1686222477000}]"}

        

    4. We have various codes on the basis of we figure out the status which is as follows: errorCode cause Status 000 SUCCESS DELIVERED 025 SENT SENT 026 READ READ 020 OTHER FAILED 003 UNKNOWN_SUBSCRIBER FAILED 010 DEFERRED FAILED 022 BLOCKED_FOR_USER FAILED 101 24 Hour exceeded FAILED

    5. On the same API, we also received a response from the customer which is as follows:

       mobile : 919650186697 type : button button : {\"text\":\"Select new delivery date\"} context : {\"from\":\"919319278973\",\"id\":\"gBEGkZZQGGaXAgkHASKxKpM-kA4\"} timestamp : 1686222621000 waNumber : 919319278973 replyId : 4921687316728868875 messageId : 376937873247896673 name : Lakshay

        

    6. On the basis of the above response received we save the details in db new table defined in data model “whatsapp_status_log” for the above case user selected another delivery date and his response received was as follows:

    7. mobile : 919650186697 type : interactive interactive : {\"type\":\"button_reply\",\"button_reply\":{\"id\":\"{\\\"msgid\\\":\\\"b2fab0a7-4ae6-4dc6-b749-6d1c57f932fa\\\",\\\"reply\\\":\\\"10 June 2023 2\\\",\\\"postbackText\\\":\\\"10 June 2023\\\"}\",\"title\":\"10 June 2023\"}} context : {\"from\":\"919319278973\",\"id\":\"gBEGkZZQGGaXAglFLznXQ0Oi4Y4\"} timestamp : 1686222630000 waNumber : 919319278973 name : Lakshay we fetch reply details from request and save in our system

14. Reference what would be the cases are as follows FDR whats app notifications

15. As soon as the message is triggered we also need to log the activity and reflect the same on the workspace, would be receiving a response from Gupshup API which would tell the state of the sent message on WhatsApp to the customer

16. We need to update the activity log in the following ways:

    1. eg. Eshopbox notified John Doe

    2. First when the message is triggered: Gupshup App name: eshopbox From number: 489876578 To number: 9650186697 Sent on: "time" Second when the DLR report is received: Gupshup App name: eshopbox From number: 489876578 To number: 9650186697 Sent on: "time" Status: SENT Time: Third when the DLR report is received: Gupshup App name: eshopbox From number: 489876578 To number: 9650186697 Sent on: "time" Status: READ Time: readTime:

        

    3. All the above data points required for activity fetched from db “whatsapp_status_logs”

17. For triggering activity events we have received DLR which is mentioned in 13. c point above we need to create an event for the same which would be subscribed to by the notification service

18. Cases to be handled when a message is triggered for FDR reason can vary and for “new delivery date” the customer would be prompted to enter the new delivery date as soon as the customer selects the same we will call API: “_ah/esb/v1/ndrNotification” this API updates the delivery date in the system

19. For address updates, we will redirect the customer to the customer portal and the same goes for adding an alternate number

20. For the URL to be identical to WhatsApp (customer portal), we need to configure a new static URL in Poe-backend-notification when the message is triggered for the FDR case and the same URL needs to be redirected to API which is mapped on the server “/trackShipment/WhatsApp/{shipment_id}” this will create separate URL for WhatsApp help identify where the customer came from

EDGE CASES HANDLING:

1. In the case where a customer doesn’t take action for a certain time period and the later customer comes and visits the chat to take action and the order is no more an FDR, we need to fetch the message-Id of response from the customer on the basis of which we fetch shipment_id and then cross verify the order status and update the same we can configure API for the same or we can handle on our end

2. Multiple actions taken by the customer we need to take action on the basis of the last response received and we will ignore the above because it might be the case that the customer mistakenly chose the first response we give the benefit of the doubt to the customer

3. In the case where the customer didn’t respond back for a certain period of time, we can add an API call there to update the order_status to notify the customer (to be discussed whether it should be covered or not)

4. In the case where the order is already delivered while the FDR event is sent and the customer performs an action on WhatsApp, we can add fallback by calling API “/order/status” and if the status is delivered we can show the same response to the customer else we will take input from a user to take action.

Exceptional Cases:

• The action is received when the order is not in failed delivery status.

  • Standard message to be sent to the customer @ASHITA GUPTA (Unlicensed)

  • No action is to be taken on the order @Lakshay Aggarwal (Unlicensed) (an approach we can add API call for current order status and save the response in a variable named “order status” and can add check for status if delivered we trigger message fixed template all to be done on Gupshup UI)

• Multiple actions were received on a single failed delivery order.

  • For a single message, the user takes more than 1 action.

• Multiple times failed delivery due to the same reason.

  • No change, if an order is failed multiple times, a message will be triggered. @Lakshay Aggarwal (Unlicensed) (retry attempts are limited which are three so at max 3 times FDR event would be received)

• Random input from the customer to the Eshopbox mobile number.

  • Standard message to be sent to the customer @ASHITA GUPTA (Unlicensed)

  • To be ignored at the webhook level @Lakshay Aggarwal (Unlicensed) (if we receive a random reply we need to ignore the same webhook response backend level)

• Random reply from the customer to Eshopbox message.

  • Standard message to be sent to the customer @ASHITA GUPTA (Unlicensed)

  • No action is to be taken on the order @Lakshay Aggarwal (Unlicensed)

  • The response of the customer needs to be logged in the form of activity @ASHITA GUPTA (Unlicensed) @Lakshay Aggarwal (Unlicensed) (we are saving details of the customer in db parallel to messageId)

    • The customer replies with an image, doc, and text, and sends the location (we can handle this case by verifying with the key in case of the image our response will contain a key named “image” we need not perform any action on the same. Same goes for doc, send )

      • Image in response "mobile": "919650186697", "type": "image", "image": "{\"signature\":\"6e730fbde2e6b69e9f73c5faa354277a264d4636a72e8a34ad94cda8d50db29a\",\"mime_type\":\"image/jpeg\",\"url\":\"https://gs-datareceiver-whatsapp.s3.ap-south-1.amazonaws.com/4925813498683490963_b8793b9b-066e-44c5-82bc-27d9a8ee72b6?X-Amz-Algorithm\u003dAWS4-HMAC-SHA256\u0026X-Amz-Date\u003d20230614T034555Z\u0026X-Amz-SignedHeaders\u003dhost\u0026X-Amz-Expires\u003d172800\u0026X-Amz-Credential\u003dAKIAV4FTFRLFCLI4BR77%2F20230614%2Fap-south-1%2Fs3%2Faws4_request\u0026X-Amz-Signature\u003d\"}", "timestamp": "1686714354000", "waNumber": "919319278973", "name": "Lakshay" } Location in response { "mobile": "919650186697", "type": "location", "location": "{\"latitude\":28.50553321838379,\"longitude\":77.08879089355469}", "timestamp": "1686714598000", "waNumber": "919319278973", "name": "Lakshay" } Doc in response { "mobile": "919650186697", "type": "document", "document": "{\"signature\":\"b985104b4af0442702d3c1ce49ff9b7bce5b667deaeafae939e9704fa24974a8\",\"mime_type\":\"text/csv\",\"caption\":\"cancelled_status\",\"url\":\"https://gs-datareceiver-whatsapp.s3.ap-south-1.amazonaws.com/4925816724712469067_3d5ffaf9-91e9-4bc2-9760-b5792fe3951a?X-Amz-Algorithm\u003dAWS4-HMAC-SHA256\u0026X-Amz-Date\u003d20230614T035220Z\u0026X-Amz-SignedHeaders\u003dhost\u0026X-Amz-Expires\u003d172800\u0026X-Amz-Credential\u003dAKIAV4FTFRLFCLI4BR77%2F20230614%2Fap-south-1%2Fs3%2Faws4_request\u0026X-Amz-Signature\u003d\"}", "timestamp": "1686714739000", "waNumber": "919319278973", "name": "Lakshay" }

• Non-working / operational hours messages

OPEN:

• From where the action is taken? How to identify? @Lakshay Aggarwal (Unlicensed) (action would be performed on customer portal as discussed as of now)

• According to the Gupshup API doc, there is a payload section in the DLR response here we are not receiving the payloads need to figure that out (Gupshup) looks like below

• "payload": { //Varies according to the type of payload. },

  examples: "payload": { "id": "ABEGkYaYVSEEAhAL3SLAWwHKeKrt6s3FKB0c", "source": "918x98xx21x4", "type": "text", "payload": { "text": "Hi" }, customer reply to business message { "app": "DemoApp", "timestamp": 1590854464792, "version": 2, "type": "message", "payload": { "id": "ABEGkYaYVSEEAgo-sMx1DoUoQJRW", "source": "918x98xx21x4", "type": "text", "payload": { "text": "hi" }, "sender": { "phone": "918x98xx21x4", "name": "Smit", "country_code": "91", "dial_code": "8x98xx21x4" }, "context": { "id": "gBEGkYaYVSEEAgnPFrOLcjkFjL8", "gsId": "9b71295f-f7af-4c1f-b2b4-31b4a4867bad" } } }

   

Approach: We have to make a new API for URL creation to differentiate the message coming in from Whatsapp, internally current functionality would be appended with the cases to handle WhatsApp cases explained in the 20th point above

Sequence Diagram: