Notifications
Fertiligent tells your team something needs attention in three ways: the notification bell inside the portal, browser push notifications that reach you when the portal isn't the active tab, and email for things that shouldn't wait until someone signs in.
The notification bell
The bell in the portal header carries your team's feed — a new patient message, a conversation the assistant escalated, and similar events.
- It persists. The feed is stored, so items survive signing out, a browser restart, or a deploy. What you haven't dealt with is still there tomorrow.
- Items take you where you need to go. Clicking an item marks it read and opens the thing it's about — the escalated conversation, for example, rather than a general list you then have to search.
- Old items are cleared automatically, on a retention window your clinic can set. The default is 90 days.
Browser push notifications
Each user opts in to push from their browser, on each device they use. Once opted in, Fertiligent delivers notifications to that browser and they appear as native desktop or mobile notifications. Stale subscriptions (for example a browser that's been cleared) are cleaned up automatically.
Notification email
Email carries the same kinds of alerts to people who aren't in the portal — including patients and prospects, for things like a new secure message.
- Who it comes from. A secure-message notification arrives from Secure Messages, so a patient can recognise it in a crowded inbox. Replies are routed back to your clinic's reply mailbox.
- Every email has an exit. Notification emails carry an unsubscribe link in the footer, and support the one-click unsubscribe button that Gmail, Outlook and other mail clients show at the top of a message. Either route opts the recipient out.
- Staff can reverse an opt-out, so a patient who asks your team to start emailing them again doesn't have to work out how to undo it themselves.
Unsubscribing stops notification email to that address. It is not the same as withdrawing consent to receive personal health information, and it is not the same as a patient telling you they no longer wish to proceed with their referral. Those are recorded separately — see Consent & patient privacy and Patient messaging & SMS.
In-app alerts vs notifications
Notifications are distinct from clinical patient alerts — the severity-graded, assignable items your team tracks and resolves inside the portal. Patient alerts live in the patient's record; a notification is the nudge that brings you back to the portal to act on one.
Availability
The bell and browser push are available to every clinic, subject to permissions and each user's own opt-in.
Outbound notification email is off until it's switched on for your clinic, and it stays off if anything about the check is uncertain — the platform errs toward not sending. Ask your Fertiligent contact to enable it. An administrator can manage which staff can send and receive notifications.