Push Notifications

Get pinged on your laptop and phone the moment a guest messages — even when Lodgestory isn't open.

TL;DR

• What it is — browser and device push notifications for your team, tunable per device, so you're alerted about new messages, assignments, and mentions wherever you're working.
• Who it's for — every team member, configured personally on each device they use.
• Top outcome — reply to a guest within seconds of their message, even if the Lodgestory tab isn't focused — or if your laptop is asleep and you're on your phone.

At a glance

How to find it

Breadcrumb: Settings → Push Notifications.

Direct URL: https://app.lodgestory.com/crm/settings/push-notifications

[SCREENSHOT: push-notifications-nav.png — Settings sidebar with Push Notifications highlighted]

What is Push Notifications?

The problem it solves

Your team loses context when the Lodgestory tab isn't focused. A guest replies on WhatsApp; an admin assigns a chat; a colleague mentions them in a note — and they only notice when they happen to open the tab. The guest has been waiting; the chat has been sitting; the note has been ignored.

Push Notifications fires a native alert the moment something relevant lands — on your laptop, your phone, or wherever you're logged in — so your team responds within seconds without keeping Lodgestory in front of them.

The in-app Notifications Centre is complementary: it's the historical list inside the app. Push extends that to out-of-app delivery. The two are independent — having push on doesn't silence the in-app list, and vice versa.

What you get

• Native browser alerts. Chrome, Firefox, Safari, Edge, Samsung Internet, and Opera all show a native notification with the sender, channel, and a preview of the message. Click it and the conversation opens in Lodgestory.
• Five notification presets per device — pick the one that matches how you work:
  • All notifications — everything.
  • Only new customer messages — just inbound messages from guests.
  • Only new assignments — just when a chat or ticket is assigned to you.
  • Only note mentions — just when a colleague @mentions you in a note.
  • New customer messages and new assignments — the common middle option: the two that usually matter most.
• Per-device preferences. The same person can have different preferences on different devices. Your laptop might get everything; your phone might only light up for assignments. Set each device independently.
• Click-to-open. Click a notification and Lodgestory opens directly on the right conversation — or the right ticket — rather than the home page.
• Clean device list. The settings page shows every device you've subscribed from, with its browser icon, device type, current preset, and a per-device remove action.
• Automatic cleanup. If a device becomes unreachable — for example you uninstall the browser or clear site data — Lodgestory stops pinging it automatically. No stale devices in your list wasting alerts.
• Delivery history. See a log of recent push attempts for your user, including whether each one was delivered and why any failed ones failed.

How it's different

• Independent from in-app notifications. Most CRMs bundle in-app and push into one toggle. Lodgestory keeps them separate, so you can have a loud inbox badge but a quiet laptop — or vice versa — whichever suits your day.
• Five curated presets, not forty toggles. Big notification settings pages are famously unreadable. Lodgestory's five presets cover the realistic combinations cleanly.
• Per-device, not per-user. Most tools let you pick one preference for your account. Lodgestory lets your laptop get everything during work hours and your phone stay quiet unless you personally own something. Common pattern: "laptop loud, phone quiet."
• Self-healing device list. Devices that disappear (uninstalled browser, cleared cookies, expired subscription) are automatically marked as unreachable and skipped. No manual cleanup, no wasted alerts.

Customer scenarios

• Team member at their desk, tab unfocused. A guest replies on WhatsApp. A native notification pops up on the laptop: "Acme Villas — New message from Priya Sharma: 'Is the villa pet-friendly?'". The team member clicks. Lodgestory focuses the tab and opens that conversation. Total elapsed: about two seconds.
• Laptop loud, phone quiet. A team lead subscribes their laptop to All notifications — they want to see everything during work hours. The same user subscribes their phone to Only new assignments — off-hours, only things they personally own.
• Automatic cleanup. Someone uninstalls Chrome on an old laptop. The next time Lodgestory tries to send a push there, the device returns an "unreachable" signal. Lodgestory marks it unreachable and stops pinging it. The next time they log in on a new browser and enable push, a fresh device is added.

How it fits with the rest of Lodgestory

• Notifications Centre — the in-app counterpart. Fires on the same events; stores its list inside the app and delivers through the bell badge.
• Home / Unified Inbox — the source of new-message and assignment events that trigger your pushes.
• Team Members — your push subscriptions are tied to your user. Moving to a different workspace doesn't carry device subscriptions across.

Core concepts

Quick Start — enable push in three clicks

Step 1 — Open Push Notifications

Settings → Push Notifications.

[SCREENSHOT: push-qs-1-page.png]

Step 2 — Grant permission

If the page asks for permission, click Request Permission. Your browser shows a native prompt — choose Allow.

[SCREENSHOT: push-qs-2-browser-prompt.png]

Step 3 — Pick a preset and enable

Select one of the five presets — most team members start with All notifications or New customer messages and new assignments. Click Enable Notifications.

[SCREENSHOT: push-qs-3-enable.png]

Lodgestory sets up the subscription for this browser on this device. You're live.

Step 4 — (Optional) Set up a second device

Open the same settings page on a different browser or device (for example your phone). Enable push there with a different preset — maybe Only new assignments — so each device pings you only for what matters there.

What's next

• Open Home and send a test message from your personal phone to see a push arrive.
• Tweak presets over time. If your laptop is too noisy, drop it to New customer messages and new assignments. If your phone is too quiet, bump it up.

How it works

Push works through the browser's native notification system, so alerts look and behave exactly like alerts from any other website or app.

1. You open Push Notifications settings and click Request Permission. Your browser shows its native prompt.
2. You pick a preset — one of the five — and click Enable Notifications.
3. Your browser installs a small background helper that listens for pushes addressed to this device.
4. Lodgestory records this device as a subscription under your account with the preset you chose.
5. When a relevant event happens — a new customer message, an assignment, a mention — Lodgestory sends a push to every device subscribed to a matching preset.
6. Your browser shows the native notification. Click it and Lodgestory opens directly on the right conversation or ticket.
7. If the device becomes unreachable (uninstalled browser, cleared data), Lodgestory marks it so and stops sending it pushes. No cleanup work for you.

Features in depth

The settings page

Top-level: a permission card that tells you the state of browser permission. If it's default, a Request Permission button. If it's denied, a short guide to re-enabling it in your browser settings. If it's granted, the enable toggle and the preset selector become active.

Below: your current-device card — the subscription status on this browser — and an all-devices list showing every device you've subscribed from, with per-device removal.

Five presets

Multi-device support

Each browser on each device holds its own subscription with its own preset. The same user can run All notifications on their laptop and Only new assignments on their phone. Your settings page on any given browser shows your current device in detail, plus an all-devices list for everything else you're subscribed from.

Each row in the all-devices list shows the browser, device type (desktop or mobile), current preset, and status. One click removes a subscription.

Click-to-open

Each push carries the context needed to open the right surface in Lodgestory:

• New customer message → opens the conversation in Home.
• Chat or ticket assignment → opens the assigned item.
• Note mention → opens the conversation where the note was posted.
• Custom notifications → can include a target URL that Lodgestory opens directly.

If Lodgestory is already open in a browser tab, the existing tab focuses. If not, a new tab opens.

Automatic cleanup

When a device becomes unreachable — a permanently invalid endpoint signal from the browser's push service — Lodgestory marks that subscription unreachable the first time it fails. From then on, that device is skipped. You don't get notifications intended for a phone you no longer use.

Delivery history

The settings page includes a history view with recent push attempts for your user, showing:

• The payload (what the notification said).
• Whether it was delivered.
• Any failure details.

Useful for answering "did I actually get pinged about that?"

Roles and permissions

Push Notifications is configured personally per team member. There are no role walls here — every authenticated member of your workspace can subscribe their own devices and pick their own presets.

Connections

• Notifications Centre — the in-app counterpart. Fires on the same events but stores them inside the app.
• Home / Unified Inbox — source of new-message and chat-assignment events that trigger your pushes.
• Tickets — source of ticket-assignment events.
• Notes on conversations — source of @mention events.

Limits a user will run into

Errors and FAQ

You might see

• "Permission not granted" — your browser has denied notification permission. Open your browser's notification settings, unblock Lodgestory, and retry.
• "Browser unsupported" — your browser doesn't support the push APIs Lodgestory uses. Try Chrome, Firefox, Safari, or Edge.
• "Couldn't subscribe" — check your network connection and try again. If the problem persists, refresh the page or sign out and back in.
• Silent non-delivery after subscribing — your device may have become unreachable since you subscribed. Disable and re-enable to reset.

FAQ

Why doesn't clicking a notification open the exact chat?
Standard notifications from Lodgestory carry the context to open the right conversation. Notifications from custom integrations that don't include routing details fall back to the Home inbox.

I enabled push but haven't received anything in hours.
Walk through: is browser permission still granted? Is this device listed as subscribed on the settings page? Does your preset match the events you'd expect? If you picked Only note mentions and nobody has mentioned you, you won't see pushes.

How many devices can I subscribe from?
As many as you use. Each browser on each device gets its own subscription with its own preset. Manage them from the all-devices list.

Can admins push announcements to everyone at once?
Lodgestory's core push events are automatic (new messages, assignments, mentions). Custom workspace-wide announcements are available through the partner API for teams that need them.

Can I pause pushes temporarily without losing my subscription?
No pause toggle today. Either remove the subscription and re-subscribe when you're back, or switch to a quieter preset for the day (for example Only note mentions) and switch back later.

Why is one of my devices marked as unreachable?
It returned a permanent-fail signal on the last push — typically because the browser was uninstalled, its data was cleared, or the subscription expired. Re-subscribe on that browser to get a fresh subscription.

What if I change my browser's default notification style?
Lodgestory uses native browser notifications. Whatever style and behaviour your browser applies (banner, list, do-not-disturb rules) applies equally to Lodgestory pushes.

Is my notification content secure?
The push content carries the sender name and a short preview of the message. If your device's lock screen shows notification content by default, anyone with physical access to the device could see the preview. Use your OS and browser settings to hide notification content on the lock screen if that's a concern.

API

Push Notifications is available via the Lodgestory partner API for organisations that want to send custom pushes or manage subscriptions programmatically. Ask your Lodgestory point of contact for credentials and the current reference; endpoints cover subscription management, sending immediate pushes, firing events onto the internal event bus, and reading delivery history.

Changelog

• April 2026 — General availability. Five-preset selector, per-device subscriptions with independent presets, automatic cleanup of unreachable devices, delivery history on the settings page, click-to-open on the right surface.

Related modules and next steps

• Notifications Centre — in-app counterpart; works alongside push.
• Home / Unified Inbox — source of most push-triggering events.
• Team Members — subscriptions are tied to the user managed here.