> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appeeky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Always-on

> Short alerts when something urgent happens, and routines the Co-founder runs on a schedule you set.

The briefing is the deep dive. **Always-on** is what the Co-founder does in between:

* **Alerts**: when something urgent happens, it looks into it and sends you a 3–4 line message with the fix already queued.
* **Routines**: jobs you hand it in plain language, such as "every Monday at 9, check what competitors changed", which it runs on schedule.

Anything an alert or a routine wants to change waits in your [action queue](https://docs.appeeky.com/docs/cofounder/actions-and-approvals.md) for one-tap approval.

> [!NOTE]
>
> Always-on is included with every Co-founder account. Manage it in **App Co-founder → Always-on**; tune alerts in **Settings → Always-on**.

***

## Alerts

These events can interrupt you between briefings:

| Event | Example |
| - | - |
| **Anomaly** | Downloads or revenue far outside their normal range |
| **Churn spike** | A wave of cancellations, billing failures or refunds |
| **Review crisis** | One-star reviews spiking, often right after a release |
| **Your own event** | Anything you send to your [custom webhook](https://docs.appeeky.com/docs/cofounder/api.md#custom-webhook) |

For each one, the Co-founder checks what's behind it using your store data, reviews, ranks, competitors, recent changes and what you've already told it. Then it either sends an alert with what happened, the likely cause and the one thing to do now, or stays quiet when it turns out to be noise, a known data delay or something you already explained.

Every event still goes into your next briefing.

### Alert settings

| Setting | Default | What it does |
| - | - | - |
| **Send alerts** | On | Off means urgent events wait for your next briefing |
| **Alert me for** | High and critical | Or *Critical only* |
| **Alerts per day** | 3 | Over a rolling 24 hours. Critical alerts get 2 more. |
| **Quiet hours** | 22:00–08:00 | In your timezone. Non-critical alerts wait until they end. |

The Co-founder also sends at most one alert per app per hour, and holds a non-critical alert for your briefing when it is due within 90 minutes.

Alerts go to Telegram and the Appeeky mobile app when connected, and to email when neither is. Critical alerts are always emailed too.

***

## Routines

A routine is an instruction plus a schedule. Start from a template or write your own:

| Template | When | What it does |
| - | - | - |
| **Review triage** | Every evening | Sorts new reviews, flags bugs, drafts replies |
| **Competitor watch** | Mondays | What tracked competitors changed and what to do about it |
| **Keyword rank watch** | Every morning | Tracked keywords that left the top 10 or moved 5+ places, and why |
| **Experiment check-in** | Wednesdays | Whether each recent change is working: keep, revert or wait |
| **Ads spend guard** | Every morning | Campaigns and keywords spending without results, with the fix queued |
| **Release watch** | Daily | Ratings, reviews and crashes after a new version vs the previous one |
| **Friday wrap-up** | Fridays | The week in five bullets and the one thing to do next week |

Each routine either notifies you **only when something needs you** or **every run**. Use **Run now** to try one immediately, and pause or delete it at any time.

You can also create routines in chat, on any channel:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
You:  Every weekday at 8:30, check if any competitor changed their price.
Co-founder: Done. "Competitor price watch" runs weekdays at 08:30.
            I'll only message you when a price moves.
```

### Limits

* Up to 20 active routines and 24 routine runs a day.
* A routine that fails three times in a row is paused until you resume it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.