> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telzino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Twilio

> Connect your organization's Twilio account once so every agent can send SMS

Telzino can send text messages through your own Twilio account — the [Send SMS](/functions/send-sms) function, payment links for [Card Payments](/functions/card-payments), and booking links for [OpenTable Reservations](/functions/opentable-reservations).

## One connection per organization

Twilio credentials belong to the **organization**, not to a single agent. Each organization has exactly **one** Twilio connection, and every agent in it uses that connection.

* **Rotate once, done everywhere.** Saving new credentials updates every agent in the organization on its next call.
* **Credentials only.** The connection holds the Account SID and either an Auth Token or an API Key SID + API Key Secret. It does not hold a phone number.
* **Secrets stay hidden.** The Auth Token and API Key Secret are never shown again after saving. When editing, leave them blank to keep the organization's stored secret — this works only while the Account SID (and, for an API key, the API Key SID) is unchanged. An agent still on its own Twilio credentials must enter the secret again the first time it is saved.

## How to connect Twilio

Connect Twilio once for the organization, then turn on Send SMS on the agents that should text.

<Steps>
  <Step title="Open the organization">
    In the Telzino Dashboard go to **Customers > Resellers and Organizations** and click the organization: the **Twilio SMS** card sits above its list of agents, next to PII Redaction and Screenshare. In the Connect app, open **Agents**: the **Twilio SMS (applies to all your agents)** panel sits at the top of the list.
  </Step>

  <Step title="Enter the credentials">
    Expand the card and enter the **Account SID** (starts with `AC`) and either an **API Key SID** (starts with `SK`) and **API Key Secret**, or the **Auth Token**. We recommend connecting a Twilio subaccount and using an API Key created inside it: the key can be revoked without changing the account's Auth Token. Click **Verify & Save**. Telzino checks the credentials with Twilio before saving (no SMS is sent); a trial account is saved with a warning, and an account that is not active (for example suspended or closed) is saved but flagged.
  </Step>

  <Step title="Turn on Send SMS per agent">
    On each agent that should text, add the **Send SMS** function with the number it texts from (see [From Number](#from-number-per-agent)).
  </Step>
</Steps>

You can also open the same connection from any agent: **\[Agent] > Integrations > Twilio SMS** in the Dashboard, or the agent's **Integrations** (gear icon) in Connect. That dialog notes that the credentials belong to the organization and that saving updates all of its agents. On an agent that still uses its own Twilio credentials, it says instead that saving creates the organization's connection; once it exists, every agent in the organization texts through the account you enter, so a From Number on a different Twilio account stops working. Its **From Number** field is optional in both apps: it sets that agent's number, and leaving it blank saves only the organization's credentials.

<Info>
  In the Dashboard, saving the organization's connection does not add the Send SMS function to agents. Enable it per agent: in the agent's **Functions** section click **Add function**, select **Send SMS**, then click **Add Function**. In Connect, saving a From Number in an agent's Twilio dialog also adds Send SMS to LiveKit agents automatically, and the agent's Add Functions list offers Send SMS only once the agent has a From Number.
</Info>

**Disconnect** on the organization's Twilio card — or in an agent's dialog when the agent uses the organization's connection — removes the organization's connection. This disconnects Twilio for **every** agent in the organization: they stop sending SMS until Twilio is connected again. Agents that still carry their own Twilio credentials from before the organization connection existed keep using them until those credentials are removed. Disconnecting from an agent's dialog also removes that agent's Send SMS function; other agents lose it the next time they are saved. After reconnecting, add Send SMS back in the Dashboard, or save the agent's From Number again in Connect.

On an agent that still uses its own credentials, **Disconnect** removes only that agent's own Twilio settings — its credentials and its From Number — and its Send SMS function. The organization has no connection to remove yet.

## From Number (per agent)

The number an agent texts **from** stays per agent, because different agents often use different numbers on the same Twilio account.

* On the **Send SMS** function, the From Number is part of the function itself.
* Agents that text without a Send SMS function (for example reservation booking links) use the **From Number** field in the agent's Twilio SMS dialog.

The From Number must be an SMS-capable number on the organization's Twilio account.

## API

The [Update Agent](/api-reference/agents/update#integrations) endpoint no longer accepts Twilio credentials on an agent. A request whose `integrations.twilio` sets or changes `accountSid`, `authToken`, `apiKeySid` or `apiKeySecret` is rejected with `400`. `integrations.twilio.fromNumber` is still accepted, and sending back the values a GET returned still succeeds. Connect Twilio for the organization in the Dashboard or Connect as described above.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.