Notifications

Foxl can tell you when long-running work finishes, so you do not have to sit and watch it. Every notification is opt-out per category, and nothing is sent unless the work you started actually completed.

Where to control them

Settings > Notifications, on every platform. The pane is organised by where a notification arrives:

• This device - the desktop app's own toasts, one switch per event type. Shown only in the desktop app; a browser or phone has no local toasts to gate.
• Phone push - the categories below. They are stored with your account, so you can turn a phone category off from your desktop, and they apply to every phone signed in as you.
• Email - two categories and a blanket unsubscribe, see Email.
• Test - fires a real notification through the real pipeline, so you can see where it lands.

On a phone the pane also shows the operating system's permission state and a link into the system settings when permission has been denied there (no in-app toggle can grant that for you). Push needs two things to be true: the operating system has granted Foxl permission, and the category is enabled. If you never see a notification, check the permission state first. If you declined the prompt and later switched notifications on for Foxl in iOS Settings, Foxl re-registers the next time you come back to it - no relaunch needed.

The categories

Everything useful defaults to on because it is low-volume and follows an action you took. Only the Den and marketing are opt-in: neither is sent unless you explicitly enable it. The Den row is hidden entirely while there is no game to be notified about, and hiding it never rewrites the preference you set.

A message that reaches your agent through a Slack, Telegram or Signal bot is not one of these: it shows as a desktop notification and in the bell on connected devices, and does not push to your phone.

Where each one opens

A notification that leads nowhere is worse than no notification, so every push the server can send is checked against both doors - the banner from the operating system and the row in the bell - and one that leads nowhere fails the build rather than shipping.

This holds whether the app was open, in the background, or closed, and the rows in the bell lead to the same places as the banners.

The badge, the bell and the banner agree

• The number on the app icon is exactly the bell's count. They used to be computed differently, so a phone could show three on the home screen and one on the bell for the same list. Everything the badge counts is now reachable, so it can always get to zero.
• The count advances per notification. Each push used to carry a hardcoded badge of 1, so three replies arriving while the app was closed still read as 1.
• Product updates and the occasional Den notification do not touch it at all. They add nothing to your inbox, and a badge on them used to reset a genuine count of five down to 1.
• Reading in the app clears the lock screen. Rows you read, archive, swipe away or clear have their banners removed. Unread items are left alone in both places.
• A follow-up replaces the one before it. Updates about the same conversation, task, question, note or call collapse onto the previous banner, so a task that became ready to merge and then merged does not leave two banners saying different things. Separate things stay separate.
• Signing out on a phone clears its bell and its banners, and a reply typed from a notification is never sent under the next account on a shared phone.
• Opening the app no longer resets the count, and a second phone on the same account no longer wipes the first one's number - the badge is one number per account.

The macOS dock badge is deliberately different

On the desktop, the dock badge keeps counting unread conversations alongside notifications. A reply that lands in a conversation you are not looking at files no notification of its own there, so the badge matches the sidebar's Chat row, which counts the same thing.

Chat replies

A reply can take a while on a hard question, and if you leave the app before it lands there is nothing on screen to tell you it did. This fires only when you were away when the response completed - if you watched it stream, you already know.

Tapping the notification opens that conversation.

Notes transcripts

Transcribing an imported recording takes roughly as long as the audio, so the natural thing is to start it and put the phone down. This category covers a finished transcript, and also the AI results that follow it - the summary and the coaching report, which are the slowest steps because they read the whole transcript. Tapping it opens the note that finished.

A summary you watched appear on screen does not notify you; only one that landed while you were elsewhere.

Because Notes does its transcription work on the device rather than on our servers, the app itself reports completion. If you force-quit Foxl mid-import, the import stops with it and no notification is sent. Which transcription destination you use - your own AWS account, On device, or your own Deepgram, AssemblyAI, OpenAI or ElevenLabs key - does not change this; the app reports completion in every case.

Code tasks

A Foxl Code task runs on its own and can take minutes. This fires when the task reaches a state that wants your attention: a pull request ready for review, a merge, or a failure.

Promotions and tips

The only category that is off unless you turn it on, and the only one not caused by something you did. If you enable it, you will hear from us at most once every 30 days - that limit is enforced on our side, not a promise about intent.

What you receive depends on which parts of Foxl you use and how long you have been here, so the message is at least relevant. That grouping is based on counts and dates - your tier, when you signed up, when you were last active, whether you have used Notes or Code. It never involves the contents of your messages, transcripts or files.

You will not hear from us in your first week, whatever your settings say.

Email

Two categories, stored with your account and editable in the same pane (or from the link in any marketing email, signed out):

A one-click unsubscribe link turns off all Foxl email at once and stays that way, whatever the switches say, until you turn email back on. Sign-in links, receipts, payment problems and the usage notices at 80% and 100% of a credit allowance are part of the service and are always sent.

Requirements

Your phone registers itself with Foxl once, the first time you run the app and grant permission. That registration is tied to your account, so notifications follow you across devices signed in to the same account, and signing out on a device stops that device receiving them.

Privacy

Notification text contains only what you need to recognise the event - a conversation title, a note name, a task title. The body of a message, the contents of a transcript, and any file content are never included in a notification payload.