Notifications

Most assistants only speak when spoken to. Yours can reach out — a real push notification to your phone or browser when something you care about happens, even when you have no tab open and haven't thought about the agent all day.

This is what turns the agent from a tool you visit into a colleague who taps you on the shoulder at the right moment.

Where notifications arrive

The Performance Hub mobile app — standard push notifications on your phone.
Your browser — web push on desktop and mobile browsers, delivered even with Performance Hub closed (allow notifications for Performance Hub when your browser asks).

Every notification deep-links back to the conversation that produced it — tap through and you're looking at the context, ready to respond. Notifications can carry more than text: the agent can attach an image (a chart it generated, a photo it processed), up to three action buttons, and a choice of alert sounds; supported platforms offer inline reply — answer the agent straight from the notification without opening anything.

Asking to be notified

Like everything else, it's conversational. Tell the agent what to watch and it handles the rest:

"Notify me when the overnight backup report is ready."

"Watch for any failed payments and notify me with the member's name and amount."

"When a payment completes on my payment link, notify me — then start the shipping process."

That last one is the pattern worth noticing: notify and then act. A notification can be one step in a chain — the agent tells you something happened and gets on with the follow-up you've already authorised.

The three common shapes:

Shape	Example
One-off	"Tell me when you've finished analysing that spreadsheet."
Standing watch	"Always notify me if a door controller goes offline for more than 15 minutes."
Scheduled delivery	The morning briefing from an automation, pushed at 7am

Response-ready notifications

Long tasks come with a built-in courtesy: if you ask for something that takes a while and walk away, the agent automatically sends a "response ready" push when it finishes. Start the deep-research question, close the laptop, and your phone buzzes when the answer is waiting. Nothing to set up.

Who gets notified

Notifications go to the person the agent is working with — your watches notify you. Staff who share the agent set up their own watches, and each person's notifications deep-link into the agent under their own identity. (Separately, the platform itself notifies device owners about administrative events — access requests, ownership changes, replacement restores — through the same channels.)

Sensible-use limits

Push channels stay useful only if they're not noisy, so notification volume is rate-limited per device per hour — generous for real use, but a brake on a misconfigured watch that would otherwise fire continuously. If the agent hits the limit, further notifications in that hour are dropped rather than queued into a flood; the underlying work still completes and the conversation still holds the results.

Design watches to be quiet by default: "only tell me if something's wrong" beats "tell me the status every hour" — see the watchdog pattern in Automations.

Two privacy habits worth building in: notification text appears on lock screens, so tell the agent to keep sensitive figures or member details out of titles and bodies (put them behind the tap-through instead); and attached images are delivered via temporary links that expire after about a week — fine for a chart, not the place for confidential documents.

If notifications aren't arriving

Check your browser or phone hasn't blocked notifications for Performance Hub (browser site settings / app notification settings).
Confirm the device is online — a device with no connectivity can't push (it will send what still applies once it's back).
Ask the agent — "what watches do you have set up for me?" — to confirm the watch actually exists as you intended.