> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/message/in-app-messaging/how-to-create-a-call-send-an-sms-or-send-an-email-button-to-an-in-app-message.md).

# How to create a "Call", "Send an SMS", or "Send an email" button to an In-App message?

See how you can direct users to their default phone, email or sms app by simply clicking an In-App button.

In-App messages allow you to trigger a wide variety of actions when users click a button, including opening the default phone, SMS, or email app with a predefined phone number or email address. This can be done by using links such as:

* **tel:+00XXXXXXXXX**: opens the default phone app. Users just need to press the call button to call the phone number included in the link.
* **sms:+00XXXXXXXXX**: creates a draft in the default SMS messaging app. Users only need to type a message and click "Send" to send an SMS to the linked phone number.
* **mailto:<example@domain.com>**: creates a draft in the default email app. Users only need to type a message and click "Send" to contact the linked email address.

These links improve the user experience: users are redirected to their default app with the phone number or email address already filled in, instead of having to copy-paste it and open the app manually.

Here is how to use these links in an [In-App automation](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/in-app-automations) or a Mobile Landing.

## Creating a "Call" button in an In-App message <a href="#h_88189175cf" id="h_88189175cf"></a>

To redirect users to their phone app:

1. In the [Composer](https://doc.batch.com/getting-started/features/customer-engagement-platform/content/composer), select the button of your message.
2. In the **Action** field, select **Deeplink** and enter the phone number in this format: `tel:+33123456789`

Depending on their device, here is what the redirect could look like once users click the "**Contact Us**" button:

<figure><img src="https://downloads.intercomcdn.com/i/o/510011605/e1ecafeba392281157ddadcf/Group+3.png?expires=1744885800&#x26;signature=5fe8840bf3ae76c5bc45c8ca57f0d46201df5f44c3b3dc5c1f2b1f99fcb2cf96&#x26;req=cSEnFsh%2Fm4FaFb4f3HP0gPvkBzzaoN2iQpBrgIIaw1x0%2FPHTwZIFtj3lBClx%0AfK5rfypfeG6WCGs5Vw%3D%3D%0A" alt=""><figcaption></figcaption></figure>

## Creating a "Text" button in an In-App message <a href="#h_4bd4c65887" id="h_4bd4c65887"></a>

To redirect users to their SMS app:

1. In the Composer, select the button of your message.
2. In the **Action** field, select **Deeplink** and enter the phone number in this format: `sms:+33123456789`

## Creating an "Email" button in an In-App message <a href="#h_0fe78db751" id="h_0fe78db751"></a>

To redirect users to their email app:

1. In the Composer, select the button of your message.
2. In the **Action** field, select **Deeplink** and enter the email address in this format: `mailto:experts@batch.com`

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FlbwJDf3L8HJYK4NQ1Ziq%2F1792514020387_CleanShot%202026-10-20%20at%2018.31.182x.png?alt=media&amp;token=99cbb506-0f1a-442e-b7e5-186b38d192ed" alt=""><figcaption></figcaption></figure>

Depending on their device, here is what the redirect could look like once users click the "**Contact Us**" button:

<figure><img src="https://downloads.intercomcdn.com/i/o/510017634/113ea53f23c8eb96506c9ec8/Group+2.png?expires=1744885800&#x26;signature=d2155525ff3a3ef8fc76682453c7783d9902e6bf6367a822f2618f02dc85db2d&#x26;req=cSEnFsh5m4JbFb4f3HP0gNFX5%2FWhrYdGBD3Zrzl4jVbF9D4XC5vi%2F7WKqIAn%0A%2B7mc3wtMfvOBfUOSCA%3D%3D%0A" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
We recommend **adding an emoji** that clarifies the action that will follow in the CTA.

Ex: ✉️ Contact us vs 📞 Contact us
{% endhint %}


---

# 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://doc.batch.com/guides-and-best-practices/message/in-app-messaging/how-to-create-a-call-send-an-sms-or-send-an-email-button-to-an-in-app-message.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.