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.
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