Notifications

UpServe agents finish work on schedules, webhooks, and autonomous runs — even when you’re not looking at the screen. To make sure you don’t miss the results, UpServe delivers them in two ways: in-app notifications and iOS push notifications.

When do notifications arrive

When an agent has a reply for you — If an autonomous run finishes while you’re away from the chat, or a scheduled run wakes the agent up and it produces an answer, a notification is sent. If you’re already viewing that agent’s chat, no push is sent — the message just appears in the conversation.
When your credit changes — Low balance, grants, deductions, and expirations are surfaced as notifications.
When an agent is paused — If an automatic run is interrupted — for example, by an empty credit balance, or because there’s been no contact with the agent for a while (7 days by default) — you’ll be told which agent stopped and why. One day before an agent is paused for inactivity, you’ll get a single heads-up notification.
When your subscription changes — Subscription start and cancel events are announced.
When you’re approved off the waitlist — A one-time notification is sent automatically when an admin approves your account.
Daily summary — Every morning at 9 AM in your time zone, UpServe sends a brief recap of the previous day’s agent activity. If no notifications occurred the day before, no summary is sent.
Do Not Disturb catch-up — When your Do Not Disturb window ends, UpServe sends a short summary of any agent activity that happened while you were away. This only applies if you have Do Not Disturb enabled.

Notification categories

The following categories can be toggled individually in settings:

Agent response
Credit low / granted / deducted / expired
Subscription started / canceled
Agent paused
Upgrade Suggestions
Skill improvement proposal received — Arrives when another user’s agent reports a defect in a skill you’ve published to the Marketplace. Open My Skills → Proposals to review and accept or dismiss each proposal.
Library cleanup available — Arrives when a periodic scan finds candidates that may need cleanup. Sent at most once every 7 days per user. Open Settings → Skill cleanup to handle each item on your own terms.
Skill deprecated — Arrives when the original author of a skill you’re using marks it as no longer supported. You can search the Marketplace for a replacement or fork the skill to keep using it.
Weekly skill health report — A weekly summary of success rates across your installed skills, sent once per week.
Marketplace comments — Arrives when another user comments on an item you posted to the Marketplace.
Community comments — Arrives when someone comments on a post you wrote in the community.
Skill auto-created — Arrives when an agent creates a new skill on its own, based on experience from a completed task. The skill is private to that agent and is not published to the Marketplace.
Skill auto-improved — Arrives when an agent refines one of its existing skills on its own. The notification includes a note that you can roll back to the previous version if the change doesn’t help.

Each category has its own toggle so you can keep only the ones you care about. The daily summary and Do Not Disturb catch-up cannot be turned off individually.

Where to configure them

On the web, open Settings → Notifications (/settings/notifications). Everything is managed from this one screen:

Master push toggle — The large toggle at the top. When it’s off, no notifications are pushed to your phone (in-app notifications still accumulate).
Per-category toggles — Turn each category from the list above on or off. Turning a toggle off prevents both the push and the in-app notification from being created.
Do Not Disturb hours — Set a start and end time. During this window, push notifications are silenced. UpServe uses your current time zone. Overnight windows (e.g. 22:00 – 08:00) work as expected.
Mute specific agents — All agents registered to your account are listed. Toggle any agent to silence every notification from it.

Receiving push notifications on iOS

UpServe push notifications are delivered through the iOS app.

From Settings → Notifications, tap Download iOS app to open the App Store, or search “UpServe” directly. (The link points to the US App Store; searching “UpServe” may be faster in other regions.) Install the app.
Sign in. On first launch, iOS asks for notification permission — tap Allow. From that moment on, the device can receive push notifications.
Once permission is granted, the app automatically links the device to your UpServe account. No extra setup is needed.

If you declined permission earlier, you’ll need to re-enable it from Settings → Notifications → UpServe on iOS. The app won’t ask again on its own.

Live Activities (Lock Screen / Dynamic Island)

When you’re using the iOS app, UpServe shows real-time progress on the lock screen and Dynamic Island while an agent is working.

After you send a message and navigate away, a Live Activity starts automatically.
The Dynamic Island updates as the agent switches between states — for example, when it calls a tool or waits for your approval.
When the work is done, a brief summary of the final response remains on the lock screen for a few minutes before disappearing.
Requires iOS 16.2 or later, with Live Activities allowed in your device settings.
On iOS 17.2 or later, the server can start a Live Activity remotely without the app being open first, so autonomous results can update your lock screen even when you haven’t launched the app.

What about the web?

On the website, the bell icon in the header shows the unread count and opens the notification list when clicked. New notifications update the badge in real time. The browser’s own notification permission is not used — every alert is shown inside the UpServe interface.

If you want push notifications on your phone, follow the iOS app instructions above.

How autonomous results are delivered

When an agent finishes work on its own, UpServe applies these rules. Note that when you start a conversation directly, the reply appears inline and no separate notification is generated — notifications are only created when the agent acts without a direct user request (scheduled runs, webhook triggers, and other autonomous executions).

While you’re viewing that agent’s chat, no push is sent — the response just appears inline in the conversation.
While you’re on a different screen or have the app closed, both an in-app notification and a push are sent.
If the same agent replies multiple times in quick succession, only the first reply triggers a phone push; subsequent replies update the in-app notification as a grouped entry instead of pushing again. Opening the chat clears all unread notifications for that agent.

Advanced

You don’t need this section for normal use. Read it only if you’re troubleshooting missing notifications or want to understand the system in more detail.

Internal categories

The toggles you see in settings map to these underlying categories. The labels in the UI take priority, but the category names may appear in search and metadata views.

AGENT_RESPONSE — agent reply
AGENT_PAUSED — agent paused (out of credits, or no contact for a while). Settings key: agent_paused
AGENT_INACTIVITY_WARNING — a heads-up sent one day before an inactive agent is paused. Not in the opt-out mapping, so it cannot be disabled individually.
CREDIT_LOW / CREDIT_GRANTED / CREDIT_DEDUCTED / CREDIT_EXPIRED — credit-related events
SUBSCRIPTION_STARTED / SUBSCRIPTION_CANCELED — subscription events
WAITLIST_APPROVED — waitlist approval. The settings key (waitlist_approved) exists and the backend respects it, but no UI toggle is currently exposed in settings.
UPSELL_CREDIT / UPSELL_FEATURE — recommendations and upsell hints
DAILY_SUMMARY — sent once per day at 9 AM in the user’s time zone. Not in the opt-out mapping, so it cannot be disabled individually. Suppressed automatically if no notifications occurred the previous day.
DND_SUMMARY — sent shortly after the Do Not Disturb window closes. Not in the opt-out mapping, so it cannot be disabled individually. Suppressed if no notifications occurred during the DND window.
SKILL_PROPOSAL_RECEIVED — proposal received on a published skill. Settings key: skill_proposal_received
SKILL_LIBRARY_CLEANUP_AVAILABLE — Personal Curator found cleanup candidates. Settings key: skill_library_cleanup_available
SKILL_DEPRECATED — a skill you use has been deprecated by its author. Settings key: skill_deprecated
SKILL_HEALTH_REPORT_WEEKLY — weekly skill health summary. Settings key: skill_health_report_weekly
MARKETPLACE_COMMENT — a comment on an item you posted to the Marketplace. Settings key: marketplace_comment
COMMUNITY_COMMENT — a comment on a post you wrote in the community. Settings key: community_comment
SKILL_CLUSTER_ALERT / SKILL_FORK_INSPIRATION / SKILL_SUGGESTION / SKILL_PROMOTION_SUGGESTED / SKILL_DERIVATIVE_PUBLISHED — skill curation notifications. Not in the opt-out mapping, so they cannot be disabled individually.
SKILL_AUTO_CREATED — sent when an agent autonomously creates a new skill from this task’s experience. Not in the opt-out mapping, so it cannot be disabled individually.
SKILL_AUTO_PATCHED — sent when an agent autonomously improves an existing skill. The notification body includes a pointer to the version history for one-click rollback. Not in the opt-out mapping, so it cannot be disabled individually.

AGENT_RESPONSE push suppression

The decision to skip a push is made on the server by checking whether you currently have that agent’s chat open. If the iOS app happens to be in the foreground but the server doesn’t detect an active session, a push may still be delivered. The message will already be visible on screen, so it’s a visual duplicate rather than a missed notification — the app does not filter it out at the client level.

Autonomous response grouping

When a new agent response arrives while an unread notification for the same agent already exists, the server replaces the existing notification with a grouped one. This grouping is per-agent and applies regardless of platform (iOS or web). Opening the chat and reading the messages clears all unread notifications for that agent.

Troubleshooting checklist

Is the master push toggle on? With it off, no notifications reach your phone for any category.
Is the matching category toggle on? For example, if Agent response is off, neither push nor in-app notifications are created for that category.
Are you inside Do Not Disturb hours? Double-check the start and end time and make sure your phone’s time zone is correct.
Is the agent muted? In the Muted agents section, turn the toggle off to start receiving notifications from that agent again.
Is notification permission granted on iOS? Open Settings → Notifications → UpServe on the device and make sure “Allow Notifications” is on.
Is the right account signed in on the device? Logging in with another account moves push delivery to the new account. Signing out disables push on that device for the previous account.
Are you already viewing that agent’s chat? Push is intentionally suppressed while you’re on the same screen.

Device registration behavior

On first launch, the iOS app asks for notification permission and — once granted — registers the device with your UpServe account automatically. No manual step is required.
Signing in with a different account on the same device re-links the device to the new account.
Signing out deactivates the device for that account, so push delivery stops.
iOS is currently the only push platform. Android and web push are not supported; the web uses in-app notifications only.