> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wittify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Notification Settings

> Email notification preferences for tickets and leads, billing, and Wittify news.

<Note>
  **Notification Settings** is the cross-system page where you choose which emails Wittify sends you. There are five toggles in three groups: ticket and lead notifications, billing alerts, and the Wittify newsletter. Open it from the sidebar **System → Notification Settings** submenu. The page renders inside the dashboard shell so the system switcher and topbar stay in place.
</Note>

## Reaching this page

Page header:

| Element  | What you see                                                    |
| -------- | --------------------------------------------------------------- |
| Title    | **Notification Settings**                                       |
| Subtitle | *Control which notifications you receive from Wittify on email* |

The body is a single column with three group cards in this order: **Tickets and Leads Notifications**, **Billing Notifications**, **Other Notifications**. The footer has the action bar.

## Initial loading

While the page fetches your preferences from the server, every group card renders with a pulsing skeleton in place of each switch and a placeholder pill in place of the enabled-count chip. **Save Changes** and **Discard Changes** are disabled until the load finishes. This avoids a brief flash where every toggle appears ON for a fraction of a second before snapping to the real values.

## Group card layout

Each group renders the same shape:

| Element           | Notes                                                                                                                                    |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Title row         | A small icon, the group name in bold, and a small *X / Y* pill on the end edge showing how many of the group's toggles are currently on. |
| Group description | A short sentence under the title.                                                                                                        |
| Toggle rows       | One row per preference. Each row has an icon, a title, a description, and a switch on the end edge.                                      |

## Tickets and Leads Notifications

Title: **Tickets and Leads Notifications**.
Description: *Choose how you want to be notified when new tickets or leads are captured by your agent.*

| Toggle  | Title                     | Description                                                                 |
| ------- | ------------------------- | --------------------------------------------------------------------------- |
| Instant | **Instant Notifications** | *Get an email immediately every time a new ticket or lead is captured.*     |
| Daily   | **Daily Summary**         | *Receive a daily summary of all tickets and leads captured during the day.* |

## Billing Notifications

Title: **Billing Notifications**.
Description: *Get alerts about billing, payments, and subscription changes.*

| Toggle | Title                      | Description                                           |
| ------ | -------------------------- | ----------------------------------------------------- |
| 80%    | **80% quota consumption**  | *Notify me when I have used 80% of my monthly quota.* |
| 100%   | **100% quota consumption** | *Notify me when my monthly quota is fully consumed.*  |

The 100% alert also surfaces inside the Plans and Subscriptions page as a usage strip.

## Other Notifications

Title: **Other Notifications**.
Description: *Allow us to keep you in the loop on Wittify news and updates.*

| Toggle     | Title                  | Description                                                 |
| ---------- | ---------------------- | ----------------------------------------------------------- |
| Newsletter | **Wittify Newsletter** | *Stay updated with new features, tips, and best practices.* |

## Defaults

Every toggle defaults to **on** for new accounts. You stay subscribed until you switch a toggle off. The defaults exist so users do not miss critical billing alerts during the first hours of an account.

## Footer action bar

A sticky bar at the bottom of the page.

| Button              | Behavior                                                                                                                                                                                                                                                       |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Discard Changes** | Outline-style. Opens a confirmation dialog. Title: *Discard changes?* Body: *Your unsaved changes will be lost.* The destructive **Discard** button resets every toggle to the last saved value. Disabled while a save is in flight.                           |
| **Save Changes**    | Solid primary. Disabled while a save is in flight or while the page is hydrating. While saving, the label flips to **Saving** with a spinner. Toast on success: *Notification preferences saved.* Toast on failure: *Failed to save notification preferences.* |

If you try to leave the page (or close the tab) with unsaved changes, the browser shows its native confirm prompt.

## What happens when you click Save

The page sends your changes to the server one toggle at a time, sequentially. If a request fails mid-save, the page refetches the authoritative state and resets every toggle to whatever the server now reports, so the UI never drifts away from the truth. You will see the failure toast and any toggles that did persist will stay flipped.

## Server-side delivery

These toggles only control your subscription preferences. The actual delivery (sending an email, scheduling a daily digest, sending the newsletter) happens server-side. Disabling a toggle stops new emails on the next batch run; emails already in flight at that moment may still arrive.

## Common questions

<AccordionGroup>
  <Accordion title="I switched a toggle off but I still got an email.">
    Server-side batches that were already scheduled when you switched off may still send. Wait one batch cycle (usually less than an hour, the daily digest is once per day). If emails keep arriving after that, your account may have an alternate notification path configured at the workspace tier; contact support.
  </Accordion>

  <Accordion title="The Save Changes button is greyed out even though I changed a toggle.">
    Two cases: the page is still loading the initial state (the group cards show pulsing skeletons), or a previous save is still in flight. Wait for either to clear.
  </Accordion>

  <Accordion title="Discard Changes asks me to confirm. Why?">
    The same destructive-confirmation rule applies platform-wide: any action that would erase unsaved work has to go through a confirmation. **Cancel** in the dialog closes it without discarding.
  </Accordion>

  <Accordion title="The X / Y pill in each group does not match the toggles I see.">
    The pill is the count of currently-on switches in that group. The X updates the moment you flip a switch (before saving). If you flip a switch off, **Save Changes** has not run yet, but the pill already reflects your draft.
  </Accordion>

  <Accordion title="My account is brand new. Why are all the toggles already on?">
    Notifications default to on for new accounts to make sure billing-quota alerts and ticket alerts reach you during the first uses. Switch off whatever you do not want.
  </Accordion>

  <Accordion title="I do not see the Notification Settings entry in the sidebar.">
    The entry lives under **System** in the sidebar. Click **System** to expand the submenu. If your role does not include account-level access, the entry will not appear; ask the workspace owner to grant the role.
  </Accordion>

  <Accordion title="Saved my changes, refreshed, and one toggle reverted.">
    A mid-save failure on that single toggle would refetch the authoritative state. The toast on failure is *Failed to save notification preferences.* If you missed it, try the toggle again and watch for the toast.
  </Accordion>

  <Accordion title="Will toggling these off stop critical security emails (password reset, 2FA codes)?">
    No. Critical security emails are not controlled by these toggles and always send.
  </Accordion>
</AccordionGroup>

## Where to go next

<CardGroup cols={2}>
  <Card title="Profile Settings" icon="user" href="/en/Account/Profile-Settings">Personal info, security, and account deletion.</Card>
  <Card title="User Activities" icon="list-ul" href="/en/Account/User-Activities">Audit log of every account action.</Card>
  <Card title="Plans and Subscriptions" icon="credit-card" href="/en/Account/Plans-and-Subscriptions">Plan, add-ons, payment method, billing history.</Card>
  <Card title="Dashboard" icon="grid" href="/en/Systems/AI-Agents/Dashboard">Back to the AI Agents dashboard.</Card>
</CardGroup>