One row per event, one switch per role and channel, grouped into seven collapsible categories — Sales Pipeline, Estimates & Orders, Invoicing & Payments, Contracts & Legal, Project Management, Teams & Crew, System & Integrations. A filter across the top shows only the ones a customer will read, and customer messages carry their own email and text switches. Every person also gets their own panel to quiet what reaches them, or pause all of it for themselves, without touching anyone else's. The events are a post-frame job's, not a generic sales tool's: a stage finished, the weather the day before a pour, a crew past its figured days, a construction-loan draw ready for the bank.
Also called: notification settings · who gets alerted · team alerts · customer emails
Nothing sends until you switch notifications on for the account
Try itA new account is silent — no emails, no texts, nothing in the bell, to you, your team or your customers. The top of the screen is two switches, applied in order: the account's power switch, then the tally of the event table under it, which dims and says so while the first is off. One control stops all of it for the whole company, and while the account is switched off the bell says so instead of looking like a quiet week. Software that starts emailing your customers before you have read what it says is software you learn about from the customer.
You import last year's leads on a Tuesday afternoon and two hundred people get an email from a company that has not spoken to them since March.
The owner decides when customers start hearing from the business, not the software. Everything set up while the account is off is saved and starts the moment it is switched on, and the date it went on is kept — because the first question after a surprise email is when this started.
Before a switch silences everyone, it says whose notifications you are switching off
The company-wide switches say what they do — Turn off all email, and Turn off all notifications for everyone — and before either runs, a warning names who it hits: everyone at this company. Inside the same box is Change only my notifications, which cancels the sweep and opens your own. Neither sweep wipes the routing underneath, so turning it back on gives you what you had rather than a factory default, and Undo puts back the exact state from before.
Somebody mutes 'notifications' to get through a long weekend, and on Tuesday three customers are asking why nobody answered their texts.
The office manager who wants a quiet weekend gets one — without every rep losing every customer text until somebody notices. The only button that read like 'stop notifying me' used to be the company's, so the way to quiet just yourself is now offered at the moment you reach for the big one.
Pause all my notifications — for you, in this account, nobody else
Try itEvery person has their own panel under My Profile → My Notifications: where their texts go, every event's channels, and one switch — Pause all my notifications — that quiets every event on every channel for them alone, in this account only. Turn mine back on restores every switch they had. Each channel shows what is really happening: sends, muted by you, or off when it is an admin's decision.
A rep wants his phone quiet for a week of vacation, and the only way he can find to do it switches off everyone's.
The owner on holiday, the rep at his kid's ball game and the PM who wants Sunday back each get silence without asking anyone — and without switching off the company. Drawing each channel as what it really does ends the 'I turned it on and still got nothing' calls, because a switch with nothing behind it is no longer drawn as a switch.
Per event, per role, per channel — not one master volume knob
Each event is a row, the five roles you already staff are the columns, and the three channels sit at the end of it: in-app, email, text. Sales gets the new lead, the PM gets stage completed, the crew lead gets the weather advisory the day before. Thirty-six events sit in seven groups, including the ones a post-frame job throws off — a crew past its figured days, a shortfall that needs a decision, a construction-loan draw ready for the lender, a customer's allowance pick. A single on/off per person is why everyone ends up subscribed to everything and reading none of it.
The crew lead's phone buzzes for every invoice paid in the company, so he stops looking at it, and the one that said Thursday's stage was cancelled goes unread with the rest.
The crew lead's phone only buzzes about his crew's work, so he still reads it when the one that matters comes through. The grid is exhaustive on purpose — nothing fires that the owner cannot switch — and each group collapses, with a setting that keeps one open at a time.
Is he actually being told? Check from the bell
Try itOwners, sales managers and project managers get three tabs on the notification bell: Mine, Account — everyone's, each row naming who it was for — and View as: pick a person and see exactly what reached them in the last thirty days. If nothing did, it says so in words. A rep's bell stays a plain list with no tabs to learn. Why something did or did not reach him is the per-person view further down.
A lead goes cold, the rep says he was never told, and the only way to find out was to sign in as him.
A manager settles 'did Marcus even get that?' in ten seconds instead of an argument — and a rep is never blamed for an alert that never reached him. It is a check, not a subscription: nothing is stored or switched, so there is nothing to undo.
Answer the customer from the notification that told you
Try itA New message row carries Call, Text and Email — only the ways that customer can actually be reached, read off his contact record. Pick one and the reply pops out beside the list, which stays open, over a page that is not dimmed: what he said, a box to answer, and Open the full conversation for the whole thread.
Marlin texts about moving the slab pour; the alert says so, then it takes four screens to reply, so the reply waits until evening.
The rep answers while the question is still fresh, so the customer hears back in minutes instead of tonight. It is a reply box, not a second inbox — nothing about how the office works has to change to use it.
The man on the job hears about the job, ticked box or not
Try itAnyone assigned to a build gets project started, stage completed and project completed whether or not his role box is on for those rows. The assignment is the opt-in. Who is on a job is set on the job itself, not on this grid.
The PM actually running the Kelly job had his role box turned off months ago, so the stage that finished on Friday reaches nobody who was standing on it.
The men standing on the build hear about the build, even if their role was switched off months ago — so the stage that finished on Friday reaches the people who were there. Being assigned is read as a subscription in its own right; the honest cost, stated at the foot of the screen, is that this grid alone does not list everyone who will hear about one build.
Every message that leaves your account is on one screen, and the customer ones are marked
Try itAlerts to your own people and messages to the customer are the same grid with a filter across the top, so you can look at only the ones a customer will read. Every customer row carries a To customer tag and a line saying exactly what fires it. 'My customer got an email I did not know we sent' is a phone call you take once and never want again.
A customer rings about an email your software sent him at six in the morning, and you are reading it for the first time while he is on the phone.
The owner never hears about his own customer email from the customer. The filter says To customers rather than External, because what matters is whether your customer sees it — and both audiences share one table so the messages that leave your account sit somewhere you cannot avoid.
Turning one off changes what the send screen can do
Switching Estimate ready off does not just quiet an email — the delivery step on Send Estimate stops offering it, and the link gets copied and sent by hand instead. That consequence is written in the row, beside the switch.
Somebody quiets the estimate email in January; in March a rep hits send, sees no error, and the customer never gets the quote he is still sitting waiting for.
A rep never sends a quote into silence because somebody quieted a switch in January. Naming the consequence beside the control means the trade — no automatic send, you post the link yourself — is made deliberately here, not discovered with a customer waiting.
A text is not a short email
Each customer message that can be texted carries two switches, not one — text them about the estimate, email them the contract. Text is off until you turn it on, and the text version is written as its own sentence: it names your company first, because it lands on a lock screen with no subject line above it.
The customer gets the first two lines of an email as a text from a number he does not know at nine at night, and reports it as spam.
The customer knows who is texting him before he reads a word, so it is not mistaken for spam. A text reads as more urgent than an email, so it is opted into one message at a time, and the reply comes back into the same thread you would ring him from instead of a separate inbox.
The progress update that does not repeat itself
The checkpoint update sends once per genuinely new checkpoint, never on a re-save, and the stage-completed message takes over when the last checkpoint closes the stage — so the customer gets one message about that stage, not two. All of it opens on their project page. The one message the customer gets when a stage finishes, and the reason it only goes once, is covered on stage complete, one send.
The crew fixes a typo on Thursday's checkpoint and the customer gets the same 'progress on your build' email for the fourth time that week.
The customer hears about real progress, once — so the updates stay welcome instead of becoming noise he filters out. The de-duplication lives in the send path rather than in a crew's discipline about when they tick things; a checkpoint genuinely reopened and closed again does send again, because that is a real second event.
When one man says he never gets the texts, you can see whose setting is wrong
Try itSwitch the grid from everyone to that man and it shows what he actually receives — his own mutes folded in with the company routing, both editable from there. Each row says how he is subscribed: by his role, added individually, or not at all. Until this existed, the answer to 'he never got it' was a guess between your settings and his phone, and it was usually wrong.
He swears he never got the text, you swear you sent it, and the afternoon goes on being about that instead of the stage he was supposed to have started.
The afternoon goes back to the build instead of an argument about whose phone is broken. Two settings decide one delivery, so the screen resolves them into one line — subscribed by his role, email on, text muted by him — and the admin can fix it from his own chair.
A mute quiets a channel, it never opens one
A man can quiet his own channels; he cannot switch on one his role was never given. Muted by him beats granted by you, and nothing personal grants what this grid has not. The same panel sits on his own profile, so quieting his phone is his to do without asking anyone with the keys.
A worker adds himself to invoice paid, gets ninety emails a month about money that is none of his business, and the first you hear of it is when he forwards one to the wrong person.
Nobody walks away believing he fixed a text that will never arrive, and nobody quietly signs himself up for ninety emails about money. A personal setting only ever comes down from the company's grid, never up — and a channel only an admin can open explains itself when tapped instead of pretending to be a switch.
Nobody is told about the thing he just did
The person who caused the event is taken off its recipient list, and a man holding two accounts under one email address gets one email, not two — the first account claims the inbox, while the bell row stays per account.
You tick the last checkpoint on the roof, climb down, and find your own phone telling you the stage is complete — twice.
The man who just ticked the roof complete is not nagged about his own work, so when his phone does buzz it is news. The person who caused an event is taken off its list, and two accounts under one address get one email — the inbox is claimed before sending starts, so two events in the same second cannot both win it.
The automatic emails can sound like you instead of like software
The title, body copy and button label of any notification can be rewritten — for the whole company or for one man, with the bell line and the text version authored separately — and the real branded email renders with sample values as you type. Default system wording is the tell that a customer is being handled by a tool rather than by a builder. You write the words here; the logo, colours and type they arrive in are set once in the Brand Center, and the email catalogue renders the whole set on your brand before you switch any of it on.
Your customer gets 'Estimate approved. View: link' from a company that has been talking to him like a neighbour for three weeks.
The customer keeps hearing the builder's voice three weeks into a relationship that started on his driveway. The composer opens on the standard wording, so you edit real sentences instead of facing an empty box, and saving it unchanged stores nothing — an untouched event keeps following the standard copy.
The text goes to the number on his record
A text notification goes to the mobile on his record — the one from his invite, or the one on his sign-in. His own panel shows Texts go to with that number, or says plainly that there is no mobile on file. No number, no text, and the account does not pretend otherwise.
The text switch is on for invoice paid, the office believes all five crew leads are being texted, and three of them have no mobile in the system at all.
The office can see in one place which crew lead will actually get the text, instead of believing all five are covered. A number the account does not hold is skipped and recorded as skipped rather than retried all night, so the fix is a phone number on his record — the first thing his panel shows.
The switch covers this table, and says so
Try itThe line under the master switch states its limit: it covers every event in this table and nothing else. Alerts fired by your build-stage automations take their channels from the stage rules instead. Naming the men who hear about one particular stage — owner, project manager, crew lead or somebody you type in — is done stage by stage in per-stage notification rules, and this grid only sets the account's defaults.
You turn everything off for a week away, and the stage automation carries on emailing your customer on the Tuesday.
The owner can trust the master switch, because it never claims more than it does. Alerts from the build-stage automations take their channels from the stage rules, so one sentence under the switch says where its boundary is — and that same split is why one build's stage can name people this grid never mentions.
- 1Switch the account's notifications on — a new account sends nothing until you do.
- 2Find the event — new lead, missed call, stage completed, loan draw ready.
- 3Switch which roles get it, and on which channel.
- 4Filter to To customers to see exactly what leaves your account.
- 5Anything that changes it for the whole company asks first and names who it hits, with the way to change only your own right there.
- 6Each person quiets their own alerts — or pauses all of them — under My Profile → My Notifications.
- 7Owners and managers can View as anyone from the bell to see what actually reached them.
'My customer got an email I did not know we sent' is a phone call you take once and never want again — which is why what goes to your own people and what goes to a customer sit in the same grid with a filter across the top. A single on/off per person is why everyone ends up subscribed to everything and reading none of it: sales wants the new lead, the PM wants the stage completed, the crew lead wants the weather the day before. And the one button that read like 'stop notifying me' used to belong to the whole company — somebody wanting a quiet evening could silence every customer text for every rep, with nothing on screen to say so. Now the company switches say whose notifications they are switching off, everyone has their own pause, and a manager can check from the bell what actually reached somebody.
- Notification routing was implicit and unconfigurable.
- Internal alerts and customer-facing messages were indistinguishable.
- Turning notifications off destroyed the routing configuration.
- One click could silence the whole company when someone only wanted their own alerts quiet.
- Nobody could check whether a teammate was being notified without signing in as them.
Turn it all off, and put it back
A control above the grid. All off says nobody gets emails or in-app alerts until you switch them back on, and your routing is kept. Email off says the in-app bell keeps working exactly as it does now. Undo puts back precisely what was there, not a default.
See notifications as one man
A picker above the grid. Everyone shows the role-based view. One man shows what he effectively gets, combining your company's routing with his own mutes — and lets you fix either from the same screen.
Write your own notification wording
A composer opened from a notification row. Write it for the whole company, for yourself, or on behalf of one man. The preview is the actual branded email, not a plain-text approximation — and it says when the longer email body gets used instead of the short message. Reset puts the original wording back.
The notification engine
When something happens, the engine works out who is subscribed, checks your company's settings and each person's own mutes, applies your wording if you wrote any, then puts a row in the bell, sends the email and sends the text — only where all of that allows it. Role-based sends, one named person, and per-stage rules all run through the same place.
The notification bell
The bell sits in the sidebar on a desktop and the header on a phone, and both always show the same number. The panel holds the last thirty days, with Mark all read, a one-tap mute, and an offer to turn on desktop alerts.
Toasts
One stack that nothing on the screen can clip or hide. Older ones collapse into a plus-N-more pill that opens the bell. They never lock the page, so you can keep working straight through them.
Two sounds, and only two
Two short sounds made in the browser — no files, nothing to license. Routine events make no sound at all. However many arrive at once, you hear one sound, pitched at the loudest thing in the batch.
Desktop alerts
A card in the bell panel offers get pinged even when you're in another tab. Say yes and qualifying events raise a real alert carrying your own logo. Click one and it brings the window forward, marks it read and takes you to the record. If your browser has blocked them, the panel says so and points out that chimes still work.
Quiet your own noise
A switch per event, per channel, under your own profile. Blank means follow the company setting. Off means muted for you. Your mobile number for notification texts lives on the same screen.
