Skip to content
evolus

How it works

Simple to use. Solid inside.

Six products, one platform. Here you see how Evolus works behind the scenes: how the pieces hand work to each other, what they remember, which models they think with, where your data lives and how you decide what they can do.

Ask Evo how it worksSee the plans

One platform

Evolus is not a chatbot with six different names. It is one platform, where every piece does its own job and knows who to hand it to.

One portal, the same credits, the same people with their permissions. Below you find how it works, chapter by chapter, and the documents that put it in writing.

Six ways of working

One portal, six ways of working.

Each product does one thing and does it well. Together they hand work to each other: a phone call becomes a task, an incoming invoice becomes an entry in your management system.

Two examples of work moving from one product to another. From the phone to the desk: at 7:42 pm the AI receptionist answers a customer asking for a quote; when the call ends the transcript and summary are ready; the call becomes a task for the digital employee, who notes the customer, prepares the quote and records the site visit the technician has to schedule. From the inbox to the management system: an invoice arrives, the invoice agent extracts its data, the automation records it in the management system and, if the total does not match the order, hands the check to the digital employee.

We switch on the link between the AI receptionist and the digital employee for you, on request.

Memory

Three memories, each for its own job.

An agent has to find the right answer in a hundred-page manual. A digital employee has to remember who Laura is and how far along her building site is. That is why Evolus does not have just one memory.

The three memories in an example. The document library: asked how long the spare parts warranty lasts, the agent finds the section «Original spare parts» in the Warranty and returns document, which says 24 months from delivery. Simple memory: the Returns policy file, at version 4, which the agent reads in full. A digital employee's memory map: Laura Bianchi, owner of Bianchi Heating, linked to the Via Roma site and to the replacement quotes procedure, with the new fact that delivery has moved to the 14th.

Agents

The document library

You upload manuals, price lists and policies, scanned ones too, or point to a web page. Evolus splits them into sections. When a question comes in, the agent looks for the sections about that topic, even if they use different words, and answers with those.

  • You can see the sections, correct them and write new ones by hand.
  • A library can belong to one agent or be shared by several.
  • Search indexes live in the platform database, in the European Union.

Document libraries from the Starter plan. From Business also the advanced ones: an automation creates well-reasoned sections and prepares the questions to find them by.

Agents

Simple memory

For the rules and procedures the agent must always keep in mind: short text files it reads in full, every time, with no need to search.

  • If you allow it, it updates them on its own when it learns something.
  • Every version stays in the history and can be restored.

Digital employees

The memory map

People, companies, projects and procedures become nodes linked to each other. Every email, call or meeting adds a fact or a link.

  • It gives each piece of information a weight and lets what is no longer valid expire.
  • In the portal you see the map, correct a fact or add what it needs to know.
  • It lives on the digital employee's server, in Germany, with encrypted backups.

And in Evo Assistant, memories and rules stay on your phone.

Models

The right model for each job.

Evolus does not depend on a single artificial intelligence provider. It works with models from Anthropic, OpenAI and Google and with open models, and each job uses the one that suits it best.

  • Let Evolus handle it

    A new agent starts on the model Evolus proposes as the default: you need to know nothing about models to get going.

  • Or choose yourself

    Among the models in your plan: basic from Starter, advanced from Growth, top-tier from Business. You change it from the portal whenever you like: instructions, documents and tools stay.

  • Fallback models

    You name one or more models to try, in order, if the main one does not answer. That way a provider having trouble does not stop the work.

  • Specialists where they matter

    To read scans and photos, speak on the phone and transcribe audio we use services built for the job, not just any model.

  • Your data does not train models

    The data processing agreement says so, in article 7.1: we do not use customer data to train, fine-tune or evaluate artificial intelligence models.

    Data processing agreement
The model settings of a customer support agent: «Let Evolus handle it» is selected, as an alternative to «Choose yourself». Basic models come with the Starter plan, advanced ones from Growth, top-tier ones from Business. Two fallback models, in order: in a request this morning the main model did not answer and the reply came from the first fallback model.

Security

Where your data lives. And who processes it.

We do not just say it on this page: we put it in writing in three public, versioned documents that are part of the contract.

Where the data lives. Portal, documents, attachments and search indexes: European Union, on Microsoft Azure in the Netherlands. Digital employees, with memory, conversations and transcripts: Germany, on a dedicated server in Nuremberg. Digital employee backups: Finland, encrypted before they leave the server. Requests to artificial intelligence models: United States, with European routing for the Enterprise plan. AI receptionist voice and audio transcription: United States, with a European voice region for the Enterprise plan.

  • Every customer in its place

    Every request is checked against your workspace, with automated tests on every code change. Every digital employee works in an environment of its own.

  • Encryption

    Everything travels encrypted. Passwords, keys and access to your software are encrypted when stored too, and they can no longer be read back from the portal.

  • Protected access

    Sign-in goes through a separate identity system, and you can turn on a second factor with a code by email. API keys are shown only once and can be limited to specific digital employees.

  • Tested backups

    Digital employee backups run every hour. Every 6 hours a real restore checks one of them, in rotation.

  • Declared suppliers

    The subprocessor list says who processes the data, for what and where. Every change reaches you by email at least 30 days in advance, and you can object.

  • If something goes wrong

    A written procedure for data breaches, and notice to the customer within 48 hours of our becoming aware of one.

We have started the ISO/IEC 27001 certification process. We have not obtained it yet, and we will not claim it until we do.

Read the documents

Security measuresSubprocessorsData processing agreement

Control

You decide what it can do. Everything stays on record.

Artificial intelligence works with your trust, not in place of your judgement. Every person has their own permissions, every agent and digital employee does only what you allow, and every action leaves a trace.

  • Roles and groups

    Owner, administrators, people who build, people who use, people who only look, people who handle billing. A group, such as «Sales», gives all its members the same roles. And for each agent you choose who can use it.

  • Capabilities one by one

    For agents and digital employees you switch on only what is needed: email, calendar, phone calls, connectors, web search.

  • It checks before speaking for you

    The digital employee shows you the email, phone call or WhatsApp message you asked for and waits for your yes. This safeguard cannot be switched off.

  • It says it is an AI

    The AI receptionist introduces itself as artificial intelligence, emails carry the notice, and in meetings the digital employee writes it in the chat. The AI Act requires it, in article 50, and it cannot be turned off.

  • Everything tracked

    Every automation run, step by step, the digital employees' tasks, the AI receptionist's calls. And a log of who changed roles, members, groups and domains.

  • Spending under control

    See who spent the credits and on what, group by group, and give each group a monthly budget as a reference.

How we use artificial intelligence
On Teams you ask the digital employee to tell the supplier that Friday is fine. It prepares the email for Ferri Supplies, shows it to you and asks whether to send it, with Send and Edit buttons. After your yes the email is sent and stays in the task history. Below, the activity log: Marta added Luca to the Sales group, gave him the Operator role, and the domain bianchi.it was verified.

Connections

It connects to what you already use.

No migrations: Evolus works on top of the email, software and channels you have, and lets your own software use it.

Evolus at the centre, connected to Microsoft 365, Google Workspace, IMAP email, Teams, WhatsApp, Notion, GitHub, your management system, your AI assistant and your website.

  • Email and calendar

    Microsoft 365, Google Workspace or any IMAP mailbox.

  • Teams and WhatsApp

    Digital employees work in Teams. Agents, automations and digital employees answer on a WhatsApp number of yours.

  • Catalogue connectors

    Notion, Jira and Confluence, GitHub, Linear, Airtable, Stripe and more, through the MCP protocol. From the Business plan also connectors of your own.

  • Any software with an API

    An automation reads from and writes to your management system or CRM, and your software starts it with an API key. Full API access comes with the Scale plan.

  • The Evolus MCP server

    Connect your AI assistant, if it supports MCP: you create, configure and check your automations by chatting.

  • One line on your website

    The widget works on any website where you can add one line of HTML.

How automations connect

Frequently asked questions

What people ask us about the platform.

Does Evolus use a single artificial intelligence model?

No. Evolus works with models from Anthropic, OpenAI and Google and with open models. Each agent starts on the model Evolus proposes as the default, or uses the one you choose among the models included in your plan: higher plans add the advanced and top-tier models. You can also name fallback models, which step in if the main one does not answer.

How do agents know my company's documents?

You upload documents to a library, scanned ones too, or point to a web page. Evolus reads them and splits them into sections; when a question comes in, the agent looks for the sections about that topic, even if they use different words, and answers with those. You can see and correct the sections from the portal. For rules and procedures there is also simple memory: text files the agent reads in full every time.

Do I need a technician to use Evolus?

No. Agents, automations, the AI receptionist and the widget are set up from the portal, explaining in your own words what they should do; if you describe your business to Evo, it prepares an agent for you to start from. You only need a technician if you want to connect your software through the API.

Where does Evolus work?

In the portal chat, on your website with the widget, on WhatsApp, on the phone with the AI receptionist, by email with automations and digital employees, and in Teams with digital employees, who also join Teams and Google Meet meetings. Evo Assistant, available on iPhone and Android, puts an assistant on your phone as well.

Is my company's data safe?

The portal, documents and search indexes are in the European Union; digital employees work on a server in Germany, each in a separate environment, with encrypted backups. Passwords and access to your software are encrypted. Requests to artificial intelligence models and voice go through providers in the United States, except for the European routing included in the Enterprise plan. We do not use your data to train models. It is all written down in the security measures, the subprocessor list and the data processing agreement.

Does Evolus connect to the software I already use?

Yes. It works with Microsoft 365, Google Workspace and any IMAP mailbox, with Teams and WhatsApp, with catalogue connectors such as Notion, Jira, GitHub and Stripe, and with any software that has an API. Your software can start automations with an API key, and with the Evolus MCP server you connect your AI assistant. No migrations needed: Evolus works on top of what you have.

Do you use my data to train artificial intelligence?

No. The data processing agreement provides for it, in article 7.1: we do not use customer data to train, fine-tune or evaluate artificial intelligence models. And we commit to choosing model providers whose contracts exclude training on the content we send: the status, provider by provider, is on the subprocessors page.

What if the artificial intelligence makes a mistake?

It can happen, as it can to anyone. That is why actions in your name ask for confirmation, digital employees ask when they are not sure, new automations start paused until you test them, and every run leaves a trace you can check.

Still have a question about how it works?

Ask Evo: it answers by voice or in writing, and tells you which plan to start from.

Talk to EvoWrite to Evo
Would you rather talk to a person? Book a demo