> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/platform-api/whatsapp-setup.md).

# WhatsApp Setup

Managed WhatsApp provisioning, business-scoped recipient identity, asynchronous replies, and the separate service voice-note API.

WhatsApp setup and business-account registration are managed provisioning operations. They are not workspace-scoped endpoints in the public Platform API. Workspace applications do not create or delete the upstream business setup with a Platform API key.

Contact Concurrence to complete business-account provisioning and bind a WhatsApp use case to an eligible service. [Use Cases and Bindings](/developer-guide/platform-api/workspaces/use-cases.md) describes the public service-binding operations.

## Managed Conversations

Ordinary inbound messages can drive the bound agent and receive an asynchronous text reply. Recipient addressing uses a business-scoped user identifier; do not substitute a phone number or assume that phone metadata is always present. Continuity uses the recipient identity and use case.

Managed free-form replies require an inbound message to that use case within the previous 23 hours. Template registration and status tracking do not provide a template-send path. An approved template therefore does not enable out-of-window outreach through this send path.

Inbound media and reaction records, read receipts, agent completion, and outbound delivery have separate meanings. A reaction without message or media content does not drive an agent turn, and a read receipt does not prove that the agent completed the task.

The public conversation-start and channel-switch operations do not create outbound WhatsApp threads. See [WhatsApp concepts](https://docs.concurrence.com/channels/whatsapp) for delivery and media boundaries.

## Separate Voice-Note API

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/services/{service\_id}/voice-turn" method="post" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

This operation accepts recorded audio and returns the agent's audio response to the calling integration. That integration is responsible for delivery to WhatsApp or another destination. It is not automatic managed WhatsApp media processing.

Voice-note continuity is keyed by workspace, service, and phone number and remains separate from managed WhatsApp text history. See [Voice Agent](/developer-guide/platform-api/conversations/voice-agent.md#whatsapp-voice-notes) for response negotiation and session behavior.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/platform-api/platform-api/whatsapp-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.