---
title: Call Button
slug: call-button
docTags: 
createdAt: 2025-08-18T14:03:11.809Z
---

### Introduction

This command allows you to send an image with a **call-to-action button** that lets the user initiate a phone call directly. It is useful for contact requests, sales follow-ups, or customer support.

:::hint{type="warning"}
 ⚠️ This feature is currently in **beta** and does **not work on Apple devices**.
:::



::Image[]{src="https://api.archbee.com/api/optimize/srzEvL3tK0Cgq-VfwOzrO/NNffRDDK55wbUJBe9N9Nw_image.png" size="46" width="520" height="454" position="center" caption="Call button preview" showCaption="true"}

### Command Syntax

:::BlockQuote
\#ButtonMix|Title|Subtitle|image\*IMAGE\_URL|call\*ButtonText\*id\_call
:::

### How it works

1. **#ButtonMix** → Defines the message type (multimedia with buttons).
2. **Title** → Main text displayed above the image.
3. **Subtitle** → Secondary text displayed below the title.
4. **image\*IMAGE\_URL** → Link to the image file in .jpg format (file size depends on CRM, commonly up to 5 MB).
5. **call*ButtonText*id\_call** → Defines the call button:
   - ButtonText → The label displayed on the button (e.g., *Call Now*).
   - id\_call → The identifier for the call action.

### Example

:::BlockQuote
\#ButtonMix|Title|Subtitle|image\*https\://wisphub.io/static/img/wisp-bg-5.jpg|call\*Call Now\*id\_call
:::

::Image[]{src="https://api.archbee.com/api/optimize/srzEvL3tK0Cgq-VfwOzrO/kGz7LJY60DH0flWvnZtJO_image.png" size="38" width="538" height="448" position="center" caption="Real customer example" showCaption="true"}

### Result

1. The user receives a message with an **image**, a **title, subtitle**, and a **Call button**.
2. When the user clicks the button, their phone attempts to initiate a call.
3. The CRM may log the event or trigger a flow, depending on integration capabilities.

### ⚠️ Important Notes

1. The image must be in **.jpg** format. Maximum file size depends on your CRM (commonly 5 MB).
   - Highlevel CRM Integration
2. This feature is **in beta** and **does not work on Apple devices**.
3. Button text should remain **short and action-oriented** (e.g., *Call*, *Call Now*).
4. Unlike standard response buttons, **no text response is recorded** when the user initiates a call.