The switches for HQ's automations. Pause one when it's wrong for this week, read the log when you wonder whether something sent, and ask for a new one when you notice yourself doing the same nudge for the third time.
What it is
Kitchen is the project platform. Chef is the overlay we install on top of it. Chime is the control room for the automations that run inside both: one card per automation (a chime), each with a switch.
How a chime works
- Each chime watches for one thing and does one thing: a card moving into a column, a date getting close, a client message going unanswered.
- It writes a line in the activity log before it acts, so nothing ever fires twice for the same card, message, or date.
- Messages go out from HQ Assistant, or signed Support Crew, into a thread a person already ruled as the right room. If a chime can't find a safe room or a routed consultant, it logs why and sends nothing.
- A paused chime keeps its place and its wording; it simply skips its turns until you switch it back on.
When to open Chime
- A message shouldn't go out this week. A client on hold, a consultant who's away: pause the chime that would reach them, and turn it back on after.
- You wonder whether something actually sent. The activity log shows every run, what it did, and who it reached. An exclamation mark means it couldn't, and says why.
- Monday morning. The overdue digest is the one screen for what's late and who's waiting on us.
- The wording feels off. Owner and Admin can edit any chime's message on its card. The change applies to the next send.
When to add a new one
- You've sent the same reminder or nudge by hand three times, and it always follows the same event or date.
- A client-facing message that should never depend on someone remembering.
- Tap + New chime: pick a template, or describe what should happen and when. Anything not built yet becomes a card in the build queue, and the template shows "Requested" until it's live.
- Not a job for a chime: money, deleting anything, changing someone's access, or any message a client would find strange to get from a bot.
Who can do what
Kaneisha (Owner) and Kie (Admin) can switch, edit wording, add links, and ask for new chimes. Support Crew (Operator) can switch chimes on and off and read the log. Consultants and clients never see this page.
Start from a template
A template is a chime we already know how to build. Running ones can be paused from the Chimes tab; "Ask for it" puts an unbuilt one in the build queue and marks it Requested here. Start from scratch when none of these fit: say what should happen, when, and who should hear about it.
This makes a card on the Business Backlog for the build. You'll see it here as "Requested" until it's live.