Skip to main content

HubSpot SMS tracking and delivery

Check whether a proactive message sent from HubSpot reached the recipient, and review recent messages sent to any phone number.

Written by Mohamed Elbadwihi

Use this article for HubSpot SMS tracking: checking whether an SMS (through Twilio) or WhatsApp message you sent from a HubSpot card or workflow reached the customer. It also explains what to do when HubSpot shows a text as sent but it never arrived. To automate messages, visit HubSpot workflows with Octopods.

How delivery status works

When you send a proactive message from HubSpot — from an Octopods extension card or a workflow action — Octopods hands the message off to the channel provider (Twilio for SMS, WhatsApp Business Platform for WhatsApp) and returns a request ID.

Delivery happens in two steps:

  1. Processing. Octopods validates the request, picks a channel, and sends to the provider. This usually completes within seconds.

  2. Delivery. The provider attempts to deliver the message to the recipient’s device. This happens asynchronously, so the final status becomes available shortly after processing.

A conversation thread inside HubSpot is created in the background once delivery is confirmed — there is a brief delay between clicking Send and seeing the conversation appear in the HubSpot inbox.

Reading status in the extension card

On the Choose a Channel step, click View Message History to open the Message History table for the contact’s phone number. The table has four columns:

  • Date — when the message was submitted.

  • Channel — which Octopods channel sent the message (Twilio SMS or WhatsApp Cloud).

  • Status — a coloured tag: Delivered, Pending, or Failed.

  • Details — a short description: Successfully delivered for success, Processing… for pending, or the failure reason for failed sends.

Status values you may see

The Message History table uses three summary tags:

Tag

What it means

Delivered

The provider accepted and Octopods has processed the message.

Pending

Octopods has accepted the message but has not yet confirmed processing.

Failed

The send failed. The Details column shows the failure reason.

The latest version of the card labels the Delivered tag as Sent. Both mean the same thing.

HubSpot SMS sent but not delivered

In the Message History table, Delivered (or Sent) means Octopods sent the message to the provider and logged it in HubSpot. It never updates from Twilio’s final delivery report. For SMS, Twilio accepting a message doesn’t guarantee that the carrier delivered it to the phone. Carriers can still filter or reject it afterwards.

Where to see the real SMS delivery status. Twilio has the final carrier result. In the Twilio Console, open Monitor, then Messaging logs, and search for the customer’s number. Each message shows its final status and, if it wasn’t delivered, a Twilio error code. For common codes and fixes, see Troubleshooting undelivered messages.

Common reasons an SMS shows as sent but never arrives:

  • Your US number isn’t registered for A2P 10DLC, so carriers filter the messages. See Setting Up Twilio SMS for HubSpot.

  • The customer replied STOP to your number earlier.

  • The number is a landline or no longer active.

  • Your Twilio account isn’t allowed to send to the customer’s country.

HubSpot shows Failed but Twilio shows Delivered

If Twilio’s log shows the message as delivered, the customer received it, even if HubSpot shows Failed. This happens when an error occurs after sending, while Octopods creates the HubSpot conversation. Octopods then marks the message as failed.

Don’t re-send the message until you’ve checked Twilio’s log, or the customer may get it twice. Check whether the conversation appeared in HubSpot, then contact Octopods support with the request ID and the Twilio message SID.

For workflow sends, also see Monitoring Workflow Message Delivery.

Checking a workflow-triggered message

Messages sent by a HubSpot workflow appear in the same Message History table for the enrolled contact. They also show in HubSpot’s workflow history for the enrollment — open the contact’s workflow enrollments to see the per-step result, including any Octopods error message.

Tip: If a workflow action fails for a specific contact, re-enroll that contact after fixing the underlying issue (missing phone, stale template, etc.). Octopods does not automatically retry workflow sends.

Tracking via request ID

Every send returns a request ID. If you are looking at logs or scripts outside the HubSpot UI and need to confirm a specific send succeeded, quote the request ID when contacting Octopods support so they can trace the exact delivery attempt.

When a conversation doesn’t appear in HubSpot

The HubSpot CRM card creates or reuses a conversation thread automatically after a successful send. If no thread appears within a minute or two:

  1. Confirm the message status in the Message History table is Sent or Delivered. If it’s Failed, no conversation is created.

  2. Check the Octopods workspace connected to your HubSpot portal is still active.

  3. See Troubleshooting undelivered messages for further diagnostics.


What’s next

Did this answer your question?