Orion Workers Manual

Two halves, one product

The app lives at orionworkers.com. When you sign in you see a sidebar with two main entries: Orion, your agent's hub, and Y Managers, the team-management home. These are not two products talking to each other through an integration: they are two surfaces on the same database.

Orion — the manager you talk to

Orion takes over the day-to-day operational work so you can go back to leading. You talk to it in plain language, the way you would talk to a manager you trust: "how does my calendar look tomorrow?", "create the deliverable Launch Campaign for the Marketing team", "who on the team is stuck waiting on someone?". There are no commands to memorize.

It acts on the operational work and asks when an important piece of information is missing. And before answering about your business or about the platform, it is instructed to check the live sources — its memory, the manual, the knowledge base — instead of answering off the top of its head.

There are four conversation channels: WhatsApp (the main one), Telegram, the dashboard chat and voice in the mobile app. It is one single conversation: what you started on WhatsApp continues in the dashboard, and vice versa.

Y Managers — where the team's work lives

Y Managers is the structured half. It exists because a conversation is not a record: somewhere it has to be written down what the team committed to deliver, who does what, and how it went.

Deliverable

the result the organization wants — a project with an end date, or a recurring process that never "finishes at 100%" (monthly sales, NPS, availability).

Team deliverables plan

the set of deliverables a team takes on in a period, signed before the work starts.

Work plan

the individual commitment of one person (or of an AI worker) within that period — which deliverables they touch and with how much of their effort.

Cycle

the accountability window inside the work plan. The participant submits a report, the manager gives back an assessment and feedback, and the participant can request a review.

Around that sit the people, the teams, the periodic reports and the strategic grouping of deliverables.

Why the two halves are the same account

Because Orion works on top of Y Managers. It is not a chatbot sitting next to the system: it reads and writes the same records you see on screen.

In practice it looks like this:

• "Which of the team's deliverables are late?" — it answers with your organization's real deliverables, not with an estimate.
• "Add the task 'review the copy' to the Campaign deliverable." — the task shows up on the deliverable, in the dashboard, for anyone with permission to see it.
• "What is waiting on me?" — it lists what is actually stuck in your name (plans to sign, cycles to assess, and more) and resolves it right there in the conversation.
• "Record the decision: we prioritized X because Y." — it becomes precedent, and its next decisions come out more like yours.

The reverse holds too: everything Orion does by message shows up in the dashboard, with the record of who decided what.

The quick tour — what Orion does for you

Calendar, email and documents

checks and books appointments on your calendar (Google or Microsoft 365), sends and replies to emails on your behalf, creates documents and spreadsheets and hands you back the link. On Google Drive, giving someone else access is up to you — it creates the file but does not hand out permissions; on OneDrive it can generate a sharing link.

Work and team management

creates and tracks deliverables and tasks with deadlines and percent complete, builds deliverables plans and work plans, follows cycles and assessments. It warns you when a deliverable starts to smell like it will be late, before it turns into a problem, and points out which of the team's tasks are a case for AI — offering to run or draft the ones that fit.

CRM and relationships

a register of clients and contacts, sales pipeline, next contact scheduled, duplicate-contact alert. A radar keeps an eye on the people who matter to you and gently flags who is going cold. The intensity of those nudges has three settings, which you adjust by asking it.

Personal organization

a to-do list, reminders at a set time and long-term memory — "remember that my company focuses on SMBs of 50 to 500 people".

Automatic routines

a morning summary, an end-of-day close, recurring reports. Anything you would do every day or every week, it does on schedule. And when it notices you repeating a request, it offers to automate it.

Research and files

searches the internet with sources, understands audio you send (great in traffic) and reads documents, spreadsheets and images sent in the chat.

Your dictated notes

what you recorded in Audio to Notes — dictations and meeting notes — it reads in the conversation: "what did I dictate yesterday?", "summarize the note from the meeting with that client for me". Recording still happens in the dashboard: it reads, it does not record. And it is honest about the state of the note — if the transcription was left in doubt about a name or a number, it does not repeat that detail as fact, and if the note is still being processed it says so instead of inventing the content. That reading only exists in your direct conversation with it: in a group, or in work run by an AI worker, the notes stay out of reach.

Customer service and groups

with a dedicated number, Orion can serve your clients on WhatsApp with a public role you define, escalating to you whatever needs a human. On that same number, it runs your survey (an intake form, a screening or a satisfaction survey) inside the conversation, one question at a time exactly as you approved it, and keeps the answers with the questions document — see Run a survey on your service number. In groups you authorize, it takes part when called with "@orion".

A team that can also be AI

beyond managing people, Orion manages AI workers, who join the team with a work plan of their own and account for themselves like any other participant — under an autonomy policy you define. That is the Part about the AI team.

Without a subscription. Nothing of yours is lost: the CRM, memory, knowledge, the Google and Microsoft connections and search continue, and Y Managers stays open to read, edit and log progress. What stops is creating, signing and generating in Y Managers, Ask Orion and everything Orion would do for you with AI: the answers from knowledge and the library; in prospecting and on LinkedIn, the writing and the reading of replies (and, with it, the automatic booking of meetings); the summary of 🟢 groups in the CRM (only presence is kept); automation proposals; the reading of the emails that need attention and the news, in the morning summary; background work; and Orion in groups, which stays silent when called — the reason is recorded in Governance. In an organization without a subscription, the AI manager and the AI workers are paused, and the deadlines that run on their own stop. The details, and the way back, are in No subscription.

How it acts — and when it stops to show you the draft

This is the part that raises the most questions, so it goes without hedging.

Before any consequential send, the system holds the message and shows you the draft — always, and not only when you are suspicious. It applies to email, to a message it sends to another person (WhatsApp, a group, Teams, a reply to a lead), to a calendar invitation that includes someone from outside, to changing or cancelling an event that already has someone from outside — the calendar notifies them — and to what an integration does outside Orion (sending, publishing, commenting, spending credits, issuing); an appointment that is only yours holds nothing, and neither does searching or reading through an integration. You get a card that starts with Send confirmation — nothing has been sent yet, saying what the action is — email, message, new event, a change to an event that already exists (with a line saying who will be notified), an action in an integration — and showing recipient, subject and text as they would go out; cancelling an event that already exists comes on a card that starts with Action confirmation — nothing has been done yet, also with the line saying who will be notified. In a conversation in which Orion recently read outside content (an email that came in, a web page, a contact's conversation, a file, an AI worker's result), the same action card also comes before he approves a prospecting email, activates a campaign or enrolls contacts in it, books or cancels an appointment, cancels an event, sets up the clinic workbook, hands a task to an AI worker or messages a colleague — details in security and privacy. Answer yes (or send it) to send exactly that, or no (or cancel) to cancel — any other sentence, like an "ok", a "don't cancel yet" or a "don't send it now", decides nothing, and the card comes back asking for the exact answer. When the same request produces more than one draft, the last card lists them all, numbered: yes releases all the ones that went out together, no cancels them all (send the 2 and cancel the 2 too), and the verb with the number (send 1, cancel 2) decides only that one — each one keeps its number, and one already decided is never swapped for another; if the same number appears on two cards, Orion asks you to quote the card. In a reply that brings a card, only the card asks: a question from Orion that would come with it he brings back after the card is decided, if it still makes sense — the reply tells you there is one. In the dashboard chat the draft appears right there on the screen, in a box with Approve and Cancel, which decide only that send — with several, the box shows the whole batch, with the card's numbers, each with its own buttons —; a yes or no typed there decides what the box on your screen is showing; a send that a routine left waiting appears in a separate box, with only Cancel, and its yes is the one to its card on WhatsApp or Telegram. The box's Approve is already the final yes: the click makes the send right away, with exactly the draft that was saved, without Orion rewriting anything. The box shows the whole draft; when it is very long, the box shows the beginning and says how many characters it shows, and the send carries the full text. The answer is the code's line: the receipt, or the line saying it did not go out or could not be confirmed. If Orion had a question saved for after the card, it brings it up right after that line, if it still makes sense. For sends that have no receipt (a group message, for example), Orion says in one short sentence what happened. In the dashboard, without a subscription, the boxes of drafts that were already waiting stay in the window: Cancel works on all of them — on a routine's box too —, and Approve only on a send that has a receipt (an email, a message to a person, a Slack message, a calendar invite); the rest — a group message, a scheduled Slack message and the options of a new routine (Create, Replace, Keep both) — gets a 🔒.

Two things are what make that card worth something. The first: the card is written by the code, not by Orion — so what you read is what will go out, and not the description it made of what will go out. The second: your yes is tied to the content you read. Change a comma in the text, change the recipient, change the time, and it asks again. A yes does not work twice either, and a draft does not wait forever — after a few hours with no answer it expires, and then it is a matter of asking again.

In voice conversation the lock is the same: Orion reads the card aloud — the action, the recipient with the address, the subject and the text — and the send only goes out after your spoken yes; no cancels it. Links are not read aloud: the card tells you the message includes a link (and how many) and, if the text is too long for one reply, that it goes on beyond what was read — your yes sends the whole draft, exactly as it is. What you said goes through speech recognition, so listen to the address and the name before you answer.

There are two exceptions, and you had better know about them. The first: a routine you scheduled sends at its set time without asking again — the content was authorized when you created the routine. But if, as it runs, it reads outside content (an incoming email, a web page, a contact's conversation) and then is about to send something to another person or do something that reaches other people (approve a prospecting email, book an appointment, hand a task to an AI worker, message a colleague), that waits for your yes on a card like this one; what it sends only to you still goes out at its set time. If you ask for a routine in a conversation in which Orion has just read outside content (an incoming email, a web page, a contact's conversation, a file you sent, someone else's invitation in your calendar, a CRM record that came from outside), it first shows you the whole routine on a card and only creates it with your yes — a yes that counts only for that card; a routine with the same name as one you already have also comes on a card, which asks whether to replace the old one, keep both or discard the new one (a yes on its own does not create it); when that card cannot be shown to you, the routine only looks things up and prepares, and whatever it is about to send, or change in your calendar, waits for your yes — details in security and privacy. The second: an AI worker does not go through that card — what holds its work is the autonomy policy you defined, covered in the Part about the AI team.

Once the send goes out, you get a short receipt — ✔ Email sent to…, ✔ Event created: … — Sat, August 15, 2026. The receipt is written by the code too, and it only appears when the service that does the sending confirmed it worked. For a Slack message, the receipt carries the link to the message that went out, when Slack returns it — ✔ Slack message sent to … — https://…. On a Google Calendar or Outlook event, anyone listed as a guest without a valid email address is not added to the invitation, and the receipt says who was left out — ✔ Event created: … · not added as a guest (no valid email address): …. If the send you approved did not go out, in place of the receipt you get a line, also written by the code, that says so and gives the reason when it is known — ✖ I did not send the email to…: your Google account is not connected to Orion, or the connection has expired. Nothing was sent. When the service returns an error and there is no way to know whether the send went out, the line says exactly that — ⚠️ I couldn't confirm whether the email to… went out — and asks you to check before asking again, so nothing is sent twice. On WhatsApp and Telegram the receipt and that line arrive as a message; in the dashboard and the app they do not arrive as a separate message: they always open Orion's answer. The exception is a group message, which goes out with no receipt.

If Orion is interrupted in the middle of a request (from the panel, the app or by voice), you are never left without an answer. If the answer was already ready, it arrives as usual. If it had only done simple lookups (checking your calendar or the CRM, searching for an email, searching the web), it redoes the request on its own, once. Two lookups leave a trace and so are not redone: checking your new emails (the ones it listed now count as Skimmed on the Emails page) and, for customers in Brazil, looking up a court case (it counts toward the daily limit). Then it tells you it was interrupted and did not send or carry out anything, and you ask it again. If it had already started an action (a message sent, a task, a record), it does not repeat it: it tells you it was interrupted and asks you to check before asking again, so nothing is done twice. Some lookups get the same care as an action and bring that same notice — for example, opening a full email, reading an attachment, asking the company library, running a financial report or using an external tool from Integrations. The notice stays in the conversation, together with your request, so you can ask later whether it went through. If not even the new attempt works, it tells you it could not finish: when it knows nothing was changed, it says so and asks you to send it again; when it could not check whether any action was carried out, it says that — and that notice may not stay in the conversation, so check before repeating. On a voice call, it says the notice out loud.

A note about names

Two brands live side by side: Orion Workers is the AI manager and the name of the app; Y Managers is the work-management platform. You see both in the same place.

If you used the platform before, you used to look for "Y Intelligence" in the menu. That name no longer exists in the app menu — it still appears in legacy text from the CLEAR methodology and from the management FAQ on the website. Everything that was artificial intelligence is Orion today: the Orion entry in the sidebar and the Ask Orion chat, which follows you across every page of the dashboard.

Map of the screens

The sidebar has three groups: Orion; Y Managers, with the work sections right below it; and Settings, a page with Organization, Users, Teams, Grouping, Billing and My Profile. The bar stays collapsed to icons and opens when the pointer passes over it. In a phone browser it does not take up the screen: it opens from the ☰ button at the top left and closes when you tap outside it, on the ✕ or on a page.

At the top of it sit your organization's name and logo; at the bottom, the line Orion Workers · Powered by Y Managers and your avatar, which opens your account.

The sidebar

From top to bottom, in three groups:

Orion

your agent's hub. Detailed just below.

Y Managers

opens the team-management home — Waiting on you, the work sections as tiles and Settings, on one screen, the same Y Managers screen as in the app. At the top of it, an Orion card shows its status (WhatsApp connected, unread e-mails) and leads to the hub. In the browser, right below it, sits the How Y Managers works bar: a three-minute video on the method and the cycle — the deliverable, the deliverables plan, the work plan, the feedback cycles and the dashboard — that only opens when you click it (the arrow opens and closes it; on a phone it opens the upright video). It has no ✕ and does not go away: it is reference material, for whoever joins the team at any time. After the work tiles, also only in the browser, the Annual planning card leads to the annual planning page, open to the whole organization. On plans without the team panel, the entry shows a padlock and the screen explains why. Right below the entry, indented in the bar, sit the work sections:

Dashboard

the team's charts — hours and cost allocation per deliverable, progress, distribution by status. It is the overall view of the work.

Deliverables

the list of every deliverable, with title, recipient, status, progress, hours and planned end — plus cost, for those who can see money. Team is not a column: it is a filter at the top of the list. This is where deliverables are created and edited.

Team Plans

the teams' deliverables plans — create, sign, follow and close.

Work Plans

the individual plans, with participant, period, stage, signatures, feedback frequency and the state of the cycles.

Reports

the archive of the monthly reports on the team's work — generated automatically for organizations with a subscription and activity in the month, or on demand, also with a subscription, for any closed month — plus the maturity signals and the lessons archive. They contain per-person assessments.

Course

the study mode, with sections, lessons and per-person progress. It only appears if your organization has an active course.

Each work tile on the Y Managers home (and on the app screen) shows a number of the moment, counted on the same view as the page it opens: on Dashboard, how many deliverables due in the last 90 days were rescheduled (shown from 5 on); on Deliverables, the overdue ones and those due in 7 days, in your team; on Team Plans, until when the agreed plan in progress runs; on Work Plans, how many are in progress and being drafted (for managers) or the cycle of your plan; on Reports, the latest month ready; on Course, how much you have completed. With nothing to say, the tile shows only its description.

Settings

opens a page with what keeps the house in order — one row per page, each opening the page it always did (the addresses did not change). Until October 2026 each of them was a loose entry in the bar. Each role sees only its own:

Organization

your company's data — identity, address, contact, profile — and the wording of the assessment scale. Editing belongs to the Admin.

Users

the register of people. This is where an Admin brings someone new into the organization, by email.

Teams

the structure of teams and subteams, who is in each one and with which role.

Grouping

the strategic layer that groups deliverables into objectives, initiatives, key results or whatever your organization wants to call them.

Billing

the organization's plan, the seats and access to the billing portal.

My Profile

your data. Some fields appear locked with a padlock — those are the HR fields and, for anyone who is not an Admin, the org role and Active, covered in the chapter on roles and permissions. It also opens from your name, at the foot of the bar.

Below the destinations there are three shortcuts that are not work pages:

Manual

opens this documentation in a new tab, already at the chapter that answers the screen you are on and in the language the app is in. On screens that do not have a chapter of their own yet, it opens the index. That same link repeats, discreetly, next to the title on Deliverables, Team Plans, Work Plans, Reports, Users, Teams, Organization and My Profile.

Guided tour

runs the walkthrough of the screens again, as many times as you like — including after the "First steps" list has already disappeared.

Sign out

ends the session. It stays pinned at the end of the list, always visible, even when your role unlocks a lot of pages — the other two scroll along with the destinations.

At the foot of the bar sit the four language buttons — EN · PT · ES · FR. Switching there changes the app's language right away and is saved as your preference, holding for the next times you sign in, on any device. It also changes the language Orion speaks: reminders, digests and reports on WhatsApp start coming in that language. It is the same language the Language field shows on My Profile — changing it in one place changes it in the other.

Which screen you start on

When you create the organization you say what you came to solve first. Whoever came for the AI manager lands on the Orion hub; whoever came for deliverables and team management lands on the Y Managers home — unless the plan does not include the team panel: then the start screen is Orion. Nothing is hidden because of that choice — it only decides where you land when you open the app.

Who sees each page

Visibility is not just a menu detail: the server checks the same thing on every request, so hiding an item is not the only barrier.

One important rule that does not show up in the menu: cost and salary figures are stripped on the server for anyone who is neither an Admin nor a team manager. Assistants and members do not see those numbers even on the Dashboard — they never reach the browser.

The Orion hub

The Orion entry opens your agent's hub, split into four blocks: Channels, Identity, Core Tools and Danger zone. At the top sit your First steps list and, right below it, the Quick guide bar: a two-minute video that shows those same steps and only opens when you click it (the arrow opens and closes it; on a phone it opens the upright video). The ✕ hides the bar for that visit: it comes back on the next load, until you close it three times — from then on it does not appear again. For whoever sees the list (the Admin), it also goes away on its own once the three steps are done. The ✕ count lives in the browser you are using, so in another browser or on another device it starts over from zero. The same video is at orionworkers.com/tour/en, with no sign-in needed — it is the address Orion sends at the end of the setup.

Channels — five cards, with the real connection state

Each card shows the true state of the connection (Connected, Not connected, or Checking… while it loads — never an invented state).

WhatsApp

connect and manage Orion's WhatsApp number.

Telegram

connect Orion to Telegram.

Google

connect Calendar, Gmail, Drive and Contacts.

Microsoft 365

connect Outlook, calendar, Teams, OneDrive and the Office suite.

Emails

the address you forward your emails to, and what has arrived through it.

Identity — who it is and how it behaves

Boss

your details as boss — name, timezone, phone and e-mail. The phone and e-mail Orion recognizes you by only change here, while you are signed in: he does not change them in the conversation (see security and privacy). The phone is how Orion recognizes you when you write, so it takes care of the format for you: type it with the area code (for example, 416 555 0123). Without a + in front, the number is read in the country shown right below the box, under Number's country: the one you chose there, which stays saved even with no number saved; with no choice, the connected WhatsApp's country, while it is connected; without it, your organization's country (the «United States» written out only counts for the currency: older accounts got it for any country outside Brazil); without that, your device's — by its time zone or, without it, by its connection —, saved the first time you open the Orion dashboard, on the computer or in the app; last of all, Brazil. In an account that pays in dollars and whose organization has no country set, Brazil is left out: until that first time, no country is saved. To change it, choose another country there and save: the choice is kept, even with no number. If you remove the number, the default country comes back. If no country is saved yet, the box shows empty and asks you to choose — and, while it is empty, a number typed without the + is not saved: Orion asks for the country code in front. Orion saves the number in international format and reads it back the way it understood it: We'll write to you at +1 (416) 555-0123 · Canada. If the number doesn't add up, it is not saved: Orion says why and, when it can, shows the most likely reading for you to accept with one click; when the same digits are a valid number in two countries (some Canadian and US numbers are also valid Brazilian landlines), it asks which one is yours, even if you chose a country before, and shows both readings for you to pick with one click — typing the country code in front (+1 613 555 0142) always settles it. A landline is accepted, with a note that it was read as a landline. If your number was saved in the past without a country code, the page shows a yellow notice with the reading ready — Use +1 (416) 555-0123 · Canada — and one click fixes it. If the WhatsApp connected to Orion is your own number and you save a different one, the page warns that Orion will stop treating that WhatsApp as yours. On the shared official line (the Orion contact), the number doesn't change in this box: it shows the connected phone and the way to connect the new phone — and warns you if the messages Orion sends you are going to a different number (see security and privacy). Known limit: mobile numbers from Mexico and Argentina reach WhatsApp with one extra digit (the 1 after +52; the 9 after +54). In Argentina, save the number with that 9 (+54 9 11…); in Mexico, for now Orion may not recognize the boss by the phone. The timezone is only saved when it is a real timezone — any other text is refused instead of becoming the wrong clock. With no timezone saved, the first option in the list says the default in effect (America/New_York); once chosen, the timezone doesn't go back to blank — to change it, pick another. In the conversation you can name the place: "my time zone is Toronto" (or Brasília, Manaus, Lisbon, Madrid…); when it doesn't understand the place, it asks — it never picks a time zone on its own.

Personality

Orion's personality, tone and behavior, including what it must never do.

Public role

how it presents itself to others, when it serves people who are not you; it is also where the line of each connected service number — not your personal line, not a line with no number connected, and not Instagram — shows the 📋 Run a survey shortcut, which leads to the Run a survey block.

Core Tools — ten cards, plus Audio to Notes

AI Workers Team

autonomy policy and audit trail for your AI workers, and the escalation queue waiting on your decision.

Integrations

connect third-party tools with your own credentials.

Automations

scheduled or recurring tasks and messages.

List

your personal to-do list and pending items.

Audio to Notes

transcribes meeting audio into structured notes, written in the language spoken in the meeting, with the full conversation cleaned up (who said what, not summarized or censored) one click away, ready to copy, and dictations into your own words. The card always appears, in the panel and in the app. If your plan does not include transcription, it shows a lock 🔒 and tells you a higher plan unlocks it. Recordings made before stay there to read and delete: when there are any, the locked card takes you to the list. Deleting a recording also removes its audio, transcript and full text, even mid-processing, and does not depend on the plan.

Bookings

a calendar of appointments and bookings with clients.

Knowledge

documents and context Orion draws on before answering.

Orion's Notes

what it noted about you and about your work.

CRM

contacts, companies and sales pipeline.

Prospecting

find and reach new customers.

Relationships

your personal network and contact reminders.

Danger zone

A single card, Delete, which permanently erases the agent and its data. Exactly what is erased — and what your company keeps, when the organization has more than one person — is in the chapter on leaving and deleting data. Worth reading before you click.

"Ask Orion" — the chat on every page

A floating button on every page of the dashboard (or ⌘K / Ctrl+K) opens the chat. In a phone browser it is a circle with ✨, in the bottom right corner. It is the same brain as WhatsApp, in the same conversation: what you handled over there continues here.

What sets it apart is page context. The chat knows what you are looking at, so you can point instead of describe: open a deliverable and ask "why is this one late?"; open a work plan and say "summarize this for me". When you open the chat without typing anything, it offers a few ready-made questions for the screen you are on. For security, the chat only receives from the dashboard which screen is open — never the text of the address — and the deliverable, plan or team on screen only when it exists in your organization. A link with text in its address does not carry that text to Orion, nor show it as the screen's title.

Files and audio. The 📎 next to the text box attaches up to 5 files per message — PDF, Word (.docx), Excel (.xlsx), CSV, TXT and images (JPG, PNG, WebP) — and Orion reads them the way he reads the ones that arrive on WhatsApp. Each file shows as a tag above the box while it uploads; if it is a type he can't read, over the limit or blocked by the security check, the tag says so right away, and the ✕ removes it from the message. You can send just the file, with no text. With the box empty, the 🎙 in place of Send records a voice message, as on WhatsApp: the time runs on screen, 🗑 discards and ➤ sends; recording stops on its own at 5 minutes. The audio is transcribed and counts against your plan's transcription minutes, like a WhatsApp voice note; the bubble shows the audio, which you can play while the window is open, and what Orion understood. The first time, the browser asks for permission to use the microphone.

Dictating instead of typing. The 🎙 in Ask Orion sends what you said as a message. In the other boxes where you write to Orion it does the opposite: it writes in the field what you said, and what happens next is still up to the box's own button — Ask, Get feedback, Send answer, Save. That is how it works in the Knowledge library question, in a doubt about a court case (for clients in Brazil), in a lesson's self-check, in the year's planning interview, in Notes, in Personality, in the Public role boundaries, in an AI worker's persona and in the plan's long fields. The reason: in those boxes the text is kept as the words of whoever wrote them, and transcription sometimes gets a name or a number wrong — reading it before sending keeps the mistake from being recorded. In the two plan fields that already saved by themselves when you left the box — the review's message and a deliverable's description — dictation saves too, exactly as leaving the box would; correcting it afterwards saves again. Recording stops on its own at 5 minutes, 🗑 discards and ✓ writes in the field; the audio counts against your plan's transcription minutes and is not stored anywhere. The first time, the browser asks for permission to use the microphone; in a browser that doesn't record audio, the box says so instead of staying silent.

If your dashboard session has ended, or your access cannot be confirmed at that moment, the chat tells you the message did not reach Orion and nothing was done: sign in again (or try again in a moment) and send the message once more.

Without a subscription, the button stays there, with a 🔒 instead of the ✨ — in the phone's circle too. It opens the chat with the notice Ask Orion is locked, which states the reason and the way back, in place of the ready-made questions; the text box is turned off. If the subscription lapses with the chat open, the next message comes back with the same notice, and nothing is done. The boxes of drafts that were already waiting stay in the window (see How it acts). On a new account, the chat works from sign-up: the Y Managers free period starts there and counts as a subscription.

The "Waiting on you" bell

At the top of the sidebar, just below your organization's name and above the list of pages, there is a bell with a counter. It gathers, in one place, everything that is stalled waiting on a decision from you — a plan to sign, a cycle to assess, a report to submit, an AI worker escalation (only the ones you decide: as Admin, account owner or leader of the worker's team), unread notifications. Clicking an item takes you straight to the screen where the decision is made, and the list really does shrink as you resolve things. In a phone browser, the same bell sits at the top right of the screen, with the same counter. Without a subscription, what you can't do stays on the list, with a 🔒 and the reason. In an organization without a subscription — or with a cycle's deadline on hold —, the item's deadline shows as ⏸ deadline paused; the renewal of an AI worker's plan is the exception, because it is due when the plan ends.

"First steps"

A short activation list, present both on the Dashboard and in the Orion hub, collapsed by default into a single line with the progress ("x of y").

Two things are worth knowing: each item is marked done from the real state — the WhatsApp number really is connected, the plan really was signed — never because someone clicked through a tour. And the list is trimmed according to what you said you came to do, so whoever signed up only for the AI manager does not get deliverables steps. When everything is done, it disappears on its own.

On mobile

The Orion Workers app (App Store and Google Play — links to both stores are on the cards of the dashboard home screen, next to the tools) brings the same screens to your pocket, in four tabs — Home, Clients, Emails and Settings — plus an unlabeled microphone button in the center that opens the real-time voice conversation. Installation and voice mode are in the chapter on channels. At the end of the Home screen is the Danger zone, with Delete account. The app also creates an account for people who don't have one yet (see In the mobile app, in Getting into the platform). The bar at the top of the Home screen opens the written conversation with Orion — the same conversation as WhatsApp and the dashboard, behind the same gate as Ask Orion (with no subscription, the app says what to do). There, with the box empty, the 🎙 in place of Send records a voice message, as on WhatsApp: the time runs on screen, 🗑 discards and ➤ sends; it stops on its own at 5 minutes, the audio becomes text on the server and reaches Orion like a WhatsApp voice note, counting against your plan's transcription minutes. During a real-time voice conversation the box's 🎙 does not record — the microphone belongs to the call — and closing the conversation midway discards the recording.