Your Command Center has a bell in the top right. It answers one question: is there anything a human needs to deal with, right now? If the number next to it is zero, you can close the tab.

The bell lists two kinds of thing, and only two.

Escalations. A conversation where Arbyn has stopped and handed off to a person. This happens when a shopper asks for a human, when a question falls outside what you have allowed the agent to handle, or when the agent is not confident enough to answer. Each row shows the shopper's own words, so you can tell in a glance whether it is urgent.

Actions waiting for your approval. If your guardrails are set so that refunds, cancellations, returns or address changes need a human to sign off, the requests queue here. Arbyn has already worked out what it wants to do. It is waiting on you to say yes.

Each row shows the time, a short label saying which kind it is, and the beginning of the message. Clicking a row opens that conversation in your inbox, at the point that matters.

The number on the bell is the count of things you have not looked at yet. It clears as you open them.

A notification list that shows you everything is a list you stop reading. We picked the two categories where the honest answer is "a person has to do something", and left everything else off on purpose.

Billing is not in here. If your plan changes, or you reach your conversation limit, that appears as a banner across the top of your Command Center instead, because it affects the whole account rather than one conversation. Putting it in the bell as well would mean you see the same thing twice and start ignoring both.

Normal conversations are not in here. Arbyn answering a shopper correctly is not something you need told about. That is the product working. Your inbox has the full list whenever you want it, and the Command Center shows recent activity underneath.

We would rather tell you this than let you wonder.

There is no SLA breach alert. The database has columns for tracking how long a conversation has been waiting against a target, but nothing fills them in, so there is no honest number to show you. Rather than invent a threshold and put a red badge next to it, we left it out. If you need to know how long things have been sitting, the inbox can be sorted by age.

There is no drill-down or history. The bell shows what is outstanding now. There is no archive of notifications you have already cleared, and no filtering inside the dropdown. The inbox is the place for that.

You cannot turn individual categories off. Both kinds always show. If that becomes a problem for your workflow, tell us, because right now nobody has asked.

The bell shows zero but I know something is waiting. Check two things. First, an escalation only counts while the conversation is still open. If someone on your team resolved or closed it, it leaves the list even if the shopper never got a reply, so look in your inbox filtered to Escalated. Second, approvals only appear if a guardrail is set to require them. If a guardrail is set to handle something automatically, Arbyn does it and never asks, which is working as configured. You can check under Settings, then Guardrails.

The number never goes down. The count is of items you have not opened. Opening the dropdown does not clear it. Opening the individual conversation does. If a conversation genuinely still needs action, it is meant to stay counted.

I clicked a row and it opened the wrong place. It opens the conversation, not a specific message inside it. For a long thread you may need to scroll. If it opened a conversation that has nothing to do with the notification, that is a bug and worth reporting, because the row and the link are built from the same record.

Nothing appears at all, ever, even during busy periods. Confirm your agent is actually escalating. Under Settings, then Escalation Triggers, there is a list of the situations that cause a handoff, and a confidence threshold under Agent status on the Command Center. If the threshold is set low and no triggers are enabled, Arbyn will answer almost everything itself and there will be genuinely nothing to escalate. That may be what you want. It is worth knowing it is a setting rather than a fault.

The dropdown is cut off on my phone. It is built to fit a narrow screen and has been checked at phone width. If it is clipped, your browser is likely zoomed in. Reset zoom to 100 percent.

The bell is the fastest way in, not the only way. The same information lives in:

Use the bell to find out whether you need to act. Use the inbox to actually work through it.