Notifications: the bell, email, and routing
Nexxus alerts your team about leads, applications, payments, maintenance, late fees, lease deadlines, and more — via the in-app bell and email, with two layers of control over who hears what.
Nexxus surfaces events two ways: the bell in the top bar (in-app, real time) and email. What gets sent where is controlled in two layers.
What triggers a notification
The main event families: new leads and inquiries, applications (submitted, signed, ready to countersign), payments, maintenance requests, late fees assessed, lease deadlines (expiring 60/30/7 days out), import/sync nudges, and activity on your NexxusHub posts.
Layer 1: company routing (Settings → Team)
Decides which teammate each event family goes to — leads to whoever works the funnel, maintenance to your coordinator, and so on. A catch-all email can receive everything (useful for a shared inbox); you can also set a company notification email for events that belong to the business rather than a person.
Layer 2: personal preferences
Each teammate controls their own delivery per event type — in-app, email, both, or off — under their account settings. Personal preferences never add events routing didn't send them; they only tune delivery of what layer 1 assigned.
Resident-facing emails
Separate from staff alerts: transactional emails to applicants, tenants, and owners (application received/approved, lease ready/executed, owner statements). These are gated by a single company-level toggle so you can keep them off until your branding is set up. All email goes out branded with your logo and accent color.
If someone's missing alerts
Check in order: (1) company routing assigns that event family to them, (2) their personal preference for it isn't off, (3) the email isn't in spam — Nexxus sends from a verified domain, but a new recipient's filter can be cautious at first.