Notifications
See every
@mentionon notes and every system notification addressed to you in one list, with a bell in the top nav that badges the unread count.
TL;DR
- What it is — an in-app inbox for your personal notifications — today primarily
@mentionevents from internal notes, with room for more notification types over time.- Who it's for — every role. Each user sees only their own notifications — there's no cross-user admin view.
- Top outcome — never miss a teammate pinging you on a note. Click the notification to land directly in the chat.
At a glance
| Plan tier | All tiers. |
| Who can use it | All authenticated team members. Each user sees only their own notifications. |
| Notification types today | @mention in a note. More types (ticket assignment, campaign completion) are planned. |
| Real-time model | Near-real-time. The bell updates every 30 seconds; the full page updates every minute. For instant alerts even when the tab isn't focused, enable Push Notifications. |
| Top limits | Notifications persist indefinitely. No per-page cap — the list returns all of your notifications. |
| API | Yes — partner API for fetching notifications and unread count. |
How to find it
Bell icon in the top nav. A badge shows the unread count when it's above zero.
Direct URL for the full list: https://lodgestory.com/crm/notifications
Clicking the bell opens a popover preview with up to 8 recent notifications. The footer link View all jumps to the full page.
What is the Notifications Centre?
The problem it solves
Most of the inbox's activity is one-to-one with a guest and the agent working the chat. Internal team activity — mentions, instructions from a colleague, hand-off hints — happens inside the notes attached to a chat. Without a personal inbox, those mentions drown inside each chat's history. The Notifications Centre lifts them into a personal list you can open any time.
What you get
- Bell with badge in the top nav, visible from every CRM page, showing the number of unread notifications.
- Popover preview with the ~8 most recent notifications. Each row is clickable to the chat it refers to.
- Full list page with an All / Unread only filter, icon-coded types, and click-through to the related chat.
- Auto-read on visit — opening the full list marks every returned notification as read.
- Mention parsing — when a note is created,
@nametokens are matched against team members' names; matched users are notified (except the note's creator).
How it's different
- Near-real-time, not instant. The bell refreshes every 30 seconds. For instant pop-up alerts even when you're on another page or another app, enable Push Notifications.
- Per-user, not per-team. Each notification is scoped to one user. No shared team inbox. No admin cross-user view.
- Infrastructure ready for more types. Today only
@mentionevents fire. Ticket assignment, SLA warnings, and campaign completion can be added without disrupting the existing list.
Customer scenarios
- Agent returns from lunch. Bell badge shows 4 unread. Opens the popover, sees three
@mentionnotifications from colleagues on active chats. Clicks the first; lands in the chat thread with the note visible. - Team lead catching up on the shift change. Opens the full page, filters to Unread only, walks through pings made while they were off-shift.
- Power user installing push. Configures Push Notifications so
@mentionsping a desktop notification even when the tab isn't focused. Still uses the bell for the historical list.
How it fits with the rest of Lodgestory
Upstream: notes in Home — specifically the @mention autocomplete in the Notes dialog — are the primary source today. Downstream: click-through takes you to the referenced chat. Parallel: Push Notifications adds an out-of-app delivery channel for the same events and more.
Core concepts
| Term | What it means |
|---|---|
| Notification | One row representing a single event addressed to you (today, a mention in a note). |
| Unread count | The number of notifications you haven't opened yet. Drives the bell's badge. |
| Auto-read | Opening the full list marks every returned notification as read. |
| Mention parsing | Scans notes for @name tokens and matches them against team members' first, last, or full name (case-insensitive). |
Quick Start — clear your unread list in 2 clicks
Step 1 — Click the bell
In the top nav. If the badge shows a number, there's something unread.
Step 2 — Scan the popover preview
Up to 8 recent notifications with icons and truncated content. Click any to jump to the chat.
Step 3 (alternative) — View all
Click View all in the footer to land on the full list. Switch to Unread only; walk the list. Every row returned gets marked read.
How it works
When a teammate writes a note with @YourName, Lodgestory:
- Saves the note.
- Scans the content for
@tokens and matches them against team members' names. - Creates a notification for every matched user (except the author).
Your bell updates on its next refresh (within 30 seconds). Clicking the bell opens the preview; opening the full page marks everything read.
Browser push (separate)
Browser-native push notifications are configured in the Push Notifications settings module. Push sends an operating-system-level alert even when the browser tab isn't focused. The settings module controls which events trigger push (all notifications / new customer messages only / new assignments only / note mentions only / messages + assignments).
Push and the in-app list are independent. Installing push doesn't suppress the in-app list, and disabling push doesn't stop notifications from appearing in the bell.
Features in depth
The bell + badge
Top-right of the nav across every CRM page. Badge is red; it shows the raw count. When the count is zero, no badge.
Popover preview
Clicking the bell opens a small popover with up to ~8 notifications, scrollable. Each row shows a type icon, truncated content, and a relative timestamp. Click a row to navigate to the chat. Footer: View all link.
Full list page
- Layout: single card with a scrollable list.
- Filter: All / Unread only tabs.
- Type icons are colour-coded.
- Auto-read on fetch: every returned row is marked read.
- Empty state: "You have no notifications."
Mention parsing
On note create, Lodgestory scans the content for @ followed by a name token and matches against team members' first, last, or full name (case-insensitive). Matches produce one notification per mentioned user (except the author). Unmatched @names are ignored silently.
The notification payload includes the note's chat, the note content (first 100 characters), and the note category.
Roles and permissions
| Action | All roles |
|---|---|
| See your own notifications | ✓ |
| See someone else's notifications | ✗ (no cross-user admin view) |
| Fire a notification | Indirect — any role can @mention someone in a note they create |
Cross-module workflows
Note mention → jump to chat
Colleague writes @YourName, please double-check this in a chat note. Within 30 seconds your bell badges. You click the notification. The chat opens with the note visible in the right panel. You reply in the chat or respond via a new note back to the colleague.
Modules involved: Home (Notes) → Notifications Centre → Home.
Limits a user will run into
| Limit | Value |
|---|---|
| Retention | Indefinite — no auto-purge |
| Per-fetch limit | None — list returns everything you have |
| Unread badge | Integer, no cap |
Errors & FAQ
Few distinct errors — the surface is small.
| You see | Likely reason | What to do |
|---|---|---|
| Failed to fetch notifications | Network hiccup or session | Reload; retry on the next poll |
Frequently asked
Why is my unread count still showing after I clicked the bell?
The popover shows a preview but doesn't mark everything read. Opening the full page does. Or click individual rows — navigating through the chat re-fetches and marks them read.
Why doesn't the bell update instantly when someone mentions me?
The bell polls every 30 seconds. For instant delivery install Push Notifications.
Can I see notifications for things other than mentions?
Not today. Mentions are the only event type that currently fires. Over time this module is expected to expand — the infrastructure is ready.
Why can't admins see a team member's notifications?
By design — notifications are personal. Each user's stream is private.
Is there a "mark as unread" action?
Not in the current UI. Once read, a row stays read.
Related modules & next steps
- Push Notifications — browser-push delivery for the same events (and more).
- Home (Unified Inbox) — where
@mentionsoriginate (the Notes dialog). - Team Members — the user list the mention parser matches against.
Updated about 4 hours ago