> Every page of the Heythere docs is listed in https://heythere.io/docs/llms.txt: fetch it to find a page instead of guessing its URL.

# Conversations: the WhatsApp 24-hour reply window

> One thread per customer and WhatsApp number. Learn when the 24-hour reply window closes, where replies go, and how each message's delivery is tracked.

Every message between Camille and her repair shop's WhatsApp number sits in one conversation, between one [contact](https://heythere.io/docs/concepts/contacts) and one number of the workspace. Heythere creates it when the contact first writes there or a [broadcast](https://heythere.io/docs/concepts/broadcasts) first messages them. A message is `inbound` when the contact sent it, and `outbound` when an [automation run](https://heythere.io/docs/concepts/runs), a broadcast, a member, or a [verification](https://heythere.io/docs/concepts/verifications) sent it, whose code never shows.

## When does a conversation's reply window close?

WhatsApp lets a business send any message for 24 hours after the contact's latest message, until `replyWindowClosesAt`. If Camille last wrote at 10 a.m. on Monday, the shop answers freely until 10 a.m. on Tuesday. After that, it sends only a [message template](https://heythere.io/docs/concepts/message-templates) Meta approved.

## Which messages does a contact send?

Texts, images, videos, documents, audio, voice notes, places, contact cards, the reply button or list row they tapped, and reactions. Any other message, such as a sticker, is `unsupported`. An automation reads Camille's voice note through its `transcript`, which [AI](https://heythere.io/docs/concepts/ai) writes, unless its `transcribesVoiceNotes` is false.

## Where does an inbound message go?

To the members during a [live chat](https://heythere.io/docs/concepts/live-chats) or after a handover. Otherwise to the conversation's active [run](https://heythere.io/docs/concepts/runs), which reads it only while waiting for a reply. Without an active run, it starts the number's published [automation](https://heythere.io/docs/concepts/triggers#which-automation-answers-a-number-). A reaction never starts or continues a run.

## How does Heythere send a message?

When the shop tells Camille her bike is ready, the message's `state` starts at `sending`, then follows WhatsApp's reports, up to `read`. A message that never reaches her ends `failed`, with a `reason`, such as `reply_window_closed` when it needed a template.

## In the API

Every operation is a REST endpoint and, unless marked REST only, an MCP tool of the same name. [The OpenAPI document](https://app.heythere.io/api/openapi.json) describes their parameters, payloads, and errors.


- `listWorkspaceConversations`: List workspace conversations. `GET /api/organizations/{organizationId}/workspaces/{workspaceId}/conversations`
- `listConversationMessages`: List conversation messages. `GET /api/organizations/{organizationId}/workspaces/{workspaceId}/conversations/{conversationId}/messages`
- `watchWorkspaceConversations` (REST only): Watch workspace conversations. `GET /api/organizations/{organizationId}/workspaces/{workspaceId}/conversation-changes`
- `getMessageMedia` (REST only): Get message media. `GET /api/organizations/{organizationId}/workspaces/{workspaceId}/conversations/{conversationId}/messages/{messageId}/media`
