Notifications
The Notifications center is your workspace's in-app inbox for alerts that need your attention — a new conversation arriving, a conversation that needs a human, a customer waiting for your team, a message or call that was refused, a scheduled workflow that keeps failing, an out-of-credits warning, a reply on your support ticket, and other system messages. Instead of watching every page, you get one place where these events pile up, and a bell in the top bar that tells you at a glance whether anything is waiting.
Notifications are raised automatically by real activity in your workspace. You never create them by hand — they appear as events happen.
The bell
A bell icon sits in the top bar of the Studio, on every page. When you have unread notifications, a red badge shows the count (it caps at 99+). The count refreshes on its own every 30 seconds, so you see new alerts without reloading the page.
Click the bell to open a quick dropdown with your 10 most-recent notifications:

- Each row shows a title, a short body, and how long ago it arrived (for example "5m ago"). Unread rows carry a coloured dot for their category.
- Unread rows are highlighted; read rows are dimmed.
- Click a row to open whatever it points to — a conversation, a case, a billing page — and it is marked read at the same time.
- Mark all read clears the highlight on everything at once.
- View all takes you to the full Notifications page.
The dropdown shows No notifications when there is nothing to show, and closes when you click outside it or press Escape.
The Notifications page
Open Notifications from the bell's View all link (or go to /notifications) for the complete history. It works like the dropdown but adds filters and loads older notifications on demand.

Each notification row shows:
| Element | What it tells you |
|---|---|
| Title | A one-line summary of the event |
| Body | A short description with the detail |
| Category tag | Which kind of event this is (see below) |
| Dot | Shown only while unread, in the category's colour |
| Timestamp | The date and time it arrived, for example Sep 25, 02:45 AM |
| Highlight | Unread rows are highlighted and bold; read rows are plain |
Clicking a row marks it read and, if the alert links somewhere, navigates you there.
Categories
Every notification belongs to one category, each with its own colour so you can scan the list quickly:
| Category | Colour | Typical trigger |
|---|---|---|
| Conversation | Indigo | A new conversation starts on one of your channels ("New conversation — New web conversation started"), the customer writes again in a conversation you took over ("Customer replied"), or a caller asks not to be recorded ("A caller asked not to be recorded" — it quotes the caller and asks you to decide whether to keep or delete the recording) |
| Escalation | Rose | An agent hands a conversation to a human, a human task times out, or a finished conversation is flagged "Conversation needs follow-up" because the customer left unhappy with the issue unresolved. Contact-center alerts land here too: a chat offered to you ("A customer needs you") or to your team when nobody is free ("A customer is waiting for a person"), a hand-off nobody took ("Customer wanted a human — nobody was available" or "— nobody answered", "Customer waited too long in the queue", "Customer left while waiting for a human", "Voicemail from a customer who wanted a human"), and "A booking is stuck" when a booking needs checking |
| Billing | Amber | Your credits run out and an incoming message is blocked ("Out of credits") |
| Support | Sky blue | The Perfox team replies to, or changes the status of, one of your support tickets |
| System | Slate | The AI couldn't answer because of a problem with the AI provider. Also: a message or call that was refused because no sender is linked to it (see below); an unattended workflow (schedule, webhook or event) that failed or ran with errors ("Workflow "…" failed" / "… ran with errors", naming the step and the error); a webhook call that was accepted but could not be run ("Webhook delivery to "…" failed"); and "… has a suggested improvement" when your agent has a new learned change to review |
| Apps | Indigo | A marketplace app subscription is enabled, fails to set up, renews, lapses or is cancelled, plus unpaid-plan reminders |
| Campaign | Emerald | Still listed in the filter, but nothing currently raises it |
Refused sends and failing workflows
Perfox never falls back to a default phone number, WhatsApp number, email address or messaging-app account. Every send goes out from a sender linked to the agent or workflow. When an SMS, WhatsApp message, phone call, email or messaging-app reply is refused — because no sender is linked, or the sender isn't on any of your connected accounts — you get a System notification such as "WhatsApp from +91 98765 43210 was refused" or "SMS refused — no sender linked". The body tells you what to fix, and clicking it opens the agent (or Credentials when no agent is involved).
Problems like these repeat on every attempt, so they are sent at most once a day: once per channel, reason and sender for a refused send, and once per workflow for a failing unattended workflow or webhook delivery. A workflow that recovers and then fails again alerts you straight away, but never more than once an hour.
Filtering and marking read
Two controls at the top of the page narrow what you see:
- Unread only — a toggle that hides everything you've already read, so you can focus on what's outstanding.
- All categories — a dropdown to show a single category (Conversation, Escalation, Campaign, Billing, System, Support or Apps) at a time.
Mark all read clears every highlight in one click. You can combine the toggle and the category filter — for example, "unread Escalations only".
Loading more
The page loads the newest 20 notifications first. When there are older ones below, a Load more button appears at the bottom; click it to append the next page. This keeps the list fast even after a long history has built up.
When nothing matches your filters, the page shows No notifications — You're all caught up.
How a notification reaches you
Some notifications are addressed to you specifically; others are workspace-wide and seen by everyone on your team. Either way, your own read/unread state is tracked per person — marking one read for yourself doesn't clear it for a teammate.
Tips
- The red badge is your prompt — if it's showing a number, something is waiting.
- Use Unread only to burn down a backlog, then Mark all read to reset.
- Filter to Escalation to keep an eye on conversations handed to a human, customers waiting for your team (see Contact Center), or conversations flagged for follow-up, Billing to catch out-of-credit blocks as soon as they happen, and System to catch refused sends and failing scheduled workflows.
- Clicking a notification is the fastest way to jump straight to the conversation, case, or page it refers to.