- Gmail
- Outlook
- Microsoft 365
- IMAP inbox
Gmail is implemented today: the AI sorts incoming emails, recognises the request and prepares a draft reply. Outlook, Microsoft 365 and IMAP are assessed as projects.
Your software stays. We connect what you already use: DATEV, beA, practice software, calendar, inbox. Today the routinefrei customer workspace connects Gmail and Google Calendar: sorting enquiries, preparing draft replies, coordinating appointments and documenting important actions. We only connect other providers after a technical, functional and economic review, never on spec: Microsoft 365, telephony, accounting, CRM, shop and messaging are possible pilot integrations, not standard modules that can be activated today.
Three steps, always the same.
The AI reads a request in the connected inbox and recognises what it is about: appointment, general enquiry, invoice, complaint or a sensitive special case.
In the core product it uses Gmail and Google Calendar. For shop, accounting, CRM or telephony, we first check whether a reliable interface and a sensible data flow exist.
It carries out the action or prepares it for approval, documents the result and reports back clearly on what happened. Anything sensitive always goes to a person.
The diagram shows the possible target architecture. Today, email and calendar are implemented; all other nodes stand for integration projects that are assessed individually.
The green cards belong to the existing core product. All areas marked orange are possible pilot integrations and are only offered after a technical check.
Gmail is implemented today: the AI sorts incoming emails, recognises the request and prepares a draft reply. Outlook, Microsoft 365 and IMAP are assessed as projects.
Google Calendar and your own booking page are implemented today. Microsoft 365, Cal.com and Calendly are only assessed if needed.
A phone pilot deliberately starts with answering, a structured summary and handover. Appointment actions only follow once the pilot works reliably.
We check the API, permissions and data quality. Only then can a pilot read order status or hand special cases over to your team.
Lexware Office, sevDesk or DATEV are only connected as a limited pilot after a review of the provider, permissions and process.
We check the data model and duplicate rules before new contacts or cases are created in a CRM.
Messaging needs a concept for channels, consent and handover. Only then is a clearly limited pilot set up.
Do you use industry software that isn't listed here? In the initial consultation we check the interface, permissions, costs and benefits, and only then do you get a quote.
This is what it feels like when the AI talks to your apps. This demo runs on sample data from a fictional business. Ask a question or choose an example, and see how the AI picks the right app and answers.
Ask a question below or choose an example. The demo works exclusively with fictional data.
Please do not enter real names, contact details or confidential content. Privacy
In a free initial consultation, let's look at which of your apps can sensibly be connected and where the AI takes the most work off your hands. Without obligation or pressure.
Request a free initial consultation