> 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/conversations/sms.md).

# SMS

Integrate with provisioned SMS use cases through the workspace conversation lifecycle, with separate consent, suppression, and delivery controls.

Workspace applications use a provisioned SMS use case and the [Conversations API](/developer-guide/platform-api/conversations.md) to start and continue durable agent conversations. Concurrence manages sender registration, number assignment, provider credentials, and inbound delivery. Contact the Concurrence team to provision a use case before binding it to a service.

Direct sends and recipient controls use separate [Channel Manager APIs](/developer-guide/platform-api/conversations/channel-manager.md). Its [SMS recipient endpoints](/developer-guide/platform-api/conversations/channel-manager.md#sms-recipient-opt-in-and-opt-out) support opt-in messaging, opt-out reads, and suppression reversal. They require Channel Manager credentials and scopes; a workspace API key does not grant access. Sender provisioning remains a separate onboarding step.

## Bind a Provisioned Use Case

Use [Use Cases and Bindings](/developer-guide/platform-api/workspaces/use-cases.md) to inspect eligible routing and bind the SMS use case to a service. A binding selects the service configuration; it does not establish carrier approval or recipient consent.

## Start an Outbound Conversation

{% openapi src="<https://api.platform.amigo.ai/v1/openapi.json>" path="/v1/{workspace\_id}/conversations" method="post" %}
<https://api.platform.amigo.ai/v1/openapi.json>
{% endopenapi %}

Select the SMS channel and a provisioned use case bound to the service in your workspace. The channel resolves its sender from the provisioned pool. See [Starting an Outbound Conversation](/developer-guide/platform-api/conversations.md#starting-an-outbound-conversation) for the integration workflow.

Conversation creation, the agent's completed turn, provider acceptance, and recipient delivery are separate outcomes. A send rejected by channel policy can leave recorded conversation evidence without a delivered reply. Do not apply one channel-manager error code to every workspace conversation operation.

## Inbound Messages and Continuity

Managed inbound delivery validates the provider, resolves the destination use case, and routes ordinary content to the current non-terminal conversation. Phone-based continuity does not itself verify the patient's identity. Recognized consent-management keywords are handled by the channel rather than the agent on the supported sender paths.

## Consent and Suppression

Complete the campaign review before outreach. Customer consent evidence must cover the sending brand and intended messages. Concurrence's opt-in-message record reflects provider acceptance of registered confirmation copy, not proof of prior consent or recipient delivery.

Recognized opt-outs suppress ordinary sends across the recipient's managed business setup. Starting another conversation or selecting another number within that setup does not bypass suppression. On the supported toll-free path, `START` or `UNSTOP` clears the line-specific opt-out only. After reviewing renewed consent, a caller with Channel Manager's `sms:consent:write` permission can separately reverse setup suppression with a recorded reason. Workspace credentials alone cannot authorize this reversal.

Registered sender pools also apply content checks to ordinary outbound text. A blocked or unavailable check prevents the send; media handling has different coverage. The full sender, keyword, consent, and registration boundaries are in [SMS concepts](https://docs.concurrence.com/channels/sms).

## Delivery Evidence

Delivery callbacks can update recorded status after the provider accepts a message. Some carrier paths do not supply final delivery receipts. Inspect the evidence exposed for your deployment rather than treating a completed tool or agent turn as a delivered message.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.concurrence.com/developer-guide/platform-api/conversations/sms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.