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

# Send SMS during a call

> Use a Message node to text the caller while they're still on the line, for example a confirmation code, an address or a link.

## How it works

When the flow reaches a Message node, Voicy sends the SMS and moves on right away through the node's **Success** or **Error** branch. The caller hears nothing from this node itself, so the next node usually tells them the message is on its way.

| | Value |
| - | - |
| **Sender** | The agent's phone number on this call: the number the caller dialed (inbound) or the number the agent called from (outbound). |
| **Recipient** | The caller's phone number. |
| **Body** | The text you write in the node. |

You can't change the sender or recipient in the node.

## Set it up

<Steps>
  <Step title="Add the node">
    Add a **Message** node to your flow and open **Message Settings**.
  </Step>

  <Step title="Write the message">
    Type the SMS body. Type `[` to insert a variable collected earlier, for example `שלום [customer_name], קוד האישור שלך הוא [confirmation_code]`. A character counter is shown. There's no length limit, and long messages are split into parts automatically.
  </Step>

  <Step title="Connect both branches">
    Route **Success** to the next step and **Error** to a fallback, for example reading the details aloud instead.
  </Step>
</Steps>

## Requirements

<Warning>
  SMS works only on calls to or from a phone number bought through Voicy, and that number must support SMS. On SIP trunk calls and browser test calls, the node always takes the **Error** branch without sending.
</Warning>

When you verify or deploy the flow, you get a warning (not a blocking error) if the agent has no phone number or its number isn't SMS-capable.

## In the transcript

Each send attempt adds one system row: **SMS sent** on success, or **Send failed** with the error detail. Expand it to see the sender, recipient, body and status. Both successful and failed attempts are recorded with the call.

## Tips

* Test the full flow on a real phone call. A browser test can only exercise the Error branch.
* Keep the message short and self-explanatory. The caller may read it after hanging up.
* If a variable in the body wasn't collected, check the flow order so it's collected before the Message node.


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