Set Up Push Notifications
Most hotels only need browser alerts and one channel. This takes about 5 minutes.
This guide helps you manage push notifications for your current property. The page has three layers: property level, user level, and browser level. Property level decides whether check-in and checkout alerts can send at all. User level categories decide which allowed alerts reach this account and paired AVA devices. Browser level controls this browser and its subscription. Paired Vouch AVA Alarm devices use the same user-level categories. Verified native devices can stay linked across every merchant you can access. The page uses collapsed categories, accordion cards, and one sticky save button. On mobile, setup instructions stay below each form, and the save bar stays clear of the last field. You can route alerts to Slack, Google Chat, Telegram, or Zapier. AVA also sends check-in milestone alerts and room-access ready alerts. Shared channel alerts include your hotel name in the message details. AVA now adds the same emoji prefix to matching notification titles everywhere. Expand Check-in and Check-out to fine-tune alert subtypes. Property, user, and browser changes all wait for Save notification settings. If you disable a parent gate, its child controls stay off until you save. AVA remembers each child choice and restores it when the parent turns back on. When a user-level or browser-level save succeeds, AVA shows the standard Settings saved successfully! toast once after the batch finishes. You do not see that toast if permission is denied or any requested save fails.
If you use AVA Portal, browser push prompts are skipped on mobile. The native shell registers the device after sign-in. It can receive incoming video calls and check-in or checkout alerts allowed by the property policy. Browser alerts still work in desktop browsers.
Streamliner check-in and checkout alerts reach the AVA mobile app as gentle banners. They also update the in-app bell on Android and iPhone. These alerts follow the property policy above and the user categories below. They still reach linked, registered devices.
Use this page for browser alerts, property-level check-in and checkout delivery, and user categories. For paired alarm devices, use Set Up Vouch AVA Alarm. You can also add or rename a device name there.
If you manage several hotels, one verified AVA installation can stay linked across them. That lets your native notification preferences apply without switching hotels one by one.
When you encode a keycard, the banner now says the room is ready. It no longer reuses the Key retrieved wording.
This page follows the hotel you selected in the switcher. Browser alerts and test notifications stay tied to that property. External channel alerts use merchant-wide settings for that property.
When you open Open in Streamliner from Slack, Google Chat, Telegram, or Zapier, AVA keeps the correct hotel in the link. That should take you to the same property that received the alert.
AVA refreshes your browser subscription when you return, reconnect, or reload after a browser update. Repeated check-in, checkout, and housekeeping alerts keep separate banners.
Where to Find It
Settings → Customizations → Push NotificationsQuick Reference
| Setting | What It Controls | Who It Affects |
|---|---|---|
| Property level: allow check-in/check-out alerts | Turns check-in and checkout delivery on or off for this property | Everyone at this property |
| User level: My browser push notifications | Chooses which allowed alerts reach this account and paired AVA devices | Staff on this device |
| Browser level: browser notifications | Lets this browser show Streamliner alerts | Staff on this device |
| Browser subscription sync | Refreshes your push subscription when you click Save notification settings | Staff on this device |
| Save confirmation | Shows the standard success toast after a successful user-level or browser-level save | Staff editing notification settings |
| AVA Portal mobile shell | Uses the native shell for incoming video calls and Streamliner bell alerts | Staff using AVA Portal |
| User-level AVA device delivery | Uses the same category choices on paired AVA devices across all accessible merchants | Staff using this account |
| External channel notifications | Merchant-wide routing for Slack, Google Chat, Telegram, or Zapier | Teams in those channels |
| Notification titles | Shared emoji prefixes across browser, settings, and Telegram alerts | Staff who read alerts |
| Operational alert tags | Keeps rapid check-in, checkout, and housekeeping banners separate | Staff who receive fast updates |
| Vouch AVA Alarm Integration | Sends incoming video-call alarms to paired Android and iOS devices and stores optional device names | Staff handling video calls |
| Channel integrations | Accordion cards for each outbound channel | Hotel admins |
| Save notification settings | Saves property, user, browser, and channel changes together | Anyone editing settings |
[Update] - 2026-05-16
- Added optional merchant-specific names for Vouch AVA Alarm devices.
- The connected devices table shows the name beside the alarm code when you add one.
- You can rename the label later from the alarm edit modal.
Before You Start
Confirm these basics:
- You are signed in to the correct property
- Your browser allows notifications for this site
- You have the correct webhook URL (Slack/Google Chat/Zapier)
- You have the Telegram bot token and chat ID, if you use Telegram
- You have permission to update settings if you are changing external channels
Turn On Browser Push Notifications
-
Under Browser level: browser notifications, turn on the toggle
-
If your browser asks, click Allow
✓ You should see the status change to Enabled
-
Choose the alerts you want under My browser push notifications
-
Click Save notification settings
This toggle is browser-scoped. It applies only to the current browser and property. User choices stay saved separately, even when a parent gate is off.
Choose Which Browser Alerts You Receive
Use My browser push notifications when you only want to change alerts for your own browser.
- Go to Settings → Customizations → Push Notifications
- Find My browser push notifications
- Turn categories on or off
- For Check-in and Check-out, expand the category and choose specific alert types
- Click Save notification settings
These settings do not change Slack, Google Chat, Telegram, or Zapier. Use External channel notifications for those channels. Turning off a parent category turns off all of its subtypes too. User categories also apply to paired AVA devices when the property allows the alert. If a parent category is off, child choices stay saved but appear off until you re-enable the parent. Use Save notification settings to apply the full hierarchy together.
Send a Test Browser Notification
-
In Push Notifications, scroll to Test Notification
-
Click Send Test Notification
✓ A test alert should appear on your device within a few seconds
Each test notification is sent as a fresh alert. If you click Send Test Notification again, you should see a new notification.
Your browser push notifications follow your Streamliner language on this device. If you change your language later, turn push notifications off and on to update it.
Choose Which External Channel Alerts Are Sent
Use External channel notifications when you want to control alerts sent to Slack, Google Chat, Telegram, or Zapier.
- Go to Settings → Customizations → Push Notifications
- Find External channel notifications
- Turn categories on or off
- For Check-in and Check-out, expand the category and turn specific alert types on or off
- Click Save notification settings
External channel settings apply to the whole property. If you turn off Checkout started, it stops for all connected external channels.
Property, user, browser, and external channel changes all wait for Save notification settings. Nothing applies until you click the save button.
You need settings permission to change External channel notifications. You can still change your own browser alerts without this permission.
Open Channel Integrations
Telegram setup happens in the AVA portal. Use these steps when you add the bot token and chat ID.
Telegram uses the title it receives from Streamliner. That keeps the same emoji prefix in browser alerts and external channels.
Each integration opens as its own accordion card. Use it when you need to configure one channel at a time.
Single Webhook (Simple)
Send all enabled categories to one channel.
-
Select your platform (e.g., Slack)
-
Paste the Webhook URL
-
Turn on Enable Integration
✓ You should see the integration status show Enabled
Category-Specific Webhooks (Advanced)
Route alerts to different channels (e.g., Alerts → #it-support).
- Turn on Use specific webhooks for different categories
- Enter a URL for each category
- Leave a category blank to use the default URL
Telegram
Set up Telegram with a hotel-owned bot and one or more destination chats.
- Select Telegram
- Paste the Bot token
- Enter the Chat ID
- Choose Same chat for all notifications or Different chats per category
- If needed, add category overrides under Category-Specific Chats
- Turn on Enable Telegram
- Click Save notification settings
Saved bot tokens show as *****.
Click Edit token only when you want to replace the existing token.
Use @channelusername for public chats.
Use the numeric chat ID for private groups or channels.
If the chat is private, Telegram shows the number in getUpdates.
In Same chat for all notifications, all alerts use the default Chat ID. In Different chats per category, categories without overrides still use the default Chat ID.
Telegram makes public https:// links clickable.
Local, Docker, or internal URLs stay as plain text so delivery keeps working.
Supported Notification Categories
| Category | Trigger |
|---|---|
| Check-in | Guest check-in started, completed, failed, or moved through key steps |
| Checkout | Guest checkout started, bill viewed, paid, completed, or failed |
| Housekeeping | Room status updates (Clean/Dirty/Inspected), identified by room when available |
| Keycard Heartbeat | Encoder connection failures and recovery notices |
| Alert | System errors, payment failures, or ID verification reviews |
| Generic | General system notifications |
Smart-lock PINs and locker codes use Room access ready under Check-in. You do not need a new notification category.
Check-in and Checkout Alert Types
| Category | Alert Type | Example |
|---|---|---|
| Check-in | Check-in started | A guest starts online check-in |
| Check-in | Document uploaded | A guest uploads an identity document |
| Check-in | Identity verified | A guest passes identity verification |
| Check-in | Room assigned | A room is assigned during check-in |
| Check-in | Payment completed | A payment or deposit step is completed |
| Check-in | Keycard encoded | A physical keycard is ready and the room is ready |
| Check-in | Key retrieved | A digital key is ready |
| Check-in | Room access ready | A smart-lock PIN or locker code is ready |
| Check-in | Check-in completed / Check-in issue | Check-in completes, or a blocked lookup shows the issue and reason |
| Checkout | Checkout started | A guest starts checkout |
| Checkout | Bill viewed / Bill settled | A guest views or settles their bill |
| Checkout | Checkout payment completed | Checkout payment is completed |
| Checkout | Checkout completed / Checkout issue | Checkout is completed or fails |
If a door-lock issue is fixed on a later retry, AVA sends the follow-up progress alert. You may see Key retrieved or Check-in completed after the earlier Check-in issue alert.
When AVA sends a guest to front-desk review during lookup, it sends a Check-in issue alert.
This includes kiosk, balance, billing, zero-night, and long-stay blocks.
The alert title identifies the failed step, such as Check-in issue at Entry.
Its message explains the reservation block in staff-friendly language.
Google Chat cards show Status: FAILED, rather than the step's in_progress status.
Successful arrivals at Entry still use the normal arrival alert.
Open Command Center → View Details to review the failed lookup event.
When staff complete a manual check-out, AVA sends the same Check-out alerts. If delivery to one channel fails, the check-out still finishes.
If a keycard encoder goes offline and then recovers soon after, AVA sends each event separately. That lets you see both the failure and the recovery in your notification center. Google Chat and other staff alerts include the specific encoder failure reason, so you can troubleshoot faster. For example, AVA distinguishes No card detected, Unsupported card type, and Card could not be read. Use Keycard Encoder Troubleshooting for the matching fix.
Troubleshooting
Push notifications stay off after you turned them off
What you see: You turned off the browser notifications toggle and it does not turn back on by itself.
Fix:
- Go to Settings → Customizations → Push Notifications
- Turn the browser notifications toggle back on
- Click Save notification settings
The toggle is saved per property and device. It stays off until you turn it back on.
Push notifications turn back on after refresh
What you see: You disable push notifications, refresh, and they appear enabled again.
Fix:
- Confirm you are in the correct property
- Turn the browser notifications toggle off again
- Keep this browser open for a few seconds so the change saves
If site data is cleared or you switch properties, you may need to disable it again.
No browser notifications appear
What you see: The toggle is enabled, but nothing appears.
Fix:
- Check your browser notification permission for this site
- Click Send Test Notification
- Make sure you are logged in on the same device
AVA may need a moment to refresh your browser subscription after you return or reconnect. If the browser changed its push subscription, the next visible tab usually restores it.
Check-in and checkout alerts do not send
What you see: Browser alerts work, but check-in or checkout alerts never arrive.
Fix:
- Go to Settings → Customizations → Push Notifications
- Turn on Property level: allow check-in/check-out alerts
- Confirm the needed items stay on under My browser push notifications
- If you use paired AVA devices, confirm the device is connected in Set Up Vouch AVA Alarm
The property-level control blocks check-in and checkout delivery for everyone at that property. User categories only work after the property allows those alerts. If a parent gate is off, child controls can look off even when their saved choice is still there.
Child notifications look off after you disable a parent
What you see: You turn off a parent gate, and the child categories also appear off.
Fix:
- Turn the parent gate back on
- Check the child categories you want
- Click Save notification settings
AVA shows child controls as effectively off when a parent gate blocks delivery. Your saved child choices remain available after you re-enable the parent.
Back-to-back alerts collapse into one banner
What you see: Several guest events happen quickly, but you only see one browser alert.
Fix:
- Keep the browser notifications toggle turned on
- Wait a few seconds for the page to resync
- Check the browser notification center for the missing alert
- Click Send Test Notification
AVA now queues push messages that arrive close together. Check-in, checkout, and housekeeping alerts also keep unique tags.
Notifications show the wrong language
What you see: Alerts appear in a different language than your Streamliner screen.
Fix:
- Change your Streamliner language using the language dropdown, for example, EN.
- Go to Settings → Customizations → Push Notifications
- Turn the browser notifications toggle off, then on again
- Click Save notification settings
- Click Send Test Notification
Each device can have its own language for notifications.
Webhook messages do not show up
What you see: Browser alerts work, but Slack/Chat has no messages.
Fix:
- Confirm the full URL starts with
https:// - Re-enable Enable Integration
- Try a test message in a new channel
Telegram still sends an alert you turned off
What you see: Your browser does not receive Checkout started, but Telegram still does.
Fix:
- Go to Settings → Customizations → Push Notifications
- Find External channel notifications
- Under Check-out, turn off Checkout started
- Click Save notification settings
Browser alerts and external channel alerts have separate settings. Changing My browser push notifications only affects your browser.
Telegram token still shows as stars
What you see: You open Telegram settings and see ***** in the token field.
Fix:
- Click Edit token
- Paste the new bot token
- Click Save notification settings
AVA keeps the stored token hidden.
Saving ***** keeps the existing token instead of replacing it.
Telegram messages go to the wrong chat
What you see: Telegram alerts arrive, but they reach the wrong group or channel.
Fix:
- Open Settings → Customizations → Push Notifications
- Check the Telegram Routing setting
- Confirm the Chat ID is correct
- Add or update the matching category override
- Click Save notification settings
Telegram uses the default chat unless a category override exists.
Telegram links are not clickable
What you see: A Telegram alert shows a URL, but it is not a clickable link.
Fix:
- Check whether the URL is public and starts with
https:// - Use the plain URL for internal or Docker addresses
- Confirm the message still sends successfully
Telegram only creates clickable links for public HTTPS addresses. Internal URLs are kept as plain text to avoid delivery errors.
You cannot save external channel settings
What you see: Browser alert settings save, but external channel settings show an error.
Fix:
- Ask an admin to confirm you have settings permission
- Refresh the page
- Try changing External channel notifications again
External channel link opens the wrong hotel
What you see: You tap Open in Streamliner from Slack, Google Chat, Telegram, or Zapier, and AVA opens a different hotel.
Fix:
- Sign in to AVA with the right account
- Return to the original notification message
- Refresh AVA if you switched hotels in another tab
External channel links include the hotel from the alert. An old browser session can still point to a different hotel.
Still Stuck?
Contact success@vouch-technologies.com if:
- ❌ Notifications are still missing after the steps above
- ❌ You see repeated error banners in settings
- ❌ Issues persist for more than 30 minutes
Helpful to include:
- Screenshot of the settings page
- The property name
- Time the issue started
- Which channel is affected, such as Telegram or Slack