# Delivery status

How Zernio keeps the delivery status of each outgoing WhatsApp, SMS and RCS message up to date on its HubSpot timeline entry.

## Before you start

`logMessages` and `logDeliveryStatus` must both be on. They are by default; see [Change what syncs](/platforms/hubspot/connect#change-what-syncs).

## Read the status in HubSpot

Each outgoing WhatsApp, SMS and RCS message logged on a contact ends with a status line, which Zernio updates as the platform reports progress:

| Line | Meaning |
|------|---------|
| `Status: Sent` | The platform accepted the message |
| `Status: Delivered` | It reached the recipient's device |
| `Status: Read` | The recipient opened it |
| `Status: Played` | The recipient played a voice message |
| `Status: Failed: <reason> (<code>)` | It was not delivered, with the platform's reason and error code |

## Turn it off

```bash
curl -X PATCH "https://zernio.com/api/v1/accounts/ACCOUNT_ID/hubspot-settings" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "logDeliveryStatus": false }'
```

Messages are still logged. New entries carry no status line, and existing ones stop updating.

## How it behaves

- The entry is updated in place: a read message shows `Status: Read`, not one line per step.
- Incoming messages, and channels that report no delivery status, have no status line.
- Statuses only update entries that were logged, so turning off `logMessages` stops them too.

## Related

- [Inbox sync](/platforms/hubspot/sync)
- [Send templates from HubSpot](/platforms/hubspot/send-templates)
- [Update HubSpot settings](/accounts/update-hub-spot-settings)