Inbound requests

Automate inbound requests: every email and form sorted and prepared before you open it.

Emails, forms, attachments: we sort, qualify, and draft a reply. A human approves before it's sent.

The problem

A shared inbox isn't a process.

When requests arrive through several channels and get handled as they come, urgent ones get buried and the same answer is rewritten a hundred times.

Things we hear a lot

Nobody knows who replied to which email.

We rewrite the same answer every day.

We open attachments one by one to find out what they are.

Urgent requests are spotted too late.

What we deliver

Four deliverables, in this order.

01

A map of your requests

Types, volumes, who handles what: we lay out what actually comes in before deciding what to automate.

02

Automatic sorting and qualification

Each request is classified by type and urgency, and missing information is flagged on arrival.

03

Pre-drafted replies

Built from your standard answers and in your tone. They're reviewed and sent by a person, never on their own.

04

Shared tracking

Who handles what, since when, with what history: the team sees the status of every request.

How it runs

Three steps, without ever switching off your inbox.

01

Mapping

2 to 3 weeks

We analyze one real month of requests: types, volumes, who handles what. Together we set the categories, the urgency rules and your standard replies.

02

Parallel build

6 to 12 weeks

Sorting first runs alongside your usual handling: the tool classifies and suggests replies, and you compare with what you would have done. We tune it every week until the classification is reliable.

03

Switchover

At the end of the build

The team works in the shared tracker: the tool prepares, a person approves. You can add a category or edit a standard reply yourselves.

No reply is sent without human approval, at any stage.

Before / after

What actually changes.

SortingBy hand, email by emailClassified on arrival
ReplyWritten from scratchPre-drafted, reviewed, sent
Urgent itemsSpotted by chanceSurfaced first
TrackingIn everyone's headVisible to the whole team

Typical cases

Where it helps.

A multi-topic customer service desk

Quotes, support and follow-ups arrive at the same address: each request goes to the right person with the right context.

Cases with attachments

An admin team that must check each file is complete before processing it.

Routing to the right expert

A firm or consultancy where requests must land with the relevant specialist.

Typical situations, not client references.

When not to call us

We'd rather tell you upfront.

You get a few requests a week: an email rule is enough.
Every request is unique and needs a fully custom answer.
You're after a public chatbot on your website: that's a different project.

FAQ

What we get asked most.

Another question? [email protected]

No. It prepares, a human approves. You can later decide to automate the simplest cases, or not.

Free call · 30 min

We'll look at your case in 30 minutes

Free call, no commitment. We'll tell you honestly if it's automatable, and if now isn't the right time.