Live chat and handoff
Chat notifications
Stand notifies reps about chats on the devices where they turn notifications on. A guided setup shows the one next step for the device in hand, ends with a test notification the rep taps, and names the cause when a notification cannot arrive.
- Availability
- Chat notifications are available to signed-in reps on all plans; paid-plan custom-signal notifications require the corresponding signal entitlement
- Configured in
- Stand app → Chats → Notifications, or the bell in the top bar on a phone
- Category
- Live chat and handoff
- Reference status
- Current
Before you begin
Plan availability: Chat notifications are available to signed-in reps on all plans; paid-plan custom-signal notifications require the corresponding signal entitlement.
Prerequisite: An authenticated rep and a supported browser. On iPhone and iPad the Stand app has to be installed on the Home Screen first.
Key boundary: A notification is best-effort delivery, not routing eligibility or proof that a rep saw the event. Browser, operating-system, network, and device settings can suppress an otherwise valid notification.
Choose which events notify you
| Setting under What Stand tells you about | Notification | Default |
|---|---|---|
| A visitor starts a chat with me | New chat started with you | Always on while notifications are on. |
| A visitor starts a chat with my Stand-in | New chat with your Stand-in | On for a rep who sets up their first device. A rep who has a device, or who has saved a notification choice of their own before, keeps what they had. |
| A visitor is waiting for my reply | Visitor waiting for your reply | On. |
| Stand marks me away | You are away from your Stand, or Your Stand-in is covering for you | On. |
| A label or Product Discovery match | The name of the label | Always on here. Each Stand-in’s Skills decide which labels notify. |
Turn notifications on
- The first line of the Notifications panel states where this device stands: on, off, blocked, stopped, or waiting for the Stand app to be installed.
- Under it is the one next step for this device. On a computer that is Turn on notifications. On iPhone and iPad it is the pictured Add to Home Screen steps for the device’s iOS version. On Android it is Install Stand when the browser offers it.
- The panel explains what the rep will get before the browser asks. The browser’s own question appears only after the rep presses Turn on notifications.
- The first time the installed Stand app is opened on a phone, it opens the same panel by itself.
- A card on Chats offers the setup while notifications are off on the device, and can be dismissed.
Test a device
- After Allow, Stand sends a test notification at once. Tapping it confirms that notifications reach the device and can be seen.
- If nothing is tapped within about twenty seconds, Stand asks whether anything appeared, with I saw it and Send again.
- Stand separates a test that reached the device but was kept off the screen from one that never arrived, and shows the checks for that case and device.
- Each device in Your devices shows when it was last tested. Test sends a notification to another device, for example a locked phone.
Manage devices
- Your devices lists every browser and installed Stand app that has notifications on, in plain words such as iPhone, Stand app.
- Add your phone shows a QR code and an address that open the install page on the other device.
- Remove stops notifications to a device that is no longer used.
- If the browser replaces its registration, the Stand app registers the current one the next time it runs on that device.
- When a device loses its permission or registration, the Stand app says Notifications stopped the next time it is opened there and offers Turn on again.
Notifications do not control routing
Availability, I chat here, concurrent capacity, connection health, and organization state determine whether a rep can receive a new human chat. Notification settings run after an event exists and do not add the rep to the routing set.
Conversely, disabling a notification does not mark the rep as away. It only removes that notification, so the rep remains responsible for monitoring Chats while accepting live work.
Device requirements
Notifications cannot be turned on inside another app’s built-in browser or in a private window. The visitor-facing widget never asks for notification permission.
| Device | Install the Stand app first? | Arrive when nothing is running? |
|---|---|---|
| iPhone and iPad | Yes. Notifications work only from the installed Stand app. | Yes |
| Android phone | Yes, when the browser offers to install. Permission given in a browser tab does not carry over to the installed app. | Yes |
| Mac with Safari | No | Yes |
| Mac with Chrome or Edge | No | Only while the browser is running |
| Windows with Edge | No | Yes |
| Windows with Chrome | No | Only while Chrome is running |
| Firefox | No | Only while Firefox is running |
| Brave | No | Only while Brave is running, and only with Use Google services for push messaging turned on in Brave |
Delivery limits
- A notification about a chat that needs a reply now is sent with high urgency and is dropped if it cannot be delivered within about two minutes, so a device that was offline does not show chats that have already moved on.
- Notifications about chats a Stand-in is answering, and label matches, are kept for up to fifteen minutes.
- Focus, Do Not Disturb, notification settings for the browser or for Stand, and network failures can still keep a notification off the screen.
- On iPhone and iPad a notification has no buttons. Tapping it opens the chat.
- A test verifies a device at that moment. It cannot guarantee that every later notification is delivered or noticed.