Notifications: the bell and the notifications page

Notifications tell you when something needs you: a new message or mention, an assignment, a reminder, a post waiting for approval, a publish that succeeded or failed, an account that needs reconnecting, a broadcast's progress, an export that is ready. They are personal: each person has their own, whatever workspace they come from. They are written in the language you use the app in (change it on Your account); what someone else wrote - a customer's message, a colleague's note, a list of competitor offers, or an error a platform sent - is shown as it was written. A few older notifications, and some WhatsApp number and template alerts from Meta, are still in English.

The bell

The bell in the header shows a number for unread notifications. It checks for new ones every 15 seconds while the OmniBrand tab is in front of you, once a minute while the tab is in the background, and once more the moment you come back to the tab. While your account is suspended the bell stops checking.

1. Click the bell to see the latest ones. Click one to open what it is about; it is marked read. Each shows how long ago it arrived ("now", "5m", "3h", then the day), as on the notifications page; point at it for the full date and time. One about another of your workspaces is marked In [workspace]: clicking it switches to that workspace first and opens the page there (as the workspace switcher does). While the list loads it says Loading notifications…; if it cannot be loaded it says Couldn't load notifications. with Retry, and the number and the notifications already shown stay. A notification that has nothing to open (it is only there to tell you something) is plain text, not a link, with Mark read under it while it is unread.
2. Mark all read clears them all. While it works the button cannot be pressed again; if it fails, Couldn't mark them read. appears at the top of the list with Retry.
3. The switch at the bottom turns the chime on or off (Sound on / Sound off).
4. See all notifications opens the notifications page (Agents included). Press Esc to close the list. The number on the bell shows up to 9, then 9+.

The first time you click the bell, your browser asks whether OmniBrand may show notifications. If you allow it, you also get a desktop alert while the OmniBrand tab is hidden or not in focus; clicking the alert opens the item.

The notifications page

Open it with See all notifications under the bell, or at /app/notifications.

• The categories are on the left (a row of buttons on a phone), each with its unread count: All, Conversations, Team, Reminders, Calls, Approvals, Publishing, Campaigns and broadcasts, System.
• The heading says "[n] unread" or "All caught up" for the category you are in, once the counts have loaded (it stays blank until then). If the list cannot be loaded you see the reason with Retry instead of the list - never "You're all caught up" at the same time. A notification about another of your workspaces is marked In [workspace] and opens there.
• Unread only hides what you have read.
• Mark all read marks every notification in the selected category (or everything, under All) as read.
• Preferences opens Your account at the notifications table, where you choose what reaches you in-app and by email.
• Notifications are grouped by day (Today, Yesterday, then dates). An unread one has a dot, a bold title and a light tint; a read one keeps its normal colours. Click a row to open it; it is marked read. A row with nothing to open is plain text with Mark read under it. Where a row opens: a mention in a post's comments opens that post; news about one post - your post approved, a step approved, changes requested, a client's answer, a post published or failed - opens that post; "Approval requested" opens Approvals; a team chat message opens its conversation ("(name) messaged you" opens your conversation with them); a ready or failed video opens the Media library on that video; a billing notification opens Settings, Billing; a webhook endpoint that was switched off opens Settings, Integrations; an email, Telegram, Messenger or Instagram broadcast opens that broadcast's page. Approval and daily digest notifications show in the language you use the app in, here and under the bell; older notifications, and the other kinds for now, show in English, and names you typed (a step, a workspace, a note) stay as typed.
• Load more shows older notifications, 50 at a time.

What each category holds

• Conversations: new inbound messages and mentions.
• Team: assignments, new team members and team chat messages.
• Reminders: follow-up reminders and digests.
• Calls: calls, once calling is switched on for a number under Accounts.
• Approvals: approval requests, and decisions on posts you sent for approval; client review answers too.
• Publishing: published and failed posts, plus account issues.
• Campaigns and broadcasts: WhatsApp broadcast progress (finished, paused or failed, and an A/B test's winner), notices about WhatsApp templates and number health, and email, Telegram, Messenger and Instagram broadcasts that finished, paused or failed. On a long label the name wraps onto a second line.
• System: exports (Workspace export ready opens the Export workspace data card in Settings, General), Market Watch undercut alerts, billing, AI videos and other updates.

Failures (a failed post, a disconnected account, an expired sign-in) are marked in red so they stand out. A failed video (AI video generation failed or Ad video rendering failed) names the video and says why, with what to do: the video service is busy (try again in a few minutes); it took too long to render and was stopped (try again; a shorter video is more likely to finish); a picture or video it uses could not be read (replace it in the Media library and try again); the video service refused it (change the wording or the pictures); or it could not be rendered for another reason (try again; if it fails again, contact support). It ends with No AI credits were used. or Your AI credits were returned. When an email, Telegram, Messenger or Instagram broadcast pauses or fails, the notification says how many were sent and why it stopped, in your language, with what to do: the channel it sends from is no longer connected (reconnect it under Accounts, then press Resume); its connection was refused (reconnect it, then press Resume); sending on the channel is not available at the moment (press Resume later); the mailbox reached its daily send limit (press Resume tomorrow); marketing messages are not set up for the Page (finish the set-up, then press Resume); the budget's currency is not the ad account's (cancel it and make a new one); the platform refused the message itself (cancel it and create a corrected one); the budget is spent; or the platform stopped accepting the messages (open the broadcast for the reason, then press Resume). The platform's own words are on the broadcast's page.

If something goes wrong

• "Couldn't load notifications." Click Retry.
• No sound: sound is off under the bell, or the browser blocks audio until you have clicked somewhere on the page.
• No desktop alerts: you blocked notifications for OmniBrand in your browser's site settings; allow them there. Alerts appear only while the tab is not in front.
• Nothing arrives by email: only failures are emailed by default. Turn on Email for the categories you want on Your account.

Related

• Your account: notification preferences
• Notification emails and digests
• Getting around the app