What it does without being asked

The morning brief

Every business day, at 7am in your local time. It starts with what is stuck on you (the same six categories as the previous chapter), then the state of the plans and the team, the day's calendar, what came in by email, your personal list and, at the end, a short summary of news from your country and industry. If there are emails from the last 7 days that may be opportunities and that you haven't decided yet, a single line with the number comes in — Opportunities without a decision: N — pointing to the list in Orion › Emails.

It arrives through the channels you have connected — WhatsApp, Telegram — and by email too. When there is nothing to say, it stays quiet: empty day, no message. Weekends are silence too.

The end-of-day close

Every business day, at 6pm in your local time, and it comes built in — you do not have to create this routine. It is the mirror of the morning: what is still waiting on you, tomorrow's calendar and your to-do list. Same rule: empty, it stays quiet; weekend, silence.

Emails that may be an opportunity

Every hour, Orion looks at every email forwarded to it and tells you when one may be a business opportunity — whatever the subject, even from someone who was in a sequence months ago. It is one numbered notice with the likely ones (the maybe ones ride along, or go out at 12:00 and 17:00), from 7:00 to 21:00 on weekdays, at most 6 a day; the numbers run through the day. Reply with the number to log it, draft the reply or create a task — or decide in Orion › Emails › Opportunities, where all of them are, with the buttons. On the organization Admin's account, the likely ones from people who are not clients already go into CRM › Pending actions. At the start, a single message brought the count of what could be an opportunity in the previous 30 days. Details and limits in Connecting your accounts › Forwarded email.

The routines you created

The ones you accepted during setup, plus any other you ask for later: "every Monday morning, send me the pipeline summary", "on the 1st of every month, the month's sales close". They are all visible at Orion → Automations, where you see what each one does, how often, and can edit or delete it.

Where a routine you ask for in the dashboard, in the app or on a voice call reaches you. It reaches you on your WhatsApp, if it is connected to Orion; if not, on your Telegram — that is what the card shows under Where it reports. When you already have a routine with the same name and the card asks replace, both or no, the new one stays on the old one's channel (for example, on Telegram or in a WhatsApp group). In every case, the card's Where it reports line shows where it goes — check it before you answer.

A routine that repeats: Orion asks when to pause it, and keeps your request. When you ask for a routine that repeats ("every day at 9am send me a summary of such-and-such page") without saying on which days or hours it should not run, Orion asks before creating it — for example, whether to skip weekends or the small hours. If you already said it in the request ("Monday to Friday", "every day, weekends included"), it doesn't ask. Until you answer, nothing is scheduled, but your request is kept: if the conversation moves to another subject, it is not lost, and every reply from Orion ends with the line "📝 I have not scheduled … yet", with the routine's name and what is missing. Answer with the days or hours to skip, or "every day": then Orion creates the routine — or, in a conversation where it recently read outside content, first shows you its card, as explained in security and privacy. If the request changes a routine you already have ("move the morning summary to 8am"), the old one keeps running until the new one is created. But if, in the same message, you ask to cancel a routine and ask for a different one ("cancel the sales summary and create a purchases summary"), the cancelled one stops right away. The same routine at another time ("and at 6pm too") becomes a second request, kept next to the first, and a one-time reminder with the same name does not touch the kept request. If, in the reply that ends with the 📝 line, Orion also asked you a question, your yes or no goes to that question — even with a send waiting for your yes, which is neither sent nor cancelled by it. If you no longer want it, just say so. The kept request is not a routine yet, so it does not show at Orion → Automations; it is valid for 24 hours, and without an answer Orion lets you know the routine was not created — if you still want it, ask again.

A routine with the same name as one you already have: Orion asks. When Orion is about to create a routine with the same name as one already active in your account — ignoring accents, capitals and punctuation; for example, you said "change the summary to 10am" and it put together a new version without cancelling the old one —, it does not quietly create a second one. It shows you the card of the new routine ("You already have a routine with this name. Before I create another one, check the whole new one"), even in a conversation where it has read nothing from outside, and the card ends with the question, with the time of the one that exists: "There is already a routine "Daily summary" (every day at 09:00). Reply replace to swap the old one for this one, both to keep both, or no to discard this one." With two or more of the same name, it lists them all, and the answer to keep them is all ("both" does not count there, because three would be left).

replace (or swap, replace it, yes, replace): Orion cancels the old one — with two or more, all the ones the card listed — and creates the new one in a single step (it does both, or neither). The receipt says which times went away: "✔ Routine created: Daily summary — every day at 10:00…; I cancelled "Daily summary" (every day at 09:00)". To swap only one of several, answer all and then delete the one you no longer want at Orion → Automations (or ask Orion to cancel it).
both (or keep both) — or all: creates the new one and keeps the old ones; the receipt ends with "I also kept …", with each one's time.
no (or cancel): discards the new one; the old one stays as it was.

A yes on its own creates nothing: with two possible outcomes, it does not say which. The card comes back with "↩️ A routine with this name already exists, and a yes does not say whether to replace the old one or keep both — nothing was created or discarded. Reply replace, both or no." The answer must be just one of those forms — in Portuguese, substituir, as duas, todas; in Spanish, reemplazar, las dos, todas —, and it works like the yes to any card: only while the routine's card is Orion's last message. If another card came after it (a send's, for example), nothing is decided and the routine's card comes back, saying why. On the dashboard, the routine box shows the card with the question and, instead of Create, the choice buttons: Replace, Keep both (or Keep all, when there are already two or more with that name) and Cancel. Each button counts as the written answer — Replace swaps the old one for the new one, Keep both (or Keep all) keeps the old ones and creates the new one, and Cancel discards the new one —, and you can also type the answer in the chat. In the app, the card comes in the text of the reply, and you answer by typing. On a voice call, Orion reads the question, and you say replace, both (or all) or no. When you ask for the swap yourself ("cancel the 9am summary and create one at 10am"), the card already says what the new one replaces, and the yes is enough. And where the card cannot be shown to you — a routine requested by email, or on a voice call in which Orion does not read the card —, the routine is created as before, but not silently: the reply ends with "ℹ️ You now have 2 routines named "Daily summary": every day at 09:00 and every day at 10:00 (the new one). The one that already existed was not replaced — if you meant to replace it, ask me to cancel the one you no longer want."

A request made while a routine card is waiting: it is not lost. In each conversation, only one new-routine card waits at a time. If, while one of them is waiting for your answer, you ask for another routine or reminder that also needs a card — in a conversation in which Orion recently read outside content, or with the name of a routine you already have —, Orion neither swaps the waiting card nor schedules the new request: it is kept, the waiting card becomes the last message again, and every reply from Orion ends with the line "📝 I have not scheduled "Dentist appointment" (once, Fri 10/02/2026 10:00) yet: the request is saved and goes ahead as soon as you answer the card for the routine "Daily summary"." When the first card is decided — by yes, by no or by the same-name choice — or expires, Orion takes the request forward on its own, with the line "📝 The request "Dentist appointment", which was waiting for that card, goes ahead now: check its card.", and its card comes right after. Nothing is scheduled before your answer to that card. With more than one request kept, they go ahead one at a time, in the order you asked. If the new request is the same routine as the card with another time or another text ("make it 8am"), it replaces the card, as before; and, in a conversation without outside content, a different routine, with a name you do not use yet, is created right away, as always. The kept request is valid for 24 hours: if it has not gone ahead by then, Orion tells you it expired and nothing was scheduled — if you still want it, ask again. If you no longer want it, just say so.

Orion does not say it scheduled what it did not schedule. If one of its replies says a reminder or a routine is scheduled or confirmed without that having been done or checked in that reply, the system makes it review the reply before it goes out; if the sentence stays, the reply arrives with the line "⚠️ In this reply I did not schedule or check any reminder or routine — if anything above says it is scheduled or confirmed, that was not verified now." What actually exists is at Orion → Automations, or ask for the list of your routines.

When a routine doesn't run

If one of your routines can't run, you'll know: silence never means "it failed". Orion sends a short notice on the same channel you talk to it on (WhatsApp or Telegram; if you have neither, by email). The notice gives the routine's name, says it didn't run this time and gives the reason in a few words. One exception: through the Orion contact, if you haven't written on that line in the last 24 hours, WhatsApp only allows an approved template, and the notice arrives shorter — just the routine and the reason, without what to do; reply to it and Orion explains the rest. It's one notice per routine per day, even if it fails at several of its times.

Temporary disruption. It already tried again and couldn't. The routine tries again on its own at its next scheduled time. If you need the result sooner, just ask. For a monthly routine, this month's run won't repeat on its own: ask if you need it. A one-time routine won't repeat either: ask again.
Your organization's AI key was rejected, ran out of credit, or isn't on file (for organizations that bring their own key). The notice says what to do (and, if the key was rejected or ran out of credit, which provider your organization chose): whoever manages the subscription replaces, tops up or adds the key under Billing › Organization AI key. Because that key serves every routine on the account, you get only one notice a day for routines that repeat: it's the notice for the first routine that fails, and it says the others won't run either until the problem is fixed. A one-time routine and a monthly one each get their own notice, because they don't come back on their own: once the key is fixed, ask again. One that had already started acting also gets its own, so you can check what it already did.
Another error. Ask again; if it keeps happening, get in touch with us. Our team is already alerted automatically.

If the routine had already started acting when it failed, the notice says it started but didn't finish and that some actions may already have been carried out. Check before asking again, so nothing is done twice.

Automatic pause. If the key is rejected (or out of credit) three times in a row for the same routine, Orion pauses the routine so it doesn't keep trying for nothing, and tells you once. It runs again on its own, on its schedule, as soon as the key is replaced. If the problem was credit and the same key was topped up, it tries again once a day, and the routine comes back when that works. Nothing needs to be reactivated. The pause doesn't show under Orion → Automations: the routine stays listed as usual, and Orion simply skips its runs while the key doesn't work.

When no notice comes. When the routine decided there was nothing to send (for example, an alert routine whose condition didn't happen): that isn't a failure. And when it prepared a send that is waiting for your confirmation: the confirmation request arrives as usual and the failure notice isn't sent with it, so your yes still applies to that send.

Automation proposals

When it notices you repeating a request (the detector only fires from three occurrences of the same pattern), it proposes automating it: "I noticed you tend to ask me for tomorrow's calendar around 7pm — want me to start sending it on my own at that time?". You answer yes and it sets it up, or you give it another time.

Delivery is limited on purpose: at most one proposal per day, and always in your morning — never at midnight.

Deliverable risk alerts

Every day it computes a risk per deliverable, from data that already exists: a deadline past due with progress below 100%, a pace below what is expected for the point in the calendar the deliverable is at, and progress frozen for several days in a row. The ones that land in the highest bands show up in the morning brief, with a short sentence saying which signal fired.

It does not invent risk: no data, no alert. And the "progress frozen" signal requires at least four days of history before it fires — on a freshly created deliverable it stays quiet on that point, instead of guessing.

What AI can take over

It reads the description of your team's active tasks and sorts each one into three groups:

AI does the whole thing: send an email or a message, book a meeting, create a form, extract, structure or summarize a text, set up a reminder.
AI does the draft: write a document, report or plan, analyze data, create content, research options — always with a human reviewing and approving.
Human only: a decision, an approval, a signature, on-site work, human production, or the technical work of your company's professional domain (an engineering design, a legal filing, a medical report).

When the description is too vague, it classifies it as human. It never overestimates automation.

From there it makes an offer, and the offer comes split into two lists:

✅ I can get these moving now — I already have enough:
1. Write the launch announcement
2. Build the tracking spreadsheet

📎 For these I need you to send me an input:
• Review the contract — I need the base material

You answer "go ahead with 1" or "all of them". Two deliberate locks: it only makes the offer when it has at least one thing it can really move forward — there is no message that just asks for a document — and at most one offer per week.

And if your team's work is almost all technical work in your domain (engineering, legal, healthcare), the classification will come out "human only" on almost everything and that offer never arrives. That is the correct behavior, not a failure: it would rather stay quiet than offer to do what it does not know how to do.

The relationship radar

Once a week it reminds you of the people you are losing touch with. The dial has three positions, and you change it by talking:

off: no proactive relationship nudges. "turn off the relationship nudges."

light (default): a short weekly reminder, with the few most overdue people.

more: a fuller weekly reminder, including who is coming up on the time to reconnect. "tell me more about keeping in touch."

How to turn off what you do not want

It is worth knowing what each control really does, because they are not interchangeable:

The relationship dial (off / light / more) is what controls the contact nudges. Ask for the change in plain language.

Orion → Automations is where you edit or delete any routine that has been created — from the dashboard or from the conversation.

STOP, on WhatsApp, turns off the re-engagement track — the come-back messages for people who have drifted away — and only works for someone already on that track. If you are not, the word reaches Orion as any other message. STOP does not turn off the relationship radar, nor the morning and end-of-day briefs.

The news roundup (every two months, by email) is switched off through the unsubscribe link in the footer of the email itself. That same link has an option to leave all Orion emails — which is today the only path that also silences the operational morning and end-of-day briefs.

The email opportunity notice follows the morning brief: whoever leaves all emails through the footer link stops getting it — and the single message about the previous 30 days too; the classification, the list and the CRM keep working. To quiet one person only, use Not a lead on the list: their maybe stops interrupting for 90 days (on a request that arrives without the writer's own address — a form, a social network, a forward —, the mark applies to that email only).