Digest & Alerts
The two times Subscriby Copilot speaks first: a digest every Monday at seven in your own time zone, written in words from your week's figures with up to three steps worth doing, and an alert when a project breaks its own pattern (payments failing far more than usual, a day of cancellations, a payment rail on which every attempt failed). Where each reaches you, what they are written from, why neither costs anything, and how to route or quieten them.
Everywhere else the Copilot waits to be asked. Twice it speaks first: on Monday morning, with the week in words, and in the hour something on a project breaks its own pattern. Both are written from your figures and nothing else, both arrive where your other alerts do, and neither costs a turn or a cent.
The Monday digest
At seven on Monday, in the time zone on your account: what came in, who joined and who left, what needs you, and up to three steps worth doing, each with a button to its page.
An alert when something breaks pattern
Payments failing far more often than a project is used to, a day of cancellations, or a payment rail on which every recent attempt failed. Told once, closed by itself when it stops.
Never charged
No free turn and no Copilot Credits are drawn for either. The model call behind the digest is on Subscriby's own books.
The Monday digest
It arrives at your seven. The sweep runs every hour and sends the digest to the creators whose own clock has just reached seven on Monday, so a creator in Colombo and one in Lisbon each read theirs at breakfast. The time zone is the one on your account, under Settings → Profile.
It covers the seven days before. Your local week: Monday to Sunday, read across every project you own, with the week before beside it where a comparison makes sense.
It is written in your language. The Copilot is handed the figures and told the language of your account; it answers two to four short paragraphs, no headings and no bullet marks. A week with nothing in it, no members, no payments, no movement, sends nothing.
It ends with what to do. Up to three steps, chosen from a fixed list and each with a reason in a few words: review members at risk, follow up failed payments, read why members cancelled, welcome new members, check trials ending soon, answer waiting members, teach the Copilot, check your bot, top up Copilot Credits, or simply open the dashboard. Each step is a button to the page on your own dashboard; the Copilot names the step, never the address.
What it is written from
| Figure | Read from |
|---|---|
| Revenue in US dollars and how many payments it came from, against the week before | Your successful payments, restated at the day's rates |
| New members, new purchases, cancellations and why, against the week before | Your members and purchases, and the cancellation screen's answers |
| Members active today, and trials ending within the coming week | Your purchases as they stand on Monday morning |
| Renewals that failed, the ones paid after all, members in a grace window today, access paused for non-payment | The Revenue Recovery ledger |
| Members waiting for an answer | Your support inboxes |
| Installations the health probe finds degraded | Your connectors |
| Entries on your Knowledge pages, free turns left this month, Copilot Credits left | Knowledge and Billing, so the steps can say when to teach it or top up |
Several projects give the digest a line per project, the busiest first, and the steps name the project each is about. The figures are kept with the digest, so what you were told can be read back against what the dashboard showed.
If the model does not answer
A Monday digest that depended on a model being up at seven would miss mornings. When the writer fails or answers nothing, the same figures are stated in plain sentences, in your language, with the steps chosen by rule, and the digest arrives all the same. The digest records which wrote it.
The alerts
Between Mondays the Copilot reads every project with something to read, once an hour, against the project's own four weeks before, so the line is yours and not a number that fits nobody.
| Signal | Over the line when | Opens |
|---|---|---|
| Failed payments | At least three attempts failed in the last day, a quarter or more of them, and at least twice the four-week rate | The Revenue Recovery activity page |
| Cancellations | At least three in the last day, and at least three times the four-week daily average | The cancellations page, with the reasons members gave |
| Payment rail errors | At least three attempts on one gateway in the last six hours, every one failed | Your payment methods, to check the gateway's credentials and standing |
An alert is told once, when it opens. While the signal lasts the alert stays open and nothing is sent again; when a pass finds the signal back under its line the alert closes by itself, and a signal that returns later opens a new one. A degraded bot or channel is not an alert here: the recovery program tells you the moment a probe finds one, and the digest mentions it rather than a second notice repeating it.
Where they reach you
Always in the bell
Every digest and every alert lands in the notification centre, whatever else you route.
Email, when routed
Both belong to a new alert class, Subscriby Copilot, in Settings → Notifications → Alert destinations. Tick Email for it and the digest and the alerts arrive by email; with no connected account, email is where they go.
Your connected account
Tick a connected account and your platform bot carries them, the digest with one button per step, signed so a tap opens your dashboard already signed in.
The class is not one of the critical ones, so unticking everything but the bell is allowed: the digest and the alerts then wait for you in the notification centre and nowhere else.
What it costs
| What arrives | Costs |
|---|---|
| The Monday digest | 0 |
| An alert | 0 |
Neither draws a free turn nor a cent of Copilot Credits, on any plan. The tokens the digest's model call used are recorded with the digest for Subscriby's own books, the way a turn's are.
Questions
Related
- Notifications — the alert destinations grid, where the class is routed
- Revenue Recovery — the ledger the failed renewals and recoveries come from
- Turns & Credits — what is and is not charged
- Subscriby Copilot — the operator, surface by surface
How is this guide?
Last updated on
Copilot in Your Inbox
A reply drafted on request in the Support Inbox: the button beside your saved replies, what the draft is written from (the thread, the member's standing, your saved replies and the Knowledge passages that match) and what it is never given, Use and Dismiss, the $0.05 it costs and where that comes from, who may ask, why a member's message can never steer it, and the per-project switch that lets the Copilot answer a member's own-subscription questions and what your Knowledge covers itself.
Capabilities
Every area the Copilot reaches, grouped the way you run a membership: your business, your members and money, growth, and operations. For each area, what runs at once (reads and new things), what waits for your confirmation (changes, removals, sends and payments), and requests you can type as they are.