Use cases

Staff alerts: route website events to the human on duty

Some website events need a human in the next five minutes, and that human is rarely sitting at the dashboard. Send the event to their pocket instead.

The events worth interrupting someone for

Every alert is a website event you already have, pointed at a phone number you choose.

Routing, not broadcasting

Alerts go to the numbers you pick per event — orders to the shop phone, leads to whoever is selling this week, failures to you. Swap the on-duty number in the dashboard when shifts change. This is routing a handful of events to a handful of staff, not blasting a list — which is why a notifications plan is the right shape for it and a marketing platform is not.

Quiet hours, on your terms

Customer-facing texts respect quiet hours without exception. For alerts to your own staff, you choose: a restaurant wants the order buzz at 9pm, an accountant does not. Per-event windows mean the payment-failure text can wait for morning while the order text never waits.

Costs almost nothing

Staff alerts are single texts to a couple of numbers — usually the smallest line item in your quota. Most businesses run them alongside order alerts on the same plan without noticing the volume.

Common questions

Do my employees have to opt in?

Staff numbers are added with their consent and can text STOP at any time — the same compliance layer covers every recipient, including your own team.

Can one event alert two people?

Yes — an event can notify multiple numbers, and an order event can text the customer and your staff at the same time.

Can alerts go to a shared shop phone?

Yes. Any mobile number works; many shops point order alerts at one counter phone and leave personal numbers out of it.

Ready when you are.

Orders, leads, failures, stock — to the phone of whoever is on duty.

Route your first alert

Five-minute setup. We handle the carrier paperwork.