Plans, leaving, and glossary

21. Plans and limits

Two billing lines, not one

The platform has two halves, and they are billed separately. Seeing that from the start avoids the most common surprise on the first invoice.

Y Managers (the team dashboard)

billed per active human member of the organization, per month. It is its own line on the invoice — it does not come bundled into Orion's channel plans. The first members of every organization are never billed (the floor is subtractive: it comes off the count, not off the price), and non-profits and government bodies get a larger floor. How many members are free today is on the Pricing page.

Orion (the AI manager)

billed per person seat. There are four plans — Telegram, WhatsApp, WhatsApp Voice and WhatsApp Voice Max — and each person in the organization can have one seat or none.

Beyond those, two items take up the same kind of seat and the same price as the WhatsApp plan, in your organization's currency: each active, billable AI worker, and each extra dedicated WhatsApp number. On the Billing page they appear added to the people, not hidden in another account — the total you read there is the total the card sees.

What changes from one plan to the next

Every plan with an agent includes the same set of capabilities: calendar, email and documents from Google and Microsoft 365, reading of forwarded emails, CRM and relationship radar, automatic routines, management of the team's deliverables, memory and precedents, internet search, and the mobile app. What changes between the plans is the channel and the size of the caps — Telegram has the smallest, Voice Max has the largest. The exact numbers are on the Pricing page.

There is also a Custom plan, negotiated case by case, for anyone bringing a group of users on at once: more integrations, the option to bring your own AI key (BYOK), and the choice of which features and limits are included. It does not automatically inherit the caps of the plan above it — each item is agreed on its own.

The 14-day trial

The trial is free for 14 days and does not ask for a credit card. It runs at the WhatsApp Voice level, with caps of its own.

The clock starts on the first channel you connect — WhatsApp authorized, Telegram linked, or your first voice session in the app. It does not have to be WhatsApp: if you start with Telegram or with voice, your trial is already running.

Two honest quirks of the trial period:

The trial's transcription budget covers the 14 days as a whole, not the calendar month. If you start on the 28th, you do not get one budget in August and another in September.

If you subscribe in the middle of the trial, the rules of the plan you bought apply immediately — not the trial's. That cuts both ways, on purpose: the plan is the one you chose, even on the days when the trial would have given you more.

The four free months of Y Managers

Independently of the Orion trial, every organization gets a four-month free period on Y Managers, for the whole organization.

That clock starts on the day the organization's first signed deliverables plan goes In progress, or 30 days after the organization is created — whichever happens first. A plan with a backdated date does not consume the period ahead of time.

The period includes up to two free AI workers and a text WhatsApp channel for the manager. That channel is unlocked when the organization shows it is actually using the method: at least one deliverables plan in progress and two work plans in progress.

When the four months end, the outcome depends on whether the organization has an active subscription:

With a subscription

the workers that were free become billable, and the Y Managers seats above the floor go onto the invoice.

Without a subscription

nothing locks up. The dashboard stays usable, the free-period workers are deactivated (and come back when you subscribe), the courtesy channel is revoked, and you are told. It is a soft ending, not a block.

Seats: who gets billed

On the Billing page, every member of the organization appears with a plan selector. Assigning a paid plan creates a billed seat; choosing Remove seat leaves the person without Orion and with Y Managers.

Seats granted by the platform (courtesy, or grants from the platform owner) appear marked as granted: they are not billed and cannot be edited there.

One rule that tends to go unnoticed: the dashboard's "Ask Orion" chat is open to anyone whose organization has an active subscription — even if that person's seat is free. "Free seat" does not mean "no chat"; it means "no channel of your own".

Monthly or yearly, and in which currency

The yearly plan costs ten times the monthly — two months free. You choose the billing interval on the Billing page itself, before going to checkout.

The currency comes from the country the company bills from: Brazil is billed in Reais, all other countries are billed in US Dollars. These are two distinct billing accounts, and an organization does not move from one to the other after the first charge. So, while the country is not set, the Billing page shows no price at all — it asks first. That is one more question in your way, and it is deliberate: showing a price in the wrong currency is getting the customer's money wrong before you have even charged it.

The Billing page

Any Admin of the organization can see the page. Only a billing manager changes the plan, seats, payment method or cancellation. The first manager is the organization's contact, set automatically; the page recommends designating more than one, and it is worth following that advice — with a single manager, that person leaving locks billing for the entire organization.

You can also ask Orion directly: "what are the plans?".

In some organizations, subscribing from the screen itself is not enabled. When that is the case, the page says so instead of letting you try.

The three meters — and what happens when you hit one

The three are independent. Spending your spoken conversation does not consume your transcription budget, and vice versa — they are separate meters on purpose, because they cost different things.

When you hit the daily capacity cap, Orion says in the conversation that it is going to take a break and will be back the next day. When you hit the monthly one, it stops until the month turns over or until you change plans. In both cases it says that it stopped — it does not go silent without explanation.

On voice, each call reserves five minutes up front and settles the account when it ends. If the session is abandoned without being closed, it is closed automatically a little later and whatever was not used goes back to your balance (a one-minute minimum stays charged).

An honest note about the caps: they exist to stop abuse, not to meter your usage. The heaviest profile measured across our own fleet sits below the monthly cap of the WhatsApp plans — it gets close to it, but does not cross it. If your usage runs far above that, the path is a bigger plan or a custom plan, and it is better to know that up front.

When the trial ends, or you cancel

Orion warns you before the trial ends.

Without subscribing, the account lands in the No subscription state. The team dashboard keeps working; the agent stops. (There is no longer a "free plan" at this point: someone who did not subscribe is not on a plan, they have no subscription — and the screen says exactly that.)

The channels do not drop at the same instant. The WhatsApp connection is undone after a two-day grace period, and the same grace period applies when a paid subscription is canceled.

Nothing is lost in this process. Your data, your history, your automations and your number stay where they were. When you resubscribe, you reconnect the channel and pick up where you left off.

22. Leaving and deleting data

Three different actions — do not confuse them

Cancel the subscription

stops the billing. Your organization, your data and your history remain.

Remove a person

takes away their access. Their work history stays with the organization.

Delete the agent and the data

erases. It is irreversible, and there is no undo button.

One practical consequence of this: deleting your data does not cancel the organization's subscription. If you are leaving for good, cancel in Billing first, then delete.

Canceling the subscription

In Billing → Manage subscription, you go to the payment provider's secure portal, where you update the card, change plans or cancel. Only a billing manager has that button.

After cancellation, the same two-day grace period described in chapter 21 applies: the channel is only undone after it, and the data stays.

Removing a person from the organization

In Users (visible to Admin and HR; the action belongs to Admin), the remove button performs a reversible removal. The person loses access, leaves the teams and disappears from the people screens — but their work plans, cycles and assessments stay standing, because they are records of the organization, not of the person. Restoring the person automatically reconnects all of that history, since their identity is the same.

Two protections you will run into: you cannot remove yourself, and you cannot remove the last Admin — promote someone else to Admin first.

Permanent deletion of a person is only offered after you remove them, and only when they have no work-plan history. If they do, the platform refuses and explains why: erasing the person would leave the organization's records orphaned. In that case, the right thing is to keep them as removed.

A user that represents an AI worker does not leave through here. To shut it down, use Orion → AI Team Governance and dismiss the worker: the identity goes with it and the billing stops immediately. Removing the synthetic user from the people screen would leave the worker orphaned — billed, with a plan, and invisible — and that is why the platform blocks that path.

Deleting your agent and your data

The path is Orion → Delete. Confirmation is by typing: you write `DELETE` to unlock the button.

Before you confirm, the screen shows a preview: approximately how many records, across how many tables, will be deleted — and a block called What will NOT be deleted. You read that before deciding, not after.

What goes:

• the agent and its configuration (personality, public role, settings);
• the WhatsApp and Telegram connections (the number is released);
• the forwarded emails, the memory pages and the knowledge docs;
• your CRM — contacts, companies and activity history;
• the scheduled routines and everything else tied to the agent;
• the conversation state, the stored files, attachments and recordings, and the memory indexes.

The list of what is deleted is not written by hand: it is derived from the live structure of the database on every run. A table created next month falls into scope by construction, and not because someone remembered to update a list. The sweep of the memory indexes is declared as best-effort in the report — when they cannot be walked, the report says exactly that, instead of counting it as zero.

What is not deleted — and why

Here the deletion splits into two paths, and what decides is whether there is an employer on the other side.

Organization with more than one person. We erase the Orion side. The work records in Y Managers — plans, deliverables, cycles, assessments and the audit trail — belong to the company, which is the controller of that data, and the law often requires it to keep them. They remain, and the deletion report explicitly says what was retained. To request the deletion of those records, the request goes to the company, not to us.

Organization of one person only. You are the company. There is no third party to protect, and refusing to erase someone's own records because "the company owns them" would be indefensible. Both sides are erased.

The head count is done at the moment of the request, never stored — organizations gain and lose people. AI workers and system users do not count as people: without that, a one-person organization with two workers would look like three and would take the wrong path.

And when the count is ambiguous or fails, the deletion deliberately takes the narrow path (Orion only) and reports the uncertainty. The two directions of error are not symmetric: erasing an employer's records is irreversible and hits people who asked for nothing; failing to erase is a problem you can fix the next day.

The honesty rule

If any part of the deletion fails, the platform does not say it deleted. It says the deletion did not complete, states that nothing is being claimed as erased, and passes the detail to the team to finish.

This is a design decision, not a detail: a false confirmation is worse than an incomplete deletion, because it takes away any chance you had of finding out.

Once the deletion is complete, the screen tells you that you can sign out. To use Orion again, it would be the setup of a fresh agent, from scratch.

23. Glossary

The work

Deliverable

the tangible, measurable result of the work — "Monthly report published", "Launch campaign live". It belongs to a team, which answers for it. It is the "what".

Recurring deliverable

a deliverable with Recurring status — a continuing goal, with no final deadline (monthly sales, NPS, uptime). You record the result of each period and it never "finishes" at 100%.

Task

the "how". It belongs to a deliverable, and it is task progress that computes the deliverable's progress. Different from your personal to-do list, which belongs to no deliverable.

Target and target type

the amount to be produced and the unit it is measured in — percentage, unit or money value (plus any types your organization already uses). There is no "yes/no" target type.

Recipient

who benefits from the deliverable — internal, clients/users, beneficiaries, community, suppliers, government, partners, investors.

Requester

the team that formally asked for the deliverable.

Grouping

the tree of groups the organization uses to classify its deliverables (by area, by business line, by whatever makes sense). It has its own page in the sidebar.

Planned baseline

the planned dates, the target type and the deliverable's target. Editable until the planned start date arrives; from then on they are locked, and changes move into the "Updated" fields.

The plans

Team deliverables plan

the deliverables a team will work on during a period. It is signed by the manager, and the signature is the moment the scope gets reviewed.

Planned

a deliverables plan already signed whose period has not started yet. Not to be confused with Draft — a draft has not been reviewed by anyone.

Source plan

the signed deliverables plan (and In progress or Planned) a deliverable has to come from in order to enter a work plan. For an AI worker this rule blocks; for a person, it only records a warning.

Work plan

a worker's individual commitment — which deliverables they work on and how their time is split across them, as a percentage of effort.

Participant and supervisor

the two signature lines of a work plan. Both signatures advance the plan and automatically create the assessment cycles.

Agreed

the work-plan stage after both signatures, before the period starts.

Adjustment requested

a stage of its own, created when someone asks for an adjustment to a plan that is not yet agreed. Both signatures are cleared and both parties sign again. Not the same as going back to Draft.

Combinado

the working agreement in the form of a structured questionnaire, which comes down from the organization to the team and from the team to the person. When a work plan is signed, the Combinado in effect is frozen inside the plan — what counts is the version from the day of the signature.

Cycles and assessment

Cycle

the assessment window created by the signing of the work plan. Its duration comes from the feedback frequency chosen in the plan.

Cycle report

what the participant writes about what was done, deliverable by deliverable. It can be submitted from the last day of the cycle onward, and even after the deadline, as long as the manager has not assessed it.

Feedback given

the state of the cycle after the supervisor has assessed it. It is still mutable: the window is running to request a review or for the manager to adjust.

Review requested

the participant's request to reassess a low feedback, within the window.

Consolidated

the final, immutable state of the cycle. After that the rating no longer changes, and a work plan is only finalized when all of its cycles are consolidated.

Assessment frequency

how often a participant's work is assessed. It is what determines the length of the cycles.

Precedent

the recorded "why" of a decision — the reason, the lesson, the risk taken. It is kept and reused later, both by you and by Orion. It is what makes the system decide more and more the way your house decides.

People, roles and AI

Org role

Admin, HR, Audit or User. It applies to the whole organization and is checked on every request.

Team role

manager, assistant, member or observer. It applies to one team at a time, and a person has a single role per team.

Observer

a read-only team role, meant for a mentor or an outside consultant. Sees the team's work plans, never leads, does not see cost, and has no write button at all.

Home team

a person's main team, recorded on their profile.

Worker

the unit that carries a work plan. It can be a person or an AI worker — the work plan is the same object in both cases.

AI worker

an AI-powered worker hired by the organization. It takes a seat, has a work plan, submits its own cycle report, and is governed by an autonomy matrix.

Escalation

an action the AI worker prepared but cannot run on its own under the organization's autonomy policy. It waits for your decision, which you give in the conversation ("approve 1") or on the Orion → AI Team Governance page.

Billing

Seat

Orion's billing unit. Each person on a paid plan takes one; each billable AI worker and each extra WhatsApp number takes one too, at the WhatsApp plan price.

Free-seat floor

the number of human members your organization has for free on Y Managers. It is subtractive — it comes out of the count before the calculation — and it is larger for non-profits and government bodies.

Billing manager

who can change the plan, seats, payment method and cancellation. Every Admin sees the Billing page; only the billing manager changes it.

No subscription

the terminal state of an account that never subscribed (or canceled). The team dashboard continues; the agent stops.