Notifications

Overview

The Notifications page is your workspace activity feed. It collects the in-app alerts WaDesk creates as work happens — campaigns finishing, devices dropping offline, billing events, mentions, and more — into one searchable, filterable inbox. Reach it from More → Notifications, or from the bell icon in the top header.

Notifications are tied to your workspace: the feed shows alerts for the workspace you are currently in, plus personal notifications addressed directly to you no matter which workspace you are in (such as "your password was changed"). Switching workspaces switches the shared feed.

Auto-recorded: Most notifications are created automatically — important changes across your workspace appear here with no setup. Notification titles and messages are stored securely (encrypted).

The Bell vs. the Full Page

There are two surfaces for the same data:

SurfaceShowsBest for
Header bellYour 8 most recent notifications plus an unread count badge, refreshed periodically.A glance while you work.
Full Notifications pageThe complete feed with KPIs, category filters, search, and pagination (12 per page).Triaging or finding something specific.

At the top of the full page, four KPI cards summarize: your unread count (with urgent highlighted), events today (versus your recent 30-day daily average, shown as a percentage delta), active categories (distinct categories used this week), and your workspace quiet hours.

Categories & Filtering

Every notification belongs to a category, and the tabs at the top of the feed let you filter to one of them. Each tab shows a live count. The categories WaDesk tracks:

TabWhat it surfaces
All / UnreadThe two starting views — everything, or just the unread ones.
MentionsWhen a teammate @-mentions you in an internal note.
Campaigns / BroadcastsBulk-send progress and results.
SystemProfile changes, password changes, and platform notices.
BillingPayments, plan changes, and credit events.
DevicesWhatsApp connection drops and reconnects.
ChatConversation / inbox events.
Templates, Webhooks, ContactsEvents from those areas.

The feed itself is grouped by time into Today, Yesterday, Earlier this week, and Older so the most relevant items stay at the top (empty groups are hidden). A search box filters by notification title and message text. The right column also shows your top sources this week — a ranked count of which categories are most active.

Marking Read & Clearing

You have a few ways to keep the feed tidy:

  • Mark all read — clears the unread state on everything in one click (button in the page header, and in the bell dropdown).
  • Mark a single notification read — opening or interacting with one marks it as read.
  • Clear all — deletes notifications from the feed (in the results footer or bell dropdown).
  • Delete one — remove a single notification.

Urgent notifications — for example a password change or a device going offline — are highlighted so they stand out even when the feed is busy, and they are counted separately in the unread total.

The Event Catalog

Beyond the broad categories above, WaDesk has an authoritative catalog of high-signal events you can tune individually in Settings. These are the named events the notification system knows about:

AreaEvents
DevicesDevice connected, Device disconnected
SendingCampaign completed, Campaign failed, Broadcast completed, Flow started, Flow failed
InboxNew customer reply, You were @mentioned, Conversation assigned to you, SLA breached
Billing & walletWallet low balance, Plan upgraded / downgraded, Payment failed
IntegrationsWebhook delivery failed, Integration disconnected, Appointment booked
DigestWeekly summary

Channels & Quiet Hours

How and when you are notified is controlled from the Settings page (the Preferences button on the Notifications page links straight there). You choose, per event and per category, which delivery channels to use:

  • In-app — shows in the bell and the Notifications feed.
  • Email — sent to your account email.
  • Slack — posted to a connected Slack channel.

How a channel decision is made

When an event happens, WaDesk decides whether to send it on each channel using the first rule that applies, in this order:

  1. A specific choice you set for that event in Settings wins.
  2. Otherwise, a default you set for that category.
  3. Otherwise, the built-in default for that event.
  4. Otherwise, the overall default (in-app on, email and Slack off).

The shipped defaults are tuned like a well-run SaaS — quiet email by default, but every critical event lights up the in-app bell. A few high-signal events default email (and some Slack) on:

EventIn-appEmailSlack
Default (everything else)OnOffOff
Device disconnectedOnOnOff
Wallet low balanceOnOnOn
Payment failedOnOnOff
SLA breachedOnOnOn
Campaign failedOnOnOff
Webhook delivery failedOnOnOff
Integration disconnectedOnOnOff
Weekly summaryOffOnOff

Quiet hours (Do Not Disturb) are a workspace setting — the Notifications page surfaces the current window (for example 22:00 to 07:00) in a KPI card. During quiet hours, non-urgent alerts are held back so you are not pinged overnight.

Note: Notification channel and category preferences are saved at the workspace level and are owner-editable. If a teammate cannot change a preference, that is expected — the workspace owner controls these defaults.

Troubleshooting

SymptomLikely cause & fix
I see different notifications than a teammateThe feed is workspace-shared plus your own personal items. Personal events (password, profile) only appear for you.
The feed emptied after switching workspacesExpected — notifications are workspace-scoped. Switch back to see that workspace's feed.
Not getting email or Slack alertsChannels are off by default for most events. Enable them per event/category under Settings → Preferences (owner-only).
No overnight pings even for things I wantQuiet hours are holding non-urgent alerts. Urgent events still come through; adjust the quiet-hours window in Settings.
A preference toggle is disabled for meNotification preferences are owner-editable at the workspace level. Ask the workspace owner.
Old notifications keep reappearingUse Clear all to delete them, or Mark all read to clear just the unread state.
WaDesk Documentation