J
Jacob Radcliffe
Your deeper integration with Twilio allows you to handle delivery receipts that are sent in at a later time from the message. When we work with these other providers they are pretty slow. Like really slow. Ideally we can add metadata like a messageId from the API we are sending messages with. So for example:
  1. Conversation Provider Outbound SMS Webhook received - includes GHL messageId, message, et
  2. API call to a SMS Provider. They provide their own messageId in the response. We currently have nowhere to save this messageId, and no way to tie it to GHLs internal messageId.
Searching Issues: Normally we wait and attempt to get a message receipt and then update delivery on update message status endpoint. This is not always reliable. But searching last sent messages isn't reliable because its possible other messages came in or out since that message.
Ideally the update message status endpoint has a few upgrades:
  1. A field on the "Update Message Status" endpoint for externalMessageId or customSMSMessageId, etc. We also need an update on "Search Conversations" so we can query our externalMessageId and find the GHL internal messageId.
  2. Additional message status for "queued" so we can at least give a time stamp in GHL on the "Update Message Status" endpoint. If its on pending we don't get a timestamp in the UI. Various APIs use this status to indicate that they received the message, its in the queue, but they are waiting on a delivery receipt to update it again. Pending tells you nothing and gives you no internal data/messageIds to reference like it does with twilio messages.