Notices
Notices delivers in-app, push, SMS and email notices to Customers and Workers by their preferences, with digests and quiet hours.
Notices delivers in-app, push, SMS and email notices to Customers and Workers by each recipient’s preferences, with digests and quiet hours. The sender decides what to say; the recipient decides how and when to hear it.
Summary
| Part | This System |
|---|---|
| Group | Communications |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Front: offered from a Startup’s first days |
You can ask:
- “Text customers when their order ships”
- “Send me a daily digest instead of every alert”
- “Do not notify anyone at night”
- “Let customers choose how we reach them”
What you get
| Part | This System |
|---|---|
| Starts | On for every Startup at creation, with nothing to install. |
| Built from | Email delivery, Telephony, Realtime, Workflows |
Nouns it owns
| Noun | Definition |
|---|---|
| Message | A Message is one communication from any party over one medium, such as email, SMS, or chat, inbound or outbound. |
| Channel | A Channel is a place Messages flow, such as a chat channel, a Mailbox, or an SMS number. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Message.create | Message | None | Message.created |
| Message.schedule | Message | None | Message.scheduled |
| Contact.subscribe | Contact | None | Contact.subscribed |
| Contact.unsubscribe | Contact | None | Contact.unsubscribed |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Message.created | By Message.create |
| Emits | Message.scheduled | By Message.schedule |
| Emits | Contact.subscribed | By Contact.subscribe |
| Emits | Contact.unsubscribed | By Contact.unsubscribe |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Customer Lead |
| Team | Customer Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Designer, Researcher, Security Engineer, Sales Engineer, Prospector, Onboarding Specialist, Success Manager, Operations Lead, Delivery Manager, Risk Analyst, Finance Lead, Billing Specialist, Treasurer, Legal Lead, Compliance Officer, Privacy Officer, Contracts Manager, People Lead, Communications Lead |
Approvals and limits
| Verb | Rule | Detail |
|---|---|---|
| Message.create | Mandate answer for the Customer Lead | Answers Conversations and sends Messages, each through the Startup’s Guards. |
Processes that use it
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Customer Lead’s view | The Metrics its accountable Role answers for. | Month-3 retention, Net revenue retention, Logo churn, Repeat purchase rate, First response time, First responses on time, Resolution time, Agent resolution rate |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (13) |
admin | Every Verb (13) |
member | Every Verb (13) |
viewer | Read only (4 of 13) |
Import and export
None.
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Each notice honors the recipient’s Channel preferences and opt-outs; which Events notify stays the founder’s.
Controls it carries:
Related Systems
- Mailboxes
- Phone
- Sequences
- Discussions: also holds Channel
Example
A SaaS for shift scheduling tells nurses about open shifts. One nurse takes push only, after 7am; another takes a daily email digest. A shift starting in two hours skips the digest and goes by SMS, as the Setting for urgent notices allows.