She talks
In chat, in voice and face to face, in one window. Every sentence names its source, and an answer without coverage in your knowledge never reaches the customer.
Ada works on your website from the first question to a booked slot, and then runs the demo herself. Every answer rests on your company's knowledge and cites its sources. Every change to your data is prepared for a human to approve.
Core infrastructure hosted in the EU · answers with source citations · no ad or analytics trackers
Ada is an AI assistant. You are talking to a system, not a person.
This works today, on your website and your content. Each item has its own page with a sample conversation and a clear split between what is ready and what is still being built.
In chat, in voice and face to face, in one window. Every sentence names its source, and an answer without coverage in your knowledge never reaches the customer.
A slot picked inside the chat window, a confirmation with a calendar file, reminders. She runs the demo herself, prepared on the visitor's own website.
She receives and replies in the same thread, from the same knowledge as on the website, and protects booked slots with reminders.
From a catalogue you define, at the moment it answers the question just asked. She never invents an address of her own.
Questions without coverage become a list of topics to write, and every turn leaves a trace in the audit log.
Where this behaviour comes from: the platform and Ada's working cycle.
No new windows and no new passwords. Ada comes to the tools your team already uses.
You add Ada to your Slack or Teams workspace like a new team member, point her at the knowledge groups she may access, and connect the tools you work with. No changes to your infrastructure.
You write to Ada in a channel, in a thread or in a direct message, the way you would write to a colleague. Once, or on a schedule: the same instruction can become a recurring task that comes back at a set time.
Ada does not send you off to read the documentation. She comes back with a finished answer or an artifact, and every change to your data waits for your click on a confirmation card.
Ada is not a chatbot for a single team. The same machinery, a knowledge base with citations, connectors and confirmation cards, serves support, finance, sales and engineering.
She pulled revenue from Stripe, checked the sales pipeline in Pipedrive, reviewed open issues in Linear and put it all together into one picture. In a single Slack message.
A new hire asks Ada in a direct message about benefits, leave and procedures. Ada answers from your company's curated knowledge base and points to the source every time. Questions with no coverage land in the knowledge gap register, so HR sees what is still missing. The result: a finished answer in the thread with a link to the source, instead of a pointer to the intranet.
Each month Ada pulls data from your payment and accounting tools through connectors, turns it into a summary and posts it to the finance channel as a recurring task. Sending an invoice or correcting a record always goes through a confirmation card. The result: a board-ready summary waiting in Slack on Monday morning.
After a sales call Ada prepares the opportunity update in your CRM and puts it up for one-click approval. The team asks her about pricing, terms and proposal wording, and she answers only from approved material, with citations. The result: a CRM that stays current without manual clicking, and customer answers consistent with your offer.
Ada collects overnight monitoring alerts and tracker issues, groups recurring problems and posts a morning summary to the team channel. Questions about on-call procedures and runbooks get an answer sourced from the knowledge base. The result: one triage thread instead of thirty notifications, every day at the same hour.
Ada connects to more than 1,600 tools through managed connectors. CRM, project management, finance, communication, analytics. If your team uses it, Ada can connect to it.
Most connectors take one click to authorise. You pick the tool, confirm access and you are done. You set the permission scope when you connect, and you can disconnect at any moment.
Some tools use API keys instead of OAuth. Either way Ada handles the authentication and starts working right away, and secrets stay on the platform side, never in the conversation.
No webhooks to configure and no Zapier zaps. Connectors are managed on our side, and every write action in your tools goes through a confirmation card.
Not every matter is settled in writing. Ada sends a link to a conversation room and speaks in the same voice she writes in.
From the chat you get a link to a room where Ada speaks and listens in the browser, with a live avatar. No installation, no new account and no new passwords. One click starts the call.
Voice is not a separate mode with looser rules. The same knowledge sources, the same limits and the same permissions of the person asking apply exactly as they do in writing.
An AI employee gets exactly the same boundaries as a human one. These are not settings you can overlook, they are the way the platform works.
Every request passes availability, mode, limit and knowledge corpus checks in turn before it reaches the language model at all. When any gate blocks, the model provider is never called.
The answer is buffered in full and checked for coverage in the sources before anyone sees the first character. Missing citations mean the whole answer is rejected, and the question goes to the knowledge gap register.
Data changes never leave the model's turn. Ada prepares a confirmation card, a human approves it with a separate click, and the safety checks run again at the moment of approval.
Ada answers only from content the person asking is allowed to see. This is not a filter applied to the result, it is a condition of the query itself. Separation between companies is required on every database query and covered by isolation tests.
Budgets and limits are fail-closed: when something breaks, the feature shuts down rather than running unchecked. On top of that, rate limits for voice conversations and SSRF protection when importing content from URLs.
Core infrastructure runs on servers in Warsaw, and on the Enterprise plan we sign a data processing agreement (DPA). Models run through the commercial APIs of the providers listed in our subprocessor register, under no-training terms; some of that processing may take place outside the EEA under appropriate safeguards. The site and the widget use no cookies, no ad or analytics trackers and no external CDN for our code.
You do not have to take our word for it. The platform
publishes a capability matrix at /capabilities, where you can
check for yourself what is enabled on your instance.
/capabilities. It is a technical inventory of your
instance's features that you can verify yourself, without taking our
word for it.Tell us what tools your team uses and what it works on day to day, and we will show Ada in action on your own scenarios. No pressure and no commitment.