AI for customer service
Sorting incoming questions, answering them from your own knowledge, and only sending once approved.
Those hours go into solving the hard questions in person, instead of into sorting and typing standard answers.
Customer service is a department in Altramano with 10 ready-made templates for sorting and answering incoming questions.
What runs on its own
- Sorting incoming questions by urgency and subject.
- Proposing a draft answer from your own knowledge base, with its source.
- Creating a ticket from a WhatsApp message or a mail.
- A weekly overview of recurring complaints.
- Informing customers automatically when a status changes.
10 templates for this department
Every template comes with a manual in plain English. Choose one, point it at one or two integrations, fill in three settings at most.
| Sjabloon | Soort | What it does |
|---|---|---|
| Appointment confirmation and reminder | automation + assistant | A new appointment in your table? |
| First-line responder | AI agent | An assistant that answers customer questions from your own documents. |
| First-line responder (table) | AI agent | An assistant that answers customer questions from your table of frequently asked questions and your documents. |
| Escalation after 24 hours | automation | Tickets still set to New after 24 hours land in a manager's mailbox. |
| Customer message → proposed reply | automation | Every incoming customer message (a mail or a forwarded WhatsApp message) gets a proposed reply from your knowledge base table. |
| Mailbox → ticket with classification and assignment | automation + assistant | Every mail in your service mailbox becomes a ticket in a table, with a category, an urgency and a proposal for who picks it up. |
| No-show follow-up | automation | Is an appointment set to No-show? |
| Return or complaint → solution for approval | automation | A complaint or a return gets a proposed solution; after your approval the reply goes to the customer. |
| Satisfaction question after closing | automation | After a ticket is closed the customer gets a short satisfaction question, for approval first. |
| Frequently asked questions → knowledge base table | automation | Every week the closed tickets are summarised into new frequently asked questions for your table. |
In the Studio
AI agents for customer service
Customer service agent
Answers customer questions by mail, chat and WhatsApp from your own knowledge, and hands over to a person when needed.
Saves, estimated: ± 5 hours a weekRequest sorter
Gives every incoming question a label and a priority and puts it with the right colleague.
Saves, estimated: ± 5 hours a weekComplaint handler
Summarises a complaint, drafts a reply and makes sure the customer gets a solution.
Saves, estimated: ± 2 hours a weekReview responder
Answers Google reviews in your tone: a thank-you for a good one, an invitation for a poor one.
Saves, estimated: ± 30 minutes a weekAppointment maker
Books appointments in your calendar, confirms them to the customer and sends a reminder the day before.
Saves, estimated: ± 2 hours a weekReturns handler
Handles returns from your web shop according to your rules: from request to refund, with a person for the exception.
Saves, estimated: ± 3 hours a weekSatisfaction poller
Sends a short survey after a job or an order and summarises the answers for you every week.
Saves, estimated: ± 1 hour a week
What runs on its own in your industry
Integrations these templates use
One workspace
Everything in one place.
What you see on this page happens in one place. You ask the Studio, automations and AI agents do the work, and what your systems cannot do, you add with an app. Everything works with your Company Brain and with the systems you already have.
Start with what you need now. The rest is already included.
See what is in each tierYou set the limit
What falls within it runs by itself. What falls outside it comes to you first.
For example: it books invoices under €1,000 straight through; above that, they come to you first. You choose that amount yourself. You can look back at everything that has happened.
Frequently asked questions
Does AI answer customers by itself?
Only if you allow it. By default a draft is ready from your own knowledge, with its source; an employee approves it.
Does it work with our ticket system?
Zendesk and Jira are on straight away; Freshdesk, Intercom and Crisp we switch on as soon as you need them. No ticket system? Then the mailbox works with Tables.
What happens with an angry customer?
The automation marks the urgency and the tone and gives the message priority. The answer stays human work.
What if the AI makes a mistake?
You set the limit. Above it, it comes to you first, and you can look back at everything.
Are we allowed to do this with our customer data?
Your own environment is in Amsterdam. If the data has to stay in the EU, Altramano only uses providers that process in the EU.
