Each person uses it in the chat they already have, and the assistant works in email, calendar, ERP and CRM with the company's procedures. The administrator decides which systems it reaches and what it does without asking; every other write to a system waits for a person's yes, and every action is recorded. Personal data and reserved words reach the model masked, from an EU server dedicated to the company, and the model can also run on your own servers.
30 minutes on the area you want to explore, with no commitment
Each person decides, for their own account.
The administrator decides, system by system, for every assistant in the company.
It follows the prompts each person writes on their own.
It follows the procedures the company distributes by role and the ones colleagues share after a security check.
Whatever the person pastes leaves, and the company does not know what.
Personal data and reserved words reach the model masked, from an EU server dedicated to the company, and the model can run on your own servers.
Nobody records who decided it.
A person confirms every write, or the administrator has authorised it for that system, and the record says who decided and when, as the AI Act requires.
It stays with the person who found it, and leaves with them.
It stays with the company, and passes from one person to their colleagues through shared documents, procedures and skills.
Deadlines slip and email piles up. The two usual answers do not solve it:
The quickest people use an AI assistant from their own accounts, and the company cannot see what goes through it:
A team AI subscription has to be opened and steered by each person, and it does not know the company's systems:
Everyone writes to it, voice notes included, in the chat they already use: Slack, Discord, Telegram, Google Chat or Microsoft Teams.
For each system you choose whether the assistant reads, drafts, asks for confirmation or acts on its own.
It answers from procedures, price lists and contracts, citing the document, and remembers each person's preferences.
The role's template sets tools, permissions, procedures and skills. A new hire's assistant is created from the template and is ready to work.
A person or the company loads them, and whoever shares them decides which colleagues read them. Every assistant answers from those documents and cites the one the answer comes from.
What one person teaches their assistant becomes a skill colleagues install from the console, after a security check. The assistants suggest the skills the company has verified.
When you ask, the assistant sends the meeting's recap and tasks to the participants, by email or in their chat.
The controls are set in the console and apply to every assistant.
The role is administrator, operator or auditor. Accounts are created by the administrator, who can require a second sign-in factor from everyone.
Every skill that is not Cerase's is analysed, and a risky one gets in only with the administrator's yes.
They stay in a separate service, every connector runs isolated, and a connector with risky code is rejected.
Names, tax codes, IBANs and the words the company marks as reserved are replaced before the text leaves the company's server, in the EU. The person sees what was masked and corrects it.
«I am sending the quote for project Orione to Mario Rossi (tax code RSSMRA80A01H501U, mario.rossi@acme.it) for IBAN IT60X0542811101000000123456 by Friday.»
«I am sending the quote for project [PROJECT 1] to [FIRST LAST 1] ([TAX CODE 1], [EMAIL 1]) for IBAN [IBAN 1] by Friday.»
The person approves from the link or by answering in the chat, and can correct the action before it goes.
It is an append-only log, exported as CSV or JSON from the console.
The administrator chooses which systems each assistant can reach.
A system not listed here is connected with a custom connector.
It writes to clients and suppliers from an address of its own, on your company's domain too, and receives the replies in its own inbox.
An email that has to come from you is left in your drafts, ready to review.
In the console you see every email it receives and sends.
Good morning,
your invoice 247 has been recorded and the due date set to 30 June. If the IBAN has changed since the last payment, could you confirm it?
--
Sofia · AI assistant of Luigi Bianchi, CEO @ Rossi S.p.A.
To speak directly with Luigi Bianchi: luigi.bianchi@rossispa.com
This message was written and sent by an AI assistant, powered by Cerase.ai
You create a new process by asking the assistant in chat, and the ones below are a few examples of thousands possible.
Every morning it proposes the replies, and sends nothing without your yes.
It drafts a reply to every request that comes in, from the helpdesk too, and sends it after your OK.
Every week it sends you the summary from analytics, advertising and CRM.
From the spreadsheet's prices it prepares the quote as a PDF, with exact sums.
From your voice note it updates contacts, deals and notes.
It records received invoices in the ERP, scanned ones included.
From a document or your notes it prepares the presentation as a PDF.
It fills in a PDF you received, adds your signature and shows it to you before sending it back or out for signature with Docusign; a qualified electronic signature you apply yourself.
It is natively integrated with Google Meet and Microsoft Teams, and reads the notes of the recorders you already use.
Every morning it offers to join the day's calls; you can also add it to the guests or paste the link in the chat, and it tells you if nobody lets it in.
The audio is stored in the EU, in storage dedicated to your company, and transcribed by a provider in its EU region.
In the chat you ask it for the summary, the recap to the participants or the CRM update, and weeks later it finds what was decided.
It updates CRM, ERP, documents and email with the permissions the company sets.
Examples of typical SME workflows.
You see pending approvals, activity and the credits spent.
An action is an operation on one of your systems: an email sent, a deal created, an invoice recorded.
| 14:32 | Carlo Rossi | Sofia · Pro | Email sent · ACME · invoice 247 | Done |
| 14:30 | Giulia Bianchi | Marco · Pro | Contract change · BiancoSrl | Awaiting OK |
| 14:25 | Carlo Rossi | Sofia · Pro | Payment schedule updated · 30/05 | Done |
Who has access to Cerase, in which group, with which assistants assigned. Add, suspend, change permissions.
| Name | Role | Groups | Assistants | Last access |
|---|---|---|---|---|
| Paolo Rossi | CEO | management | Cesare Pro | today 09:45 |
| Maria Conti | CFO | managementadmin | Anna Pro · Sofia Pro | today 14:02 |
| Carlo Rossi | Administration | admin | Sofia Pro | today 14:32 |
| Stefano De Luca | Admin operator | admin | Sofia Smart · Luca Smart | today 14:18 |
| Giulia Bianchi | Sales account | sales | Marco Pro · Lara Smart | today 13:58 |
| Roberto Greco | Sales operator | sales | Marco Smart | yesterday 17:32 |
| Elena Marin | Marketing | marketing | Lara Smart | today 10:08 |
| Anna Veneri | Customer service | cs | Luca Smart | today 11:20 |
Every assistant starts from a template and has its own memory and permissions.
| Instance | User | Specialisation | Connectors | Memories | Last used |
|---|---|---|---|---|---|
| Sofia Pro | Carlo Rossi | Administration | 6 active | 47 | today 14:32 |
| Sofia Smart | Stefano De Luca | Admin operator | 4 active | 12 | today 14:18 |
| Sofia Pro | Maria Conti · CFO | CFO/administration | 8 active | 38 | today 14:02 |
| Marco Pro | Giulia Bianchi | Sales · account | 5 active | 23 | today 13:58 |
| Marco Smart | Roberto Greco | Sales · operations | 4 active | 8 | yesterday 17:32 |
| Anna Pro | Maria Conti · CFO | Management reporting | 7 active | 19 | today 14:02 |
| Luca Smart | Stefano De Luca | Bank reconciliation | 3 active | 14 | today 14:18 |
| Cesare Pro | Paolo Rossi · CEO | Management / decisions | 8 active | 27 | today 09:45 |
| + 3 more instances (Marco · Lara · Luca) | |||||
The people who use the assistant create them, in chat or here: at a set time or when something happens in your systems. The admin sees them all and can pause them.
| Task | Assistant | Frequency | Next run | Status |
|---|---|---|---|---|
| Daily card payments | Sofia Stefano | Daily 18:00 | today 18:00 | Active |
| Morning management brief | Cesare Paolo · CEO | Daily 07:00 | tomorrow 07:00 | Active |
| Campaign performance report | Lara Elena | 1st of the month 09:00 | Sun 01/06 09:00 | Paused |
| Task | Assistant | Trigger | Status |
|---|---|---|---|
| Automatic supplier reply | Sofia Carlo | Certified email · new message received | Active |
| New lead brief | Marco Giulia | HubSpot · lead created | Active |
| Unpaid invoice alert | Anna Maria · CFO | Invoice · due +45 days | Active |
Connectors open access to your systems, skills say how to work. For each connector you choose the approval level.
| Skill | Template | Instances | Default behaviour |
|---|---|---|---|
| Answer from the knowledge base | All | 11 | Autonomous |
| Prepare a draft | Sofia · Marco · Anna · Lara | 8 | Draft, never sent directly |
| Update records with confirmation | Marco · Sofia | 5 | Awaits the user's OK |
| Triage and first reply | Sofia · Luca | 4 | Draft for admin, autonomous for cs |
| Attachment handling (audio · images · documents) | All | 11 | Autonomous |
| Set up an automation | Cesare · Anna · Lara | 4 | Awaits the admin's OK |
Every conversation and every action, with who and when. It exports for the accountant or the lawyer.
| Time | Staff member | Assistant | Action | Conversation | Status |
|---|---|---|---|---|---|
| 14:32 | Carlo Rossi | Sofia · Pro | Email sent · ACME · invoice 247 | Open thread | Done |
| 14:30 | Giulia Bianchi | Marco · Pro | Contract change · BiancoSrl | Open thread | Awaiting OK |
| 14:25 | Carlo Rossi | Sofia · Pro | Payment schedule updated · 30/05 | Open thread | Done |
| 14:18 | Stefano De Luca | Luca · Smart | Bank reconciliation · 47 lines | Open thread | Done |
| 14:02 | Maria Conti · CFO | Anna · Pro | Monthly payments report generated | Open thread | Done |
| 13:58 | Giulia Bianchi | Marco · Pro | Sales proposal · RossiSpa | Open thread | Draft |
| 10:08 | Elena Marin | Lara · Smart | New oil campaign report · Drive | Open thread | Done |
The company's documents and personal ones, and which assistants consult them. What sits on Drive or in the ERP the assistant reads where it is.
Which connectors you use, which assistants work most and at what hours. Filter by period, template, user and assistant.
Organisation configuration, security, audit, notifications. All from one place, without having to write to Cerase.
Sample screens of the admin console. Users, amounts and times are sample data, not a customer's.
Every assistant starts already configured for its role.
5-10 minutesEmail, drive, CRM, ERP, the company's documents and the team's chat.
a few hours spread over 1-2 weeksFor particular cases we work alongside you, and build custom connectors if needed.
assisted setupFour plans with every feature: only the credits included each month change. Flex includes none and uses packs.
Every feature, for occasional use: the assistant spends only the credits of the packs you buy.
Every feature, for people who use the assistant for part of the day.
Every feature, for people who work with the assistant all day.
Every feature, for people who hand the assistant a lot of work and do not want to count credits.
* Indicative figures, with one complex task in five. Each line on its own uses the whole monthly allowance.
For companies that already have an AI provider, negotiated rates, or requirements that keep the model and the tokens inside their own perimeter.
The assistants use your account's key with the provider, or a model on your infrastructure. Cerase runs the assistants, permissions, privacy filter, audit, connectors and dedicated EU server; the cost of the models goes through your contract.
Base catalogue of connectors and skills, dedicated EU server, full audit.
Encrypted daily copies in the EU, which the administrator restores from the console.
A task repeated on the same material uses fewer credits than the first time.
99.5% availability, response within 4 hours, continuous monitoring. Details
Thirty minutes in a demo is enough to find the right mode for your company.
See if it's right for youWhat the SLA guarantees
Guaranteed monthly, with maintenance in the evening or on holidays.
When the service stops or the assistants do not answer.
Daily backup and restore within one business day.
We tell you about incidents before they stop your work.
Support coverage on working days, Mon–Fri 9–18 CET, in every mode.
Pick the area that interests you most and we look at it together, with no commitment.
What partners, CFOs and advisers ask before signing.