Choose which cookies you accept. You can change this at any time from “Cookie settings” in the footer of every page. Cookie policy
They make the website work, remember this choice, keep your conversation with the assistant if you use it, and protect the forms from bots. They cannot be turned off.
During your visit we remember the campaign source you arrived with and the page you landed on, so we know which campaigns and pages bring us requests. Cloudflare Web Analytics counts visits without cookies and does not depend on this option.
Used to measure our campaigns on Google Ads, LinkedIn and Meta. None is active on the website today.
Channels
Asynchronous: email with Microsoft 365 or Google Workspace, portal and forms. Real-time: WhatsApp, Teams, Slack, Meet, web chat and phone. Each channel, with what it does and what it needs.
One single record
WhatsApp “What time are you coming?”Teams Message from the supervisorCall Transcribed and summarizedCommunication and customers
Personal, shared and delegated mailboxes: support@ replies as support@. You know whether each email was delivered or bounced, and you sign in with your company account. It is enabled with your organization’s permissions.
With Meta’s official API and your account: several numbers, each with its own team, and approved templates. Whoever accepts a conversation owns it, and the customer gets the signed service report on their phone. WhatsApp voice calls are available too.
What people write to the attendo bot in Microsoft Teams, or in the Slack channels where it is present, lands in the unified inbox. It is linked to the document’s record and you reply from attendo. Text only.
Microsoft Teams and Google Meet meetings are linked to the document and the customer, with their recording and transcript. And the appointments you propose are created in Outlook or Google Calendar, with their meeting.
One per brand, on your website or your portal, with a code snippet or the WordPress plugin. It answers from your documentation, collects the visitor’s details and hands off to a person when needed.
Call from the record and each call becomes an entry on the document. Calls are recorded with a legal notice and logged consent, with a transcript and summary. Extensions per desk, IVR menus and voice bots that answer the call.
How it works
This is how it is used day to day, on the same document as the rest of the modules.
Asynchronous for what can wait: email, portal and QR forms. Real-time for what cannot: WhatsApp, Teams, Slack, web chat, phone and meetings.
With your organization’s credentials: the Microsoft or Google app registration, the Meta account and the phone system. We tell you in writing what is needed.
Each mailbox and each WhatsApp number, to its group. In the inbox, whoever accepts a conversation owns it.
The email, the message and the call stay on the document’s timeline, in order. The big picture is on the communications page.
marIA classifies incoming email and suggests the reply in the inbox. On the record it writes the draft, and a person sends it. It transcribes and summarizes calls, and the web chatbot answers from your documentation before handing off to a person. Every operation is logged with who started it, the model and its cost. Spending has the monthly cap you set.
Where it is used
Industry solutions
Use cases by department
Honesty
It does not replace your phone system: attendo’s telephony connects to the one you already have.
It does not post attendo notifications to Teams or Slack: they are conversation channels that come into the inbox.
It does not send campaigns over WhatsApp: it is a one-to-one service channel.
Works with
Laptops for the Engineering team
All activity on the document, in order, with its author and channel
See TimelineTicket TK-2481 · closed
How did we do?
“Fast, and very clear about the quote”
Ask for feedback on closing and turn a low score into work
See Satisfaction surveys
SELECT supplier, COUNT(*) … GROUP BY supplier Ask in plain language. Get answers from your data, with the source.
See AI-Chat and DB AssistantFlows, phased processes with approvals, and AI inside the flow
See Flows and AI-FlowsGlossary
Customer service
Omnichannel inbox · shared team inbox
A unified inbox is the screen where a team receives and answers conversations from all its channels, such as WhatsApp, website chat or Teams, without switching programs.
Support and service
Omnichannel support
Omnichannel means that every channel a customer uses to contact you feeds the same record and the same conversation.
Support and service
FRT
First response time is how long your team takes to send a meaningful reply after a ticket comes in.
Support and service
Service level agreement
An SLA (service level agreement) is the written commitment, usually part of a contract, on how quickly you will respond to and resolve a customer’s tickets.
Frequently asked questions
An asynchronous channel can wait: an email, a portal submission or a form is answered within its deadline. A real-time channel needs an answer on the spot: a WhatsApp message, a chat or a call.
Yes. What people write to the attendo bot in Teams, or in the Slack channels where it is present, reaches the unified inbox. You answer it from attendo, as text.
Yes. The meeting is linked to the document and the customer, with its recording and transcript.
The Lyria phone system. If you have a different one, we assess it before implementation.
Yes, with your Meta account, and we set it up with you. Meta approves templates before they are used. For small volumes there is a lighter, unofficial channel that only sends text.
Request a demo
We will show it to you with your own document types and the way you work. If it is not a fit, we will tell you.
Would you rather talk first?