It reads across, not within
An assistant bolted onto a CRM can only see the CRM. Ori reads the ticket, the invoice, the contract and the meeting together, which is the whole reason the modules share a database.
Ori reads across every module in Version X and acts on what it finds. It sees the support ticket, the overdue invoice and the missed meeting as facts about one customer, because they are records in one database. Included on every tier from Launch at €499 a month.
Availability · Every tier, from Launch
An assistant bolted onto a CRM can only see the CRM. Ori reads the ticket, the invoice, the contract and the meeting together, which is the whole reason the modules share a database.
Ori chases the overdue invoice, drafts the reply and flags the account. You get told what happened rather than being asked to do it.
Multi-step actions run through approval gates. This is the platform-wide rule, and it is what makes an AI that can act safe to give real permissions to.
Ori answers from the knowledge module, cites the document it answered from, and notices when what the process says and what the records show have drifted apart.
An AI chief of staff is a system that reads across a company’s whole operational record, rather than one function, and acts on what it finds. The difference from an assistant is scope: it sees support, finance, contracts and meetings as facts about the same customer.
Yes, within the permissions you give it, and multi-step actions run through approval gates rather than being written silently. That rule applies everywhere in the product, including during migration.
All of them. Ori and the core agent team are on every tier from Launch upward, with an included allowance of AI actions and a single metered rate beyond it that is the same on every tier.
No. Unlike Salesforce, where AI is an add-on from $550 per seat, Ori is included in the tier price. Usage above the included allowance is metered at one rate across all tiers, so moving up a tier is never the only way to get more headroom.