Automations

An automation is anything KKHS Assist starts for you later or when something happens. It might remind you once, run every morning, react the instant a message arrives, or move through several steps over a few days. You describe the outcome; KKHS Assist chooses how to run it.

You do not need to decide whether something is a reminder, routine, trigger, or workflow. Those are implementation details. They all appear on the same Automations page and use the same controls.

What you can automate

• A moment — "Remind me to renew the insurance next Thursday at 10."
• A repeating schedule — "Every weekday morning, summarize anything urgent in my client chats."
• A new message or reaction — "React ✅ when someone says approved in the Finance group."
• A condition that needs judgment — "Watch the supplier chat and tell me when the conversation sounds stuck."
• A sequence with waits — "Ask Ravi for the numbers Friday. If he has not replied by Monday, follow up. Tell me after the second miss."
• Connected work — "Update the Sheet first, then send the morning briefing only if the update succeeded."

Instant exact-match rules are immediate. Work that needs judgment runs in the background. Multi-step automations save their current step and answers, so a restart does not make them forget what they were waiting for.

Create one

Open Automations and choose a template, or describe the result in your self-chat. Templates draft a normal WhatsApp request that you can change before sending — there is no configuration language to learn.

For example:

The important parts are shown before anything sensitive goes live: what starts it, what it will do, who it may message, how long it waits, when it stops, and any connected-app changes. Automations that message another chat or change an external service stay off until you confirm them.

The Automations page

The left side is a compact library organized by the kind of outcome you recognize:

• Overview — failures and live runs first, followed by the next five scheduled starts and a compact summary of always-on watches.
• Active — every automation that is enabled and can still do work.
• Reminders — one-time nudges, repeating reminders, and recurring tasks you check off after each occurrence.
• Scheduled work — messages and assistant work that start on a clock.
• Watching — rules waiting for a message, reaction, or judged condition.
• Multi-step flows — sequences with durable progress and waits.
• Briefings — KKHS Assist's morning, afternoon, evening, and weekly digests.
• Off — saved automations that will not start anything new.

Open Reminders to see them grouped into one-time, daily, weekly, monthly, and custom cadences. One-time reminders stay here while pending; after they run, they leave the current automation inventory. A recurring task reminder also creates an open task for each occurrence, so its row says that it is something you can check off. A failed automation stays in its natural collection and in Overview, with the failure shown on that row and in its detail.

The detail adapts to the work. A simple reminder gets a compact schedule, message, destination, next occurrence, and edit form. Rules use a plain-language When and Do view. Multi-step automations get the full flow, current step, saved state, recent events, failures, and earlier runs.

Available controls depend on the automation: edit its name or schedule, switch future starts on or off, skip the next scheduled start, pause or resume a run, cancel a run, or delete the automation. Editing a multi-step definition affects future runs; an active run finishes from the version it started with.

Automations, agents, and background tasks

An automation has a specific start and action, even when it repeats. An agent owns a standing responsibility with a brief, watched chats, scheduled checks, and daily notes. A background task is one large finite assignment that gets checkpointed until it is finished.

You still do not have to choose: describe the outcome in plain language and KKHS Assist routes it to the right system.