Assisted customer service: request sorting, prepared replies, reviews

What happens today

A customer who waits is a customer who doubts.

The problem isn't the quality of replies. It's the delay before the first one, and the time spent on those that repeat.

Requests come from everywhere

Email, form, social, phone. No overview, no certainty that each one has been picked up.

The same questions, every week

Opening hours, lead times, prices, where is my order. Every reply is rewritten although it already exists ten times in the sent folder.

Reviews go unnoticed

A negative review sits unanswered for days, a positive one is never thanked. Both are publicly visible.

How it works

One entry point, a sort, a prepared reply, an approval.

The workflow gathers and prepares. The decision to reply, and what is replied, stay human.

Step 01

Everything lands in one place

Requests from your different channels are gathered in a single sheet, with arrival time, type and owner. An acknowledgement can go out immediately, with the announced response time.

Step 02

Routine replies are prepared

For recurring questions, a draft is prepared from your standard answers and the request's context. You review it, adapt it and send it. Special cases are flagged to you without a draft.

Step 03

Reviews are tracked

A new review is detected, a draft reply is prepared. You approve before publishing. Nothing appears publicly without you.

What changes

Before and after: what actually changes.

The service level doesn't change. The first-response time and the energy spent on the repetitive do.

Situation	Today	With the workflow
A request arrives	In one inbox among others	Logged, typed, assigned, acknowledgement sent
Routine question	Rewritten every time	Draft ready to review, in your tone
Special case	Lost among the rest	Flagged to the right person, with context
An online review	Discovered by chance	Detected, reply draft prepared, approved by you
Knowing what's left to handle	Impossible	One sheet: open, in progress, closed, with response times

You stay in control

What stays in your hands.

A customer reply carries your name. The workflow prepares and organises, it doesn't speak for you.

No reply without approval

Every draft is shown to you. You can decide later to automate certain simple replies, such as the acknowledgement.

You define what counts as “routine”

The standard answers are written with you. Anything that doesn't match is treated as a special case.

Every request has an owner

Assignment follows your rules: by type, by customer, by availability. A hand-off is always explicit.

Reviews are handled honestly

Public reply to every review, with no filtering or misleading solicitation, in line with the platforms' rules.

Tools involved

Your current tools, connected together.

The workflow plugs into the tools you already use. Compatibility is checked for your case, never assumed.

n8n· orchestration Your mailbox· intake and detection Website form· intake Google Business Profile· reviews

OpenAI· draft to review

Airtable· shared database

“Replying quickly to simple questions is what frees up time to reply well to the hard ones.”Design principle

Illustrative scenario

An online shop, one Tuesday.

A fictional example to show the sequence. The timings and rules are the ones you would choose.

9:02 am

“Where is my order?”

The request arrives via the form. It's typed “order tracking”, an acknowledgement goes out. A draft with the status and tracking link is prepared. You approve at 9:10.

9:30 am

Unusual return request

A customer asks for a late return for a particular reason. No draft: the case is flagged to you, with the customer's history.

11 am

4-star review

A review mentions damaged packaging. A draft thanks the customer, acknowledges the point and offers a gesture. You adjust the gesture and publish.

2 pm

Three questions about lead times

Three similar requests arrive. Three drafts are ready with the lead time for each product. You approve all three in two minutes.

6 pm

Daily summary

The sheet shows 14 requests received, 13 closed, one waiting for the carrier's reply. Nothing is lost.

Illustrative scenario: the timings, messages and rules are examples. They are defined with you, from your tools and the way you work. An illustration is not a promise of results.

Frequently asked

Before you ask.

Is this a chatbot?

No. No customer talks to a machine. The workflow prepares replies that you approve, and organises what comes in. The contact stays human.

Which channels are possible?

Email, website form, Google reviews, and in some cases certain messaging services. We check what each channel technically allows.

What if the prepared reply is wrong?

That's exactly why you review it. The standard answers are written with you, and cases that don't match get no draft.

Can we measure response time?

Yes. The sheet records arrival time and reply time. A weekly summary can be sent to you.

Every request gets a reply,
and the reply stays yours.