AI co-worker / Customer service / Business case 2

The shared inbox owns our day.

Next up

Every message becomes a case: answered from your approved knowledge, or routed with a summary. A price, a date or a commitment waits for a person.

Ready to build. Live in six weeks. Works in Outlook, Gmail, Zendesk, Teamleader or Odoo.

Book 30 minutes See the 13 co-workers
The job today

Monday morning, info@

08:30

Sixty messages since Friday. Where is my order, send that invoice again, can you deliver Thursday. Two people start at the top.

11:15

A customer asks the same question a third time, to a third person. Each answers; nobody knows what the others wrote.

17:40

Tuesday's complaint is still unanswered. It sat behind thirty easier questions all week.

What nobody measures

Two questions for your Monday meeting

How many of last week's messages asked what your website already answers? How many customers wrote twice before anyone replied?

Most firms cannot say; the inbox does not count. With a co-worker on the job, every message is a case with a number, an owner and a clock.

The job with the co-worker

The same Monday, every message a case

  1. 08:30 – Logged and sorted

    Every message becomes a case: who, what, which order. Questions your approved knowledge answers get a drafted reply with the source. The rest go to the right person with a summary.

  2. 08:45 – Approved or routed

    A person approves every reply in the first weeks; then routine answers go out under your rules. A price, a date or a commitment waits for the person you name. The complaint sits on top.

  3. All week – Nothing goes quiet

    The customer hears back at every step until the case closes. A second message on the same question lands on the same case, not with a third colleague.

What you are buying

The rules it works under

Control card Customer Service
Permissions
Reads the shared inbox, your approved knowledge, the order and customer records. Writes cases, drafts and summaries. Never changes an order, issues a credit note or touches invoicing.
Approval gates
Every reply in the first weeks. Then any price, date or commitment change, any refund or credit note and any complaint waits for the person you name.
Limits
Answers only from knowledge you approved; routes when it has none. A ceiling on replies per customer and per day, within working hours. Never escalates or closes a complaint on its own.
Record
Every message, case, draft, source, approval and send is logged with time and owner. You decide retention and who may review.
Stop
One switch pauses it. A named owner on your side decides. Open cases stay open, with their history, for your people.
Data
Stays in Europe, in your own mailbox and service tools. Never used to train anything. Sub-processors on the Data page.
Transparency
Every draft and message is marked as prepared by the co-worker, as the EU AI Act requires since August 2026.

Same seven lines on every co-worker page. How we hold them is ours; that they hold, you check in the log.

The demonstration

Ninety seconds, your inbox, synthetic customers

One Monday morning, sixty messages to a sorted case list, in the tools you run.

See it on your own inbox — book 30 minutes
  1. 01The inboxSixty messages since Friday. Each becomes a case with a name, an order and a question.
  2. 02The replyAn invoice copy from the ledger, source shown. Your colleague approves. The delivery-date change waits for the planner.
  3. 03The logFriday: every case closed, every answer on record, the complaint handled on Monday.
After go-live

What we measure

Three indicators, reported monthly. No figure here until we have measured one.

  • First reply minutes from a message arriving to the first reply sent.
  • Touch rate the share of cases a person had to handle, and why.
  • Asked twice how many customers wrote again before an answer.
Before we build

What we need from you

  • Your approved knowledge: price list, delivery terms, the replies you already copy and paste.
  • Access to the shared inbox and the order or customer system behind the answers.
  • The rules we agree in the diagnostic: what is routine, what waits for a person, who owns a complaint.
  • Three names: who approves, who gets complaints, who holds the switch.

Works with

Outlook and Microsoft 365, Gmail and Google Workspace, Zendesk, Teamleader, Odoo — and your order system through its API.

Investment

Six weeks, a fixed fee, yours

  • Time to live six weeks from the signed scope and price.
  • Fixed fee set in the signed scope and price before we build.
  • Managed service optional, monthly. We run it, watch the log, adjust the rules with you. You keep control.

Three questions about this job

  1. What if it does not know the answer? It says so and routes the case to a person with a summary. It never guesses.
  2. Does the customer know they are dealing with AI? Yes. Every message says the co-worker prepared it and names the colleague responsible.
  3. Can it answer the phone? Not yet. Phone intake is a later co-worker. Today: email, web forms and your service tool.
Business case 2

Which question did your team answer three times last week?

Thirty minutes, no slides. Bring last Monday's inbox; we walk through it.

Book 30 minutes See the 13 co-workers