Skip to main content

Notification triage

Ask AI Chat “Where do I open the Dashboard bell and the full Notifications inbox at /notifications to triage alerts — use Unread and Mark all as read (English labels — Dashboard, Notifications, bell, All, Unread, Read, Mark all as read — Common Workflows Notification triage — product navigation only, no account data)?” — then open the Dashboard bell and bookmark /notifications (ai-chat-product-context-notification-triage-reply.png, ai-chat-product-context-notification-triage-flow.mp4). The assistant typically points at the Dashboard header bell and /notifications (it may say left menu — Notifications is not a sidebar item; use the bookmark or View all from the bell). Same grounding external MCP clients get from get-vivin-context-overview (or get-vivin-context-operations). Distinct from collections on Handling a Late Payment and from the broader Common Workflows hub product maps.

AI Assistant — where to open the Dashboard bell and /notifications for alert triage

Walkthrough: ask AI Assistant where to open the Dashboard bell and full /notifications inbox for triage, then open the Dashboard bell slide-over and the Unread filter on /notifications.
First-time workspace setup

Use after go-live when alerts accumulate — there is no setup sequence step dedicated to /notifications; bookmark the full inbox once Getting Started — Recommended Setup Sequence steps 1–15 are complete. First-booking alerts on new inventory: finish Onboarding a New Property — Step 7 before bulk-clearing go-live pings. Lockout catch-up: Getting Started — Lockout catch-up after password recovery.

Finding your way in this guide

Desktop quick pass: Step 1 — Quick scan on Dashboard. Full inbox: Step 2 — Open the full inbox → filters in Step 3 → row-click in Step 4. Clear unread: Step 5; defects: Step 6 — Escalate when triage is blocked. Surface choice: When to use which surface. Habit-specific shortcuts live under Related below.

Use this workflow after busy booking or payment days when you need to clear unread in-app alerts and jump to the related booking, tenant, or listing without hunting through modules manually. It centers on the Notifications module at /notifications, with the desktop Dashboard bell for a quick first pass.

Pair with other workflows

Payment alerts often continue in Handling a Late Payment — Step 1 — start from Notifications — Payment overdue alerts when a Payments category row row-clicks into a booking; after navigation, confirm balances on Finance → Overview using Glossary — Finance income status (In debt drill-down) and Glossary — Finance Debt Aging (Top debtors / overdue buckets — FAQ — Bookings that owe money), or compare Dashboard Total Debt with Finance > KPI strip (Uncovered Debt). During month-end, pair Step 4 row-click triage with Portfolio KPI review — Dashboard Total Debt subtitle before you change rates in Sales — and poll AI usage API during Portfolio KPI review — Step 7 when assistant or utility-bill extraction volume should explain operational cost alongside debt reconciliation. Pending manual in-payment alerts need Glossary — Pending manual in-payment (Finance) on Transactions, not the Overview Manual Payments KPI alone. Arrival and departure alerts pair with Managing a Check-in and Managing a Check-out.

Prerequisites
  • An active Vivin account with access to the management frontend
  • Bookmark /notifications if you triage the full inbox regularly — there is no Notifications item in the left sidebar

Step 1 — Quick scan on Dashboard (desktop)​

Pair with other Notification triage steps

Bell quick scan pairs with Dashboard bell slide-over, Inbox module (General / Inbox sub-tabs), Common Workflows — WhatsApp per-booking messaging (New WhatsApp message from … → bell Inbox), and get-upcoming-move-ins on Landlord MCP. Downstream: Step 2 when you need search or row-click navigation — pair Common Workflows — Notification row-click navigation on /notifications.

On desktop, open the Dashboard (/). The bell in the page header shows an unread badge when applicable.

  1. Click the bell to open the Notifications slide-over from the right.
  2. Check the General sub-tab first for payment, ticket, and booking alerts (when your build includes Inbox sub-tabs — see Inbox module). Switch to Inbox for inbound WhatsApp / email message pings; summaries read New WhatsApp message from … or New email from … (tenant name when Vivin can resolve the contact, otherwise a clean +{digits} phone — never a raw WhatsApp JID). Clicking a row with a deep link opens the conversation directly — from the thread, click the tenant name in the header to open the Tenant sidebar without leaving Inbox (screenshot). If Inbox is greyed out, the account tenant chatbot is not enabled yet — triage General only and contact Vivin or use Bookings → Communication after enablement (Inbox — Chatbot gating; FAQ — WhatsApp and email per booking).

Dashboard bell — Inbox sub-tab with WhatsApp / email channel icons and unread badge on the tab

  1. Scroll the list — the panel loads more rows as you approach the bottom (skeleton rows appear while the next batch fetches).
  2. Click a General row without a link to read Notification detail inside the panel (summary, body, created time). Unread rows are marked read when you open them (no success toast on row click alone). The header title switches to Notification Detail, the General / Inbox sub-tabs hide until you use the back arrow (←) beside the title to return to the list for the same sub-tab.
  3. Use Mark all as read when you have scanned the active sub-tab and want to clear its unread state without opening every row. Success and failure both surface as toasts on the full page and in the bell slide-over — if unread badges remain after clicking, retry (see Glossary — Notification read actions).

Dashboard — notifications bell slide-over on Notification detail with Summary, Content, and Created at

Dashboard — notifications bell slide-over open with scrollable history and Mark all as read

What the bell does not do

The Dashboard slide-over has no search and no All / Unread / Read pills. General rows without a backend link open in-panel detail only — they do not navigate to Bookings, Tenants, or Listings from the bell. Inbox rows with a link do jump to the conversation. Use the full /notifications page when you need filters, search, or one-click entity navigation from payment and ticket alerts.

The bell is not shown on narrow (mobile) viewports and is not added to other modules’ page headers — open /notifications directly on mobile or when you are already deep in another module.

External automation on bell quick scan

Account-scoped Landlord MCP get-upcoming-move-ins surfaces the same arrival-week rows many General alerts reference — pair with list-tickets when ticket-category pings dominate the bell list before you row-click in Step 4. External clients cannot read in-app notification rows or Mark all as read from MCP; operators finish triage on the bell or /notifications.

Step 2 — Open the full inbox​

Pair with other Notification triage steps

Full inbox pairs with /notifications search and All / Unread / Read pills, and get-booking-summary on Landlord MCP for portfolio context. Upstream: Step 1 (bell scan). Downstream: Step 3 (filter slice).

Go to platform.vivin.app/notifications (or your bookmarked /notifications URL).

The full page adds:

  • Search — matches summary and body text (debounced; pause briefly after typing)
  • All / Unread / Read filter pills
  • Mark all as read for the current filter + search slice
  • A totals line (matching count and unread count)
  • Infinite scroll with an explicit End of list marker when every matching row is loaded

Notifications module — full history with All filter

External automation before opening /notifications

Account-scoped Landlord MCP get-booking-summary returns active and upcoming booking counts when external assistants need portfolio context before an operator opens the full inbox — MCP has no /notifications list tool; unread read-state changes remain operator UI only (Step 5).

Step 3 — Narrow to what still needs attention​

Pair with other Notification triage steps

Inbox narrowing pairs with /notifications Unread pill and search, and list-bookings / list-tenants on Landlord MCP when external clients match names before row-click. Upstream: Step 2. Downstream: Step 4 (entity navigation).

  1. Click Unread to show only items you have not reviewed yet.

Notifications module — Unread filter

  1. Optionally type in search to find a tenant name, booking reference, or keyword from the message body.

Notifications module — All filter with search text narrowing the list

  1. When nothing matches, the list shows No notifications found for the selected filters. — switch pills or clear search before assuming data is missing.

Notifications module — empty state after search with no matching rows

  1. After you have handled unread items, switch to Read to confirm history or audit what you already cleared.

Notifications module — Read filter with read-only rows and totals line

External automation when search narrows the slice

Account-scoped Landlord MCP list-bookings helps external clients match tenant names or unit codes you type in search — pair results with get-booking before row-click navigation in Step 4. When search text looks like a person name rather than a room code, list-tenants / get-tenant resolve tenantId targets the same way /notifications row-click uses bookingId — then get-tenant-bookings narrows to the active stay. For Payments-category keywords (amounts, “overdue”, “received”), list-payments surfaces ledger rows you can cross-check with get-payment before you open the booking in Step 4 — external clients cannot change Unread / Read pills from MCP; operators finish read-state cleanup on /notifications or the Dashboard bell.

Step 4 — Open the related booking, tenant, or listing​

Pair with other Notification triage steps

Row-click navigation pairs with Common Workflows — Payment alert to receivables triage (Step 4 → Finance debt receivables triage / Handling a Late Payment — Steps 1–3 → Step 5; notifications-row-navigate-to-booking-detail.png, notifications-row-navigation-flow.mp4, finance-overview-income-chart-debt-aging.png, finance-overview-debt-aging-walkthrough-flow.mp4) and Common Workflows — Confirmation alert triage on Upcoming stays (Step 4 → Processing a New Booking — Step 5b / Step 6 → Confirmation to check-in handoff; bookings-detail-transactions-approve-payment-modal.png, booking-lifecycle-status-tabs-flow.mp4), Common Workflows — Handling a Late Payment collections hub (alert row-click → confirm balance → Handling a Late Payment — Step 1 / Step 3), Glossary — Notification row navigation, FAQ — Handling a Late Payment hub, Handling a Late Payment — Step 1 (Payments alerts), and get-booking / list-payments on Landlord MCP. Upstream: Step 3. Downstream: Step 5 after you act on each row.

On the full Notifications page, clicking a row does more than update read status when the platform attached a navigation target:

  1. If the row is still Unread, it is marked read in the background.
  2. The app navigates using the first match: backend link, then bookingId, tenantId, listingId, or propertyId.

Notifications module — inbox row ready to open the related booking

Example outcome after a payment-related notification:

Bookings — detail opened after clicking a payment notification row on /notifications

Walkthrough: on /notifications, click a row with a bookingId target — the app marks it read and opens the booking detail sidebar.

From the opened booking, review Payment Plan or Contract Values for the charge behind the alert. When the shortfall is a security deposit (not rent schedule lines), also open the Deposit tab — an amber Partially paid badge means the deposit is short (Partial Paid on depositStatus — see Glossary — Deposit lifecycle status); portfolio triage uses Finance → Deposits — Partial paid lifecycle card — see FAQ — Partly collected security deposit and Handling a Late Payment — Step 1 (deposit vs rent Partial Paid distinction).

External automation on payment alerts

Account-scoped Landlord MCP clients can triage the same Payments category rows you open from /notifications — get-booking and list-payments / get-payment for ledger context after row-click navigation, create-manual-payment-in when an external assistant records a bank transfer that still needs Approve payments, and list-bookings when several alerts reference the same tenant. Booking-scoped Tenant MCP get-payment-info returns the tenant-facing schedule for one reservation — use it when the alert followed a WhatsApp or email thread (Inbox module) rather than a portfolio-wide collections pass. list-bookings-by-email resolves bookingId when the tenant name in search matches multiple stays; get-tenant-info confirms profile fields before you mirror segment filters on Finance → Contract Values; notify-landlord escalates when the tenant disputes a balance external automation cannot clear — operators still finish approval and read-state cleanup in Step 5.

Booking sidebar tab refresh

Inside the booking sidebar, Communication and Tickets load on their own — use Refresh (Communication) or Retry (Tickets) without leaving the inbox workflow. Other tabs stay available. When the whole Bookings or /notifications list needs a refresh, that is a Directory list refresh whole-module Retry — not tab-scoped recovery. See Common Workflows — Booking sidebar tab refresh, FAQ — Communication or Tickets won't open, and Glossary — Booking detail sidebar tab refresh.

Finance Overview — Manual Payments KPI beside Total Debt (monthly manual total; triage pending rows on Transactions)

Finance Transactions — All card with amber Pending chip active and filtered ledger rows

Booking detail Transactions — Approve payment confirmation (same modal on Finance → Transactions)

Finance Transactions — bulk selection bar with Approve selected and Reject selected

Walkthrough: Finance → Transactions — clear date range, click amber Pending on the All card, open Approve payment (cancel before saving).

When several payment alerts arrive during a Portfolio KPI review month-end pass, treat Step 4 as the alert-driven entry and Step 7 as the portfolio snapshot: after row-click opens the booking, compare its balance with Dashboard Total Debt (headline vs >15 days subtitle — dashboard-kpi-total-debt-tooltip.png) and Finance → Overview Debt Aging (finance-overview-debt-aging-expanded-bucket.png) — hub matrix: Common Workflows — Payment alert to receivables triage; Portfolio KPI review — Dashboard Total Debt subtitle, FAQ — Dashboard Total Debt subtitle before you clear the last unread rows in Step 5.

If none of those target fields are set, the row is marked read when applicable but you stay on the inbox — use Mark as read when you only want to clear unread without leaving the page.

When the opened booking is still Upcoming, finish Processing a New Booking — Step 5b / Step 6 before you bulk-clear confirmation-week alerts — hub matrix: Common Workflows — Confirmation alert triage (notifications-row-navigate-to-booking-detail.png, bookings-detail-transactions-approve-payment-modal.png, notifications-row-navigation-flow.mp4); when alerts are quiet and move-in is ~7 days out, hand off via Common Workflows — Confirmation to check-in handoff → Managing a Check-in — Step 1 (workflows-operations-check-in-out-planning-view.png).

Step 5 — Clear remaining unread​

Pair with other Notification triage steps

Unread cleanup pairs with /notifications Mark all as read, Common Workflows — Payment alert to receivables triage (confirm balance on each payment overdue row before Mark all as read — notifications-row-navigation-flow.mp4), Common Workflows — Confirmation alert triage (finish Step 5b / Step 6 on each Upcoming Booking created / Payment received row — bookings-detail-transactions-approve-payment-modal.png), downstream workflows (Managing a Check-in, Managing a Check-out, Handling a Late Payment) before bulk-clear, and Glossary — Notification read actions. Upstream: Step 4 (acted on each alert). Downstream: Step 6 when read-state or row-click fails.

  • Per row — Mark as read on unread items you have reviewed but do not need to open in another module.
  • Bulk — Mark all as read clears unread for every notification matching the current filter + search (not a hidden second query).
External automation on inbox cleanup

Account-scoped Landlord MCP get-booking-summary gives portfolio-level active/upcoming counts when several Payments category rows still need row-click follow-up in Step 4 before you Mark all as read. list-bookings and get-booking surface every reservation on a property when unread alerts cluster on one unit — external clients cannot clear in-app read state from MCP; operators finish on /notifications or the Dashboard bell. get-upcoming-move-ins mirrors arrival-week General alerts before you bulk-clear rows that still need Managing a Check-in follow-up. list-tickets, get-ticket, update-ticket, close-ticket, and add-ticket-comment help when Operations-category alerts still reference open turnover or damage tickets — pair close-ticket only after operator Cost allocation is reconciled when contractor spend is involved (Glossary — Ticket — linked cash flows).

Tenant-facing unread cleanup contrast

Booking-scoped Tenant MCP get-payment-info confirms tenant-facing balances on the last Payments alert you opened before you bulk-clear unread — pair with list-bookings-by-email when Inbox message pings (Step 1) preceded the row and identity was ambiguous. get-booking-status and get-dates-and-schedule are the right reads for arrival-week General alerts before you Mark all as read on rows that still need Managing a Check-in follow-up. get-maintenance-tickets / create-maintenance-ticket mirror Operations ticket alerts — do not clear unread on maintenance escalations until the ticket row is Completed or assigned. notify-landlord is for tenant-channel escalations that should stay open until a human replies; do not Mark all as read on those rows until the thread is handled on Bookings → Communication or /inbox. Surface-choice contrast: Automation & AI — Workflow pairing for surface choice.

When you have scrolled through the full history for the active filter, an End of list line appears below the list:

Notifications module — full history scrolled to the end with the End of list marker

Walkthrough: Dashboard bell slide-over → Mark all as read → close → full /notifications page → Unread and Read filters.

Step 6 — Escalate when triage is blocked (when needed)​

Pair with other Notification triage steps

Triage escalation pairs with Using in-app support, Resetting a Management User Password (lockout catch-up), and Portfolio KPI review — Step 7 (month-end Pending mesh). Upstream: Steps 1–5 self-serve paths.

When /notifications row-click navigation, Mark all as read, or the Dashboard bell Inbox sub-tab behaves unexpectedly after you followed Steps 1–5, document what you tried in Internal Notes or the booking Communication thread before you escalate.

Self-serve first:

File Using in-app support when product behaviour blocks triage despite correct operator steps:

Use the Help & Support drawer from Bookings or Dashboard when you need context; deep-link /bookings?support=<ticketId> when email notifications include ticket ids — Deep Links — Support. If a management lockout delayed triage, recover access with Resetting a Management User Password (Step 3) before you file support — refresh Landlord MCP Bearer JWT after Step 3 there; rerun Step 4 row-click on stale Payments alerts, clear unread in Step 5, then finish month-end Pending mesh via Portfolio KPI review — Step 7 and Entering Monthly Utility Bills — Step 4b when utility overage receipts piled up during lockout.

External automation on triage escalation

Account-scoped Landlord MCP get-booking-summary and list-bookings help external clients confirm portfolio context when /notifications search or row-click targets look wrong — pair get-booking, list-payments, and get-payment with the booking id from the alert summary before you file a support ticket. list-tenants, get-tenant, and get-tenant-bookings resolve person-name alerts that never attached a bookingId. list-tickets, get-ticket, and add-ticket-comment document Operations-category escalations on the ticket thread. External clients cannot read in-app notification rows, change read-state pills, or Mark all as read from MCP — operators finish triage on /notifications or the Dashboard bell.

Tenant-facing triage escalation contrast

Booking-scoped Tenant MCP notify-landlord alerts your team when tenants dispute balances or access through a chatbot — it does not replace operator triage in Steps 1–5 or a Vivin support ticket when row-click navigation or read-state APIs fail. get-payment-info and list-bookings-by-email remain the right tenant-scoped reads when Inbox threads preceded the alert. Surface-choice contrast: Automation & AI — Workflow pairing for surface choice.

When to use which surface​

NeedUse
Quick scan of recent alerts on desktopDashboard bell slide-over
Search, read-status filters, full history/notifications
Jump from a notification into Bookings / Tenants / Listings/notifications row click
Operator alert when a tenant payment is receivedEmail + in-app when opted in — see Glossary — Payment notification (operator) and Preferences; in-app rows are visible only to users who enabled Payment notification emails on /settings/personal

Notification triage section cross-reference​

Use the steps above for the main path. For related guides, open Related below, or return to Common Workflows.

Pair with other Notification triage guide sections

Related below links this workflow to modules, concepts, settings, and escalation paths.

Documentation map & escalation​

Upstream & downstream workflows​

Navigation & bookmarks​

Pair with other Notification triage guide sections

Bookmark routes pair with Management Frontend Deep Links and Create New menu.

Concepts & settings that shape this workflow​

Operator habit hubs​

Day-to-day operator habits (lockout catch-up, pending receipts, payment triage, handoffs, and related playbooks) live on the Common Workflows habit hub.

Deep-link anchors for habit hubs

Finance, bookings & collections surfaces​

Check-out vs cancellation​

Lockout catch-up after password recovery​

Pending manual receipt approval​

WhatsApp per-booking messaging​

Bot reasoning (audit)​

ChatBot settings​

Utility overage collections​

Check-out final utilities handoff​

Check-in to check-out handoff​

Check-out collections before refund​

Check-out ledger cleanup before refund​

Cancellation collections before void​

Rent reduction after invoicing​

Notification row-click navigation​

Payment notification (operator)​

Payment alert to receivables triage​

Finance debt receivables triage​

Handling a Late Payment collections​

Finance Income status drill-down​

Cash flow forecast drill-down​

Reject/revert mistaken receipts​

Month-end invoicing (fixed date)​

Bulk Hostkit invoicing​

Same-day turnover coordination​

Occupancy KPI to block hygiene handoff​

Deposit missing on Finance Deposits​

Deposit lifecycle status​

Partly collected security deposit​

Wrong tenant on a booking​

Cancel Booking vs Delete Booking​

Portfolio retirement decisions​

Provider platform Delete Booking guard​

Archived booking ledger visibility​

Archive property (building-level)​

Confirmation to check-in handoff​

Confirmation alert triage​

Portfolio segmentation by tenant category​

Inbox, tenants & operations surfaces​

Deeper workflow reads​

See Upstream & downstream workflows above for the same guides.

Deeper API reads​

Dashboard Total Debt subtitle​

Pair with other Notification triage guide sections

After Step 4 row-click, compare the opened booking balance with post-login Total Debt headline vs >15 days subtitle before Step 5.

Uncovered Debt KPI​

Pair with other Notification triage guide sections

After Step 4, open Finance → Overview and compare Total Debt with Uncovered Debt — when they align, rank Top debtors before Step 5.

Directory list refresh​

When a directory such as Bookings, Notifications, or Listings needs a refresh during this workflow, use Retry on the alert, or reload the page. Zero rows after a successful load means your filters matched nothing — widen filters or clear search.

See FAQ — Directory list refresh and Common Workflows — Directory list refresh.

Booking sidebar tab refresh​

Inside an open booking, Communication and Tickets load independently — use header Refresh (Communication) or banner Retry (Tickets). Other sidebar tabs stay usable. Whole-module list refresh is Directory list refresh.

See FAQ — Communication or Tickets won't open and Common Workflows — Booking sidebar tab refresh.

Key glossary terms​

Module documentation hubs​

  • Notifications module — Full /notifications history with search, filters, and row-click navigation; Payment overdue alerts when Payments category rows need triage (Step 4)
  • Dashboard module — Bell slide-over and post-login KPI context
  • Bookings module — Reservation sidebars opened from row-click navigation
  • Finance module — Portfolio ledgers and payment approval
  • Utilities module — Utility overage alerts after monthly bill entry
  • Analytics module — Month-range portfolio KPI charts
  • Audit module — Discounts export when payment alerts follow goodwill reductions
  • AI Chat module — AI Assistant
  • Landlord MCP — Account-scoped get-upcoming-move-ins and list-tickets during Dashboard bell quick scan (Step 1); get-booking-summary before opening the full inbox (Step 2); list-bookings, get-booking, list-tenants, get-tenant, get-tenant-bookings, list-payments, and get-payment when search narrows the slice (Step 3; read-state pills remain operator UI); get-booking, list-payments, get-payment, and create-manual-payment-in when external clients triage Payments category alerts (Step 4; hub); get-booking-summary, list-bookings, and list-tickets when several unread rows still need row-click follow-up before Mark all as read (Step 5)
  • Tenant MCP — Booking-scoped get-payment-info, get-tenant-info, and list-bookings-by-email when Step 4 alerts followed Inbox threads; get-booking-status and get-dates-and-schedule for arrival-week alerts before Step 5 bulk clear; get-maintenance-tickets / create-maintenance-ticket for Operations ticket alerts; notify-landlord for tenant-channel escalations before Step 5 Mark all as read (hub)
  • Automation & AI — Landlord vs Tenant MCP surface choice during unread cleanup (Step 5) and when triage APIs block self-serve (Step 6)
  • Using in-app support — Vivin product tickets when row-click navigation, Mark all as read, or MCP auth block triage (Step 6)
  • Tenant Portal — Tenant payment and service-request context (hub)
  • Account Settings — Workspace-wide notification masters
  • API Reference hub — Webhooks & Notifications (distinct from in-app rows)