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. Without a subscription it changes a little — see No subscription, at the end of this chapter.

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.

In your language. The greeting, the headings and the fixed sentences of the brief come in your account's language — the same as the messages Orion sends on its own (see Language in connecting channels) —, and so does the news. What comes from your data, like a team's name, a plan's title or an email's subject, comes as it was written. For now, the details next to each pending item — like «(ciclo 3) — vence 15/08» — and the MEI section, which only exists in Brazil, stay in Portuguese.

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. And it comes in the same language as the morning brief.

The calendar in both briefs is the same as in the conversation. In the morning and at the end of the day, it reads the same calendars it reads when you ask: the main one of the connected Google account and every calendar checked in it, except holidays and birthdays (see connecting accounts). The same event on two calendars shows up only once, up to 20 per day; beyond that, the brief says how many were left out. An event that comes from a calendar that is neither the main one nor yours (a colleague's or the clinic's, for example) carries that calendar's name in parentheses. If a calendar could not be read, the brief says which one, instead of showing half the calendar as if it were whole.

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.

Deadlines and entitlements in your country

The morning summary can bring deadlines and entitlements that are yours — the tax coming due, the benefit that opened, the filing that needs attention. For that, Orion needs three things only you can state, and they live in Orion › Deadlines and alerts (or in My Profile › Deadline tracking):

The country of obligations. Not your address: where the deadlines that bind you come from. Someone living abroad who still files in Brazil picks Brazil, and someone with obligations in more than one place picks the one that weighs more.
Your life stage. It keeps you from getting what belongs to another age. Blank: you get only what applies to everyone.
How you work — self-employed, employee, sole trader (MEI, for clients in Brazil), business owner or executive. More than one is fine, and marking more doesn't bring more noise: it brings what is yours for more than one reason. Blank: you get only what doesn't depend on this.

Until you state them, none of this enters your summary. That isn't an oversight: without knowing which country your obligations are from, any deadline we sent would be a guess, and staying quiet beats sending what doesn't apply. Stating them is the step that depends on you; the flag enters the morning summary once there is a deadline of yours to flag.

You can say you don't want it, and that is different from not answering. Choose No thanks and the matter closes: we won't ask again. Leave it blank and Orion may ask once more later on — inside a conversation you started, never as a message out of the blue, and never after a “no”. Changing your answer is the same path, any time.

The pages and notices you track yourself

Beyond the deadlines Orion already knows, you can point it at your own sources — your professional board's page, the union's noticeboard, the city hall notice, the school's circular. In Orion › Deadlines and alerts, paste the address and say whether it is a page or an RSS feed. Up to 10 sources.

What Orion does with them is tell you WHAT changed — and nothing beyond that. It splits the text into passages, keeps a fingerprint of each and compares them on the next read; passages that did not exist before show up on your page, with the link. In a feed, those are the new titles. ⚠️ No model reads these pages: Orion compares fingerprints, it does not interpret. It does not summarize the page or form an opinion about it: the wording is yours to read at the source.

Today the reading happens when you add the source, and the automatic alert does not exist yet. Orion opens the address once, at the moment you add it, and the page Orion › Deadlines and alerts is where you see what changed. It does not yet wake up on its own to re-read your sources, which is why it does not promise to warn you — when that exists, this chapter will say so.

You can also ask for all of this by talking. Say “follow this page: https://…”, “which pages am I following?”, “stop following the union one” or “I only care when budget shows up”, and Orion does the same as the page does, on your own list and nowhere else. ⚠️ In conversation it tells you that a source changed, never what changed: the passage stays on the page, for the same reason no model reads these pages.

You can say what matters to you. If a page changes too often (a blog, a list of news), write the words that count — workers, budget, deadline — and Orion only counts it as a change when one of them shows up. Left empty, any change counts. The screen always shows which state each page is in, because a filter nobody can see looks like a fault.

The first read is never a change. Just added it? Orion stays quiet until there is something different.
Orion checks the address right away. As soon as you add a source, it tries to open the page once and tells you there and then whether it answered — including when you ticked RSS and the address is not a feed. If it doesn't answer, the source is added anyway and the reason stays in the list: a page that is down at that second is not a wrong address.
A source that is down is silence too. If the page doesn't answer, it doesn't flag it — it keeps the reason and you see it in the list. Flagging every stumble of somebody else's internet would be noise, not service.
The address must start with https://. A device address or a network number is refused, and the screen says why.
Removing a source doesn't erase what it already learned: put it back and you won't get a «changed» flag just for that.

This is yours, not the organization's. Your sources appear only to you, even if your account has a team.

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 live at Orion → Automations, where you see what each one does, how often, and can edit or delete it.

The routine you ask for in a conversation is yours, and you stop it from the conversation. Every routine asked for in a conversation, in the app or on a voice call is born personal: it depends on your plan, it shows at Orion → Automations under Mine, and only you see what it does. To stop it, just say so — "cancel the daily summary". It stops running right away and sits paused on the page, where you switch it back on whenever you want; nothing is deleted. If you have two routines with the same name, Orion asks which one instead of choosing. The organization's routines do not stop from the conversation: those are changed and switched off on the page. And if, at the moment you ask, your monthly run credit no longer fits one more, the routine is created and kept saved, switched off — Orion says so right away instead of promising a time that will not happen, and you switch it on from the page once there is credit.

Whose routine it is: the organization's or yours. When you create a routine in the panel you choose between the organization's and personal, and that choice decides three things. Who sees it: the organization's one appears for everyone in the organization, with its name and what it does; a personal one appears only to you — whoever administers the organization can see that it exists, whose it is, and can pause it, but does not see the name, what it does, or what it has already done. Which plan it depends on: a personal one depends on your plan; the organization's one depends on someone in the organization having a plan — the organization has no plan of its own, its people do, and one active plan is enough. Where the AI capacity it spends comes from: the organization's one spends the organization's; a personal one spends yours. The page separates them into sections — The organization's, Mine and, for whoever administers, Other people's —, and the choice is made at creation and does not change afterwards — switching would change who sees the routine and where the spending comes from, so for the other kind, create another one. A personal routine does not write to anyone outside the organization: that is an act of the organization and has the four rules further below; in the panel, the block that writes outside appears blocked while the routine is personal, with the reason written right there.

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.

Asking for the channel in the conversation. If you say by email in the request itself — "every day at 8am send me the summary by email" —, the routine delivers by email, to the address on your account, and never to an address written in the request. The confirmation says where it arrives, and, when the card appears, so does its Where it reports line. If the confirmation does not mention email, the channel did not go in: ask again, saying by email. Asking for a summary of your emails is a different thing — there email is the source, not the destination, and the answer reaches you on your usual channel. For the routine to email another person, see When the routine writes to someone outside, further below.

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 — and that list comes complete: the routines you asked for in the conversation and also the ones on Orion → Automations, these marked as being from there. Your own you can also stop from the conversation — "cancel the daily summary" —, and the organization's are changed and switched off only there.

When the routine writes to someone outside: the approval is yours, step by step. A routine can, after answering, email a person who is not in the organization — from the email account the organization connected, so it goes out in the organization's name. That is different from everything else a routine does, and so it has four rules. First: an Admin of the organization or the account owner is who creates and approves it, and the routine has to be the organization's — a personal routine does not write outside. In the panel, under Orion → Automations, a routine is built out of blocks — you add a block, choose its type and fill in its fields — and for anyone who cannot approve it, the block that writes to someone outside appears locked in the list, with the reason written right there. Second: the address is fixed, and it is what you approve — Orion does not pick the recipient at send time, and changing the address later asks for a new approval, because approving the routine does not approve a recipient that came in afterwards. Third: the approval is a box you tick, and it counts in full — without it the routine does not even save; with it ticked, saving creates the routine already switched on, and the first send happens at the next time in the interval you chose. The form says so before the click, and the card says, in the same sentence that tells what it does, who the email goes to. Fourth: the email text is yours, and you approve it once — you write the subject and the body when you create the routine, and Orion does not rewrite them: it does not swap your words for others or summarize what you wrote. If the text carries a part that has to be filled in with something an earlier step found, and that is not available at the time, nothing is sent: the routine stops and says what was missing, instead of sending an email with a hole in it. What Orion found reaches you, on your channel. It is recorded who approved it and when.

How much your routines can run per month. The limit is not how many are switched on: it is how many times they run per month, added up. There are two credits, counted separately: one for the organization's routines and one for your own, per person. Yours comes from your plan; the organization's is the same for everyone. Each routine costs whatever its own cadence asks for: one that runs hourly costs 720 runs per month, a daily one costs 30, and a one-time reminder with a date costs 1 — it is no longer exempt, it is simply cheap. The Orion → Automations page itself shows the cost on each card and, in each section, how much of the credit is already committed; the The limits on this page block gathers the numbers in one place. Because the cost depends on the cadence, the button to switch one on appears blocked when that routine does not fit in what is left, with the reason and the numbers beside it — there may be room for a daily one and not for an hourly one. Pausing a repeating one frees runs, and picking a wider interval costs less. One credit does not touch the other — the organization with no credit left does not stop your first personal routine. With no active subscription the credit is zero, and nothing runs. Creating has no limit — what you built stays saved, switched on or not. Beyond the credit, each routine has its own cap on runs per month, which exists to stop a loop and is the same on every plan; and at least 15 minutes pass between one run and the next — at that cadence, a single routine costs almost 2,900 runs per month.

In a very busy minute, a routine may go out a few minutes late — never early. When many routines come due in the same minute, Orion releases them at the pace the AI accepts, so that none is turned away along the way and whoever is talking to Orion at that moment is not kept waiting. The ones that do not fit in that minute go out in the following minutes, in the order they came due.

When a routine doesn't run

If one of your routines can't run because of a disruption, an error, your organization's AI key or because your plan's AI capacity has run out, you'll know: in those cases, 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.
Your plan's AI capacity has run out (today's or this month's). The routine doesn't run at that time and isn't redone later: it comes back at its next scheduled time, at the usual hour. You get only one notice a day for the whole account: it names the first routine that didn't run and says the others won't run either until the capacity comes back — the next day, or when the month turns over. To resume sooner, whoever manages the subscription — your organization's billing manager — can change the plan in the dashboard, on the Billing page. A monthly routine gets its own notice: this month's run didn't go out because of the limit and isn't redone, and the routine carries on next month, on its usual day and time. A one-time routine gets its own notice: it didn't run and won't repeat on its own — once the capacity is back, ask again.
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 switched on, its last run shows as Refused, with the reason, 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.

No delivery channel. If your account has neither WhatsApp nor Telegram connected to Orion, the routine doesn't run, and nothing is spent. Your business's service number doesn't count: it only talks to your customers. The Orion contact on WhatsApp doesn't carry routines at a set time either (see connecting channels). The first time, Orion sends one notice per routine, to your account's email or, if you talk through the Orion contact, there, and one that repeats is paused: under Orion → Automations, its card says why. It resumes on its own, within 15 minutes of a channel being connected, if the plan and the run credit still allow it; if not, it stays paused, and you switch it on from the page. If its time came while it was paused, it runs once right after resuming, as when it's switched on from the page, and then keeps its schedule. A one-time routine won't repeat: connect a channel and ask again. To get it by email without connecting a channel, set Where the answer goes out to email under Orion → Automations and switch the routine back on. The notice doesn't repeat: it only comes again if the routine runs and later ends up without a channel again.

No active plan, or a suspended account. The routine doesn't run and sends no notice. Without a plan, one that was on is paused and doesn't come back on its own — see No subscription, below. With a suspended account, the routine stays on and runs again at its time once the account is reactivated.

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. (Only for someone with a subscription.)

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. A third one, about the subscription: the offer doesn't go out in an organization without a subscription (or that pays only for a plan without the team dashboard), nor to someone without Ask Orion.

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."

Usage ideas

From time to time, Orion sends a usage idea: something it can do, told as a short everyday case, ending with Try it yourself and the first step to try it. The idea goes only to whoever owns the Orion, in their conversation with it — never in a group, never to one of your clients — and comes in your account's language.

When. Around 10 a.m. your local time. In the account's first two weeks, every day; until the end of the second month, every other day; after that, every three days. The count starts from the beginning of your account, not from the last idea.
No piling up. If Orion already sent another message on its own that day — the trial-period ones, a come-back message, the news roundup or, for clients in Brazil, an obligation reminder of the MEI —, the idea moves to the next day. The morning and end-of-day briefs do not count.
Each idea, only once. Whoever has Orion MEI or MEI+ (for clients in Brazil) gets the ideas written for the MEI; the other plans, the general ones. When they run out, the ones about features you do not use yet come back — such as a connected calendar, Instagram, the customer-service number, Radar or an AI worker.
Outside your plan. If the idea is about a feature your plan does not have, it ends with a line saying which plans have that feature.
Where it arrives. On the channel where you talk to Orion: your WhatsApp, Telegram or the Orion contact — never by email. Through the Orion contact, if you have not written in the last 24 hours, WhatsApp only allows an approved template: a short invitation with the idea's title arrives, and the whole idea comes right after you reply with anything, within 24 hours (your reply reaches Orion as usual). If an invitation goes unanswered, the next one only comes after you write to Orion again.
Without a subscription, it does not arrive.
Instead of the come-back messages. Whoever has already received an idea no longer gets the come-back messages of the re-engagement track, which would say the same thing.
To stop, reply STOP — just the word — in your conversation with Orion. The confirmation comes in your account's language, and you stop getting both the ideas and the come-back messages. See How to turn off what you do not want, at the end of this chapter.

No subscription

What it means to have no subscription — the organization or the person — is in No subscription. In this chapter, the following changes.

The morning and end-of-day briefs continue, with the calendar, your list, what is waiting on you and the deliverables at risk. In an organization without a subscription, the state of the plans comes only with what was already written (no new Situation is generated), the AI can help block goes away and the deadlines show as paused; in an organization that pays only for a plan without the team dashboard (MEI and MEI+, in Brazil, or Orion Light, outside Brazil and paid by card), the deadlines run, but the Situation and the block stay the same way. And, if you are the one without a subscription, the email part brings only the count — without the reading of the ones that deserve attention —, the brief comes without the news and without the AI can help block, and under Needs you (at the end of the day, Still needs you) what you cannot sign or assess shows a 🔒, with the reason once at the end of the block. Under Stuck with others, a plan waiting for acceptance from someone without a Y Managers subscription comes on a line of its own, without the Worth a nudge: that person can't sign until they have a plan or seat.

These don't happen without a subscription: the automation proposals and the usage ideas, for whoever has no subscription; and, in an organization without a subscription or that pays only for a plan without the team dashboard, the What AI can take over classification and the I can get these moving now offer. Deliverable risk alerts continue: they are a calculation, with no AI.

Orion doesn't ask for what you can't do. Whoever has no subscription in Y Managers doesn't get a request for an act that would show a 🔒: the daily reminder to sign a work plan, the one-click link to sign a plan or approve an AI worker's renewal, the submit your report at the turn of the cycle, the chasing of a decision coming due (due soon, due today, overdue), the invitation to log the why of a deviation or a plan's lessons, the Cycle with no report — ready for your feedback notice and the AI manager's proposal on WhatsApp. What is still pending shows in Waiting on you, with a 🔒 and the reason. Whoever has access gets everything as before.

Repeating routines stop. Without an active subscription in the organization, a routine cannot be switched on: the button appears blocked, with the reason written, and what you built stays saved. And a routine that was already on when the subscription stopped being valid stops running on its own, within minutes: its card turns to paused, and the last run is recorded as refused, with the reason. When the subscription comes back, you are the one who switches it on again — Orion does not switch back on, by itself, what stopped for lack of a plan.

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. The routines you already had moved to this page, keeping their time, their quiet hours and their date; the ones that fire once only show the date and switch themselves off afterwards. When you create one you choose between every (hour, 12 hours…), once on a date, or every month on a day, for as many times as you want — and you can pick the time, to the minute. You can create and switch on in one go, or create it turned off, to build it bit by bit and switch it on later from its card — an automation that writes outside the organization doesn't get that second option, because there the approval and the switching on go together. You can also pick where the answer goes out — WhatsApp, Telegram or email, and with email it arrives at your account's address, never at an address written in the request — and who it goes to: blank, it reaches you; pick a group and everyone in it will read what the routine writes, which is why it then requires the same explicit approval as anything leaving the organization. Email and a group don't go together: email reaches you, at the account's address, so picking one of them disables the other on the page, with the reason written there. The edit form opens on the routine's own card, and saving an edit switches nothing on or off: the routine stays as it was, and the switch is the button on the card. Duplicate creates a new routine with the same steps, for when you want a similar one without redoing everything — the original is unchanged. And See runs, also on the card, shows the history: when it ran, what happened each time and, when something stopped it, the reason.

STOP turns off the usage ideas and the re-engagement track — the come-back messages for people who have drifted away — and only works for someone who gets one of the two. It works in your conversation with Orion, on WhatsApp (your own number, the number dedicated to Orion, or the Orion contact) or on Telegram, and only your word counts: if a contact, a client or someone in a group writes STOP, nothing changes for you, and the word reaches Orion as any other message — the same happens if you get neither of the two. The confirmation comes in your account's language. Through the Orion contact, these messages only arrive while the conversation is open (when you wrote in the last 24 hours); otherwise they go only by email or Telegram, if you have them, and without those they wait for a day when the conversation is open. STOP does not turn off the relationship radar, nor the morning and end-of-day briefs.

Deadline tracking is switched off in Orion › Deadlines and alerts (or in My Profile › Deadline tracking) by choosing No thanks — and then the question won't come back. Leaving it blank is not saying no: it means no tracking, and being asked once more later, inside a conversation you started.

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).