Skip to main content
Notifications keep your team in the loop without anyone sitting in the dashboard. They’re configured once for the whole workspace, under Settings.

​
How it’s set up

Two independent channels, each with its own recipient list and its own on/off switch: Both are off by default. Turning a channel on with an empty recipient list does nothing — add the addresses first.
Recipients are workspace-level, not per user. Anyone on the list gets notified whether or not they have a Recepta.ai login — useful for an owner or dispatcher who doesn’t work in the dashboard.

​
Choosing recipients

Use a shared address

Something like office@ or a distribution list survives staff changes. A personal address stops being read the day that person leaves.

Keep the SMS list short

Text alerts interrupt. Reserve them for the one or two people who need to act immediately, and leave everyone else on email.
SMS notifications go out over the same A2P-registered messaging as your customer texts. If your registration isn’t approved yet, internal SMS alerts won’t be delivered reliably either.

​
Keep the billing address monitored

Separate from these settings, billing notices go to your billing contact — and this is the one that catches people out.
A failed payment eventually suspends service, and a suspended workspace stops answering your phone. If billing notices are going to someone who has left the business, nobody sees the warnings. Check the address on your billing settings is one a person actually reads.

​
Building your own alerting

If you want alerts inside your own tools — a Slack channel, a dispatch board, an on-call system — use webhooks rather than email. Subscribe to the events you care about and route them wherever your team already works: That gives you routing, filtering, and escalation logic that a recipient list can’t.