# How to broadcast messages to a device?

The **Broadcast Message** remote action allows IT administrators to send real-time notifications and instructions to enrolled **Android, iOS, macOS, Windows, and visionOS** devices directly from the Hexnode UEM console.

**What is Message Broadcasting?**
---------------------------------

Broadcasting is a communication feature used to push critical alerts, organizational updates, or device-specific information to users. These messages appear as pop-up notifications and are archived within the Hexnode UEM app for future reference.

- **Dynamic Content:** Supports wildcards to automatically populate device or user-specific data.
- **Persistent Storage:** Messages are saved locally in the Hexnode UEM app’s message center.
- **Multi-Platform Support:** Reach individual devices or entire groups across all major operating systems.

**Prerequisites and Device Setup**
----------------------------------

Before broadcasting, ensure the **Hexnode UEM app** is installed and correctly configured on the target endpoints.

PlatformSetup Requirements**Android**Automatically configured upon enrollment.**iOS / iPadOS**Hexnode UEM app must be opened; users must **Allow Notifications**.**Windows 10/11**Hexnode UEM app installs automatically; no additional configuration required.**macOS**Hexnode UEM app installs automatically; grant **Notification permissions** if prompted.**Step-by-Step Guide: Broadcasting a Message**
----------------------------------------------

Follow these steps to send a message to a single device, multiple devices, or specific user groups.

1. Log in to the **Hexnode portal**.
2. Navigate to **Manage > Devices**.
     Note: 
    You can also initiate this from the Users, Device Groups, User Groups, or Directory Services tabs.
3. Select the checkboxes for the target devices/entities.
4. Navigate to **Actions > Others > Broadcast Message**.
5. Type your message (Maximum **500 characters**).
6. (Optional) Insert **Wildcards** to personalize the message (see list below).
7. Click **Send**.

### **Supported Message Wildcards (Variables)**

Use these tags to display dynamic data: %devicename%, %imei%, %serialnumber%, %name%, %email%, %alternateemail%, %deviceid%, %domain%, %netbiosname%, %udid%, %model%, %phonenumber%, %iccid%, %wifimacaddress%, %department%, %assettag%, %devicenotes%, %osname%, %osversion%.

**User Experience: How Messages Appear**
----------------------------------------

PlatformNotification Behavior**Android**Displayed as a pop-up with **View** (opens app) and **Cancel** (hides to app) buttons.**Android Enterprise**No pop-up for **Profile Owner** mode. View under ‘Messages’ in **Hexnode For Work** app.**iOS / iPadOS**Shown as system notifications and lock screen alerts. Badges indicate unread counts.**macOS**Displayed as a notification pop-up.**Windows**Shown in the system notification area.**Viewing Message History on Devices**
--------------------------------------

The Hexnode UEM app serves as a centralized repository for all broadcasted communications.

### **On iOS and Android:**

1. Open the **Hexnode UEM app**.
2. Swipe from the left to open the menu.
3. Select **Messages** to view the full history.

### **On macOS and Windows:**

1. Open the **Hexnode UEM app**.
2. Navigate to the **Messages** tab.
3. Filter by **All**, **Unread**, or **Read** sub-tabs.

**Broadcasting in Kiosk Mode**
------------------------------

Special configurations are required to ensure users can interact with messages while the device is locked down.

- **iOS:** No specific setup; notifications are displayed natively in Kiosk mode.
- **Android:** Requires enabling the **Hexnode Messenger** via policy. 
    1. Navigate to **Policies > Kiosk Lockdown > Android Kiosk Lockdown**.
    2. Go to **Peripheral Settings > Messenger**.
    3. Check **View messages sent by admin**.
    4. Associate the policy with targets and **Save**.

**Troubleshooting Guides**
--------------------------

ProblemResolutionMessages not appearing on iOS/macOSEnsure **Notification Permissions** are granted for the Hexnode UEM app in the device system settings.Wildcards appear as text (e.g., %email%)This occurs if the specific data field is not available or not yet synced in the Hexnode portal for that device.No pop-up on Android EnterpriseIf enrolled as a **Profile Owner**, notifications are restricted. Users must manually check the **Hexnode For Work** app.Messages hidden in Kiosk ModeEnsure the **Messenger** peripheral setting is enabled in the associated Android Kiosk policy.**Frequently Asked Questions (FAQs)**
-------------------------------------

#### **What is the maximum character limit for a broadcast message?**

Administrators can send messages containing up to **500 characters**, including spaces and wildcard variables.

#### **Can users reply to broadcasted messages?**

No. The **Broadcast Message** feature is a one-way communication tool designed for administrative alerts. It does not support direct replies from the user.

#### **Are messages deleted once they are read?**

No. All received messages are archived within the **Messages** section of the Hexnode UEM app for future reference until the app is reinstalled or the device is wiped.

#### **What happens if a wildcard is used that is not supported by the OS?**

If a wildcard detail (such as %imei% on a Wi-Fi-only tablet) is unavailable, the message will display the raw wildcard string (e.g., “%imei%”) instead of the data.