Zodiac Tech CRM Docs

Notifications

What the CRM tells you about, where it tells you, and how to tune it — bell, email, hourly digest and mobile push.

everyone Easy ⏱ 5 min Updated 2026-10-05

Notifications

The CRM should tap you on the shoulder at the right moments: a new lead arrived, someone assigned you a lead, a lead replied, a task is due, an export is ready. This guide shows where notifications appear and how to tune them to your taste — per event type and per channel.

Who this is for

Everyone — notification preferences are personal.

  • Difficulty: Easy
  • Time: 5 minutes
  • Prerequisites: Signed in to the tenant panel.

Where notifications appear

Channel Where
In-app (bell) The bell icon in the top bar of the CRM panel.
Email Your inbox, immediately or as an hourly digest — your choice.
Mobile push Your phone, through the Android app (needs push configured for your business; see below).
Task reminders The assignee of a follow-up task gets a reminder notification (bell + email) before it is due.

The event types you can tune

Open Settings → Business → Notifications (/admin/notification-preferences). You will see a row per event type:

Event When it fires
Lead received A new lead enters your business (webhook, form, import…).
Lead assigned A lead is assigned to you.
Lead stage changed A lead you own moves stage.
Automation ran An automation executed for one of your leads.
Integration sync failed A connection (Meta, WhatsApp, calendar…) failed to sync.
Export ready A large export finished and is ready to download.
Team mentioned Someone @mentioned you in a note.

For each type you choose the channels: in-app, email, push — and for email, the frequency: immediate (as it happens) or hourly (collected into a digest).

Steps

1. Open your preferences

  1. Go to Settings → Business → Notifications.

Expected result: the preference matrix loads, showing your current choices per event type.

2. Tune a type

  1. For an event you care about (for example Lead assigned), tick in-app and email, and set email frequency to immediate.
  2. For noisy events (for example Automation ran), keep in-app only.

Expected result: choices save as you change them; the new rules apply from that moment.

3. Understand the digest

  1. Choose hourly email for an event type.

Expected result: instead of one email per event, you receive a single digest email each hour summarising that period's notifications. Digests are branded to your business and are sent while you are active; unread in-app items stay in the bell.

4. Use the bell effectively

  1. Click the bell in the top bar.

Expected result: recent notifications with links to their subject — a lead, a task, an export. Clicking one takes you straight there. The bell shows unread counts and survives page reloads; marking as read is per notification.

5. Mobile push (optional)

  1. Install the Android app, sign in, and allow notifications.
  2. Push is delivered through Firebase. If your business has not configured its own Firebase project, push simply will not arrive — the in-app bell and email still work.

Expected result: with push configured, notifications also land on your phone.

Push is bring-your-own-Firebase Push notifications are optional and use a Firebase project (BYO). Ask your platform admin — see Push notifications (FCM). Without it, nothing breaks; you just get bell + email.

Expected result

You get exactly the signals you asked for, on exactly the channels you picked — and silence for the rest. Nobody needs to refresh the CRM to know something happened.

Common mistakes

  • Turning everything to immediate email. Inbox flood → you stop reading them → you miss the important one. Use the hourly digest for routine events.
  • Muting lead-assigned email, then wondering about new leads. Keep at least one channel on for the events your job depends on.
  • Expecting reminders without a due time. Task reminders only exist for tasks with a due date — see Follow-ups & tasks.
  • Testing push on a device that was never signed in with notifications allowed. Check the app's permissions first.

Troubleshooting

Symptom Fix
No emails at all Mail must be configured for the install — Email & SMTP. Also check spam.
Digest never arrives, immediate does Digests are sent hourly by the scheduler; confirm cron is running (Cron & queue workers).
No task reminders The reminder engine runs every 5 minutes; check reminder_at is set and the scheduler is alive.
Push not arriving Firebase not configured for the business, or notifications not allowed on the device — see Push notifications.

Technical details

  • Preferences: App\Filament\Pages\Settings\NotificationPreferencesPage (Settings cluster, section Business). NotificationPreference::TYPES = lead_received, lead_assigned, lead_stage_changed, automation_ran, integration_sync_failed, export_ready, team_mentioned; channels in_app / email / push; per-type email_frequency immediate|hourly.
  • In-app notifications are Filament database notifications (the bell).
  • Digests: SendNotificationDigest (notifications:digest, hourly) emails pending unsent NotificationDigest rows for users on the hourly cadence, branded per tenant.
  • Task reminders: LeadTaskReminderNotification (database + mail) sent by tasks:send-reminders every 5 minutes; stamps reminder_sent_at.
  • Push: FCM tokens via PushRegistration in the Android app; platform config in MobileAuthSettings group mobile_auth (BYO Firebase, optional).

Was this page helpful?