Customer communication, multi-tenant and multi-audience
One inbox.Seven channels.An AI that knows who it's talking to.
LBD Business Communicator puts WhatsApp, email, Instagram, Messenger, phone, your web widget and your mobile app into one conversation — then adds an AI agent grounded in your own knowledge base and kept separate per customer type. A partner-only document will never surface in an answer to a customer.
- 7
- native channels, one thread
- 15
- help center languages
- 50KB
- the widget: it won’t slow your site
- 0
- documents out of their audience
Can I move Thursday’s appointment…
September invoice: I need the…
Hi! How do I upload the documents…
The product, in pieces
Seven pages, one per thing it does.
We stopped putting it all on one page. Each of these explains one thing properly, with the part of the product that does it.
- 01
Channels
WhatsApp, email, social, phone, widget and app in one thread.
- 02
Separate audiences
Customers and partners with distinct knowledge, help centers and AI.
- 03
AI agent
Answers from your content, cites its sources, hands over when it should.
- 04
Shared inbox
Assignment, notes, mentions, macros and shortcuts for the people in it.
- 05
Automation
Automated journeys, data collection and outbound campaigns.
- 06
Help center
A public help center per audience, in 15 languages.
- 07
Platform
What is underneath: isolation, APIs, logs, where the data runs.
- And thenTwo real customers, in productionSee the case studies
The engine: AI + automation
It answers from day one. And gets better every week.
Not a chatbot with a decision tree. An agent that reads your knowledge, answers with its sources attached, collects what is needed, hands over to a person when it should — and learns from every correction your team approves.
The loop that makes it better
- 01
The customer asks
On WhatsApp, in chat, by email.
- 02
The agent answers
From your content, with sources.
- 03
An agent corrects it
When needed, in one click.
- 04
It becomes knowledge
The approved correction goes back in.
This is where the difference compounds: after a month the agent answers in your team’s words, not the model’s.
First reply in seconds
At 3am, on a Sunday, in August. The repetitive question gets the exact answer while your team sleeps, and whoever wrote in is not waiting until Monday.
It learns from your team
When an agent corrects an answer and the correction is approved, it becomes knowledge. The best hand-written replies are mined from conversations and proposed as new content: the system improves by being used, not by being updated.
It does not make things up
It answers only from what you gave it, and every reply carries a "Sources" button with the articles it used. If the question leaves the perimeter, it hands over to a human with the context ready.
It collects the details first
Email, phone, reference number: asked with an in-chat form or read out of free text. The agent receives a briefed conversation, not a "hello" to decode.
It automates journeys, not just replies
Buttons, data collection, help-center search, conditions and routing to the right team. What is a procedure on a sheet of paper today becomes a path that walks itself.
It reads what it is sent
Photos of the receipt, the screen, the document. The agent actually looks at them, on any channel, instead of replying that it cannot see images.
Separate audiences
Two audiences. Two knowledge bases. No leaks.
Customers and partners do not ask the same questions and do not deserve the same answers. Here the audience is not a label on a contact: it is the dimension along which content, answers and permissions are separated. And the database enforces it, not a checkbox.
Try it: switch audience and watch what stays reachable.
Asking as
Can I move Thursday’s appointment?
Retrieval
- Moving or cancelling an appointmentCustomersIn context
- Fees and payoutsPartnersOut of audience
- Response times and availabilityCustomersIn context
- 2026 partner agreementPartnersOut of audience
- Invoicing and payment methodsCustomersIn context
- Uploading a case filePartnersOut of audience
Answer
You can move it up to 24 hours before, from your account or right here — no charge within that window.
Moving or cancelling an appointment3 documents out of 6 reach the answer. The rest aren’t hidden: for this conversation they don’t exist.
One company can’t see another
Every company sees only its own data, and the database itself enforces it — not a check written in the application, which a bug can skip.
Separate knowledge
Articles, files, pages and notes are labelled per audience. The search rules the others out before it looks, not after it finds.
Separate answers
Tone of voice, behaviour rules and the details to ask for are set per audience, not once for everyone.
Case studies
Two stories, told in full.
Instead of a wall of logos, two implementations explained in detail — picked because they sit at opposite ends of the size range. The public help centers are open: you can check them without asking anyone’s permission.
Two audiences, one inbox: how Transfeero talks to passengers and drivers without mixing them up
Transfeero runs private transfers worldwide and has two audiences with nothing in common: the passenger who booked, and the partner who drives. Each gets its own help center, its own knowledge and its own AI agent.
- help.transfeero.com
A small team answering like a big one: Go-Etna
Go-Etna takes people up Mount Etna. It is a small team, and during the day it is on the volcano rather than in front of an inbox. The AI agent covers the first line, in several languages, including when the office is closed.
- help.go-etna.com
Why only two? Because a case study is worth reading when it is detailed. We would rather publish two implementations explained all the way down than twelve cards claiming "+40% efficiency". The other projects are not here because publishing a customer’s name is their decision, not ours.
Where it fits best
The situations it carries best.
Not a list of industries: these are the situations where separating audiences and automating the first reply make a measurable difference. If you recognise yourself, the demo starts there.
- 01
You have customers and resellers
Two worlds writing to the same team, who must not see the same documents. This is the case audience separation exists for.
- 02
You work by appointment
Reschedules, cancellations, reminders and "what time are we meeting?". Questions with one exact answer, always arriving while you are busy.
- 03
Your year has peaks
Three months with no air and nine where one more person does not fit the books. An automated first line absorbs the peak without hiring.
- 04
You answer in several languages
Content is written once and published in 15 languages, each with its own address. The agent replies in whichever language it is written to.
- 05
WhatsApp is your main channel
Official number, approved templates, one live chat per number. Not a handset with automation bolted on.
- 06
You already have a help center
It gets imported rather than rewritten, and the AI agent starts answering from it. The work you did is not thrown away.
10 — Frequently asked
The questions we always get asked.
These are the answers we give on the phone, written out in full. If your question is not here, call us: the number is just below.
01What is an omnichannel customer communication platform?
It is software that gathers the messages arriving from different channels — WhatsApp, email, Instagram, Messenger, phone, your website chat and your app chat — into one shared inbox, and ties them to a single contact and a single conversation. The benefit is organisational rather than technical: whoever answers stops hopping between tools and sees that person’s entire history in one place.
02How is LBD Business Communicator different from similar tools?
In how it separates audiences. Most platforms assume a company talks to one kind of counterpart; here customers, partners, suppliers or agencies are a first-class dimension, each with its own help center, its own knowledge base and its own AI agent. A partner-only document is not hidden from a customer: for that conversation it does not exist, because the separation is enforced by the database as well as by the application.
03Can the AI give my customers wrong answers?
It can, as with any generative system, which is why the agent is tied to your own content rather than to the model’s general knowledge. Every reply carries a "Sources" button showing an agent which articles it was built on, and you decide with explicit rules which topics must always reach a person. When a question falls outside the configured perimeter the agent does not improvise: it hands the conversation to a human with the context already assembled.
04Do we need a technical team to install it?
Not to get started; yes to integrate it deeply. The widget is one line of code on your site and channels are connected from the interface. You only need someone technical to hook up your back office or CRM through the public API, or if you choose to run the platform on your own servers instead of ours.
05Where is the data stored, and who can see it?
The main infrastructure is in the European Union, on servers in Germany, and each company sees only its own data: the database itself enforces that, not a check written in the application. For your customers’ data you are the controller and we are the processor, under an agreement compliant with Article 28 GDPR. Nothing from your workspace is used to train artificial intelligence models.
Let’s talk
Half an hour, and you’ll know.
No recorded deck. You tell us how you answer today, we tell you what would change and what it costs. If it does not make sense, we say so.
Mon–Fri, 09:00–13:00 CET