Skip to content

AI chatbot · orders · shipments · returns

“Where is my order?” The answer is already in your programs.

Order status, shipment, availability, returns: the same questions every day, and every time someone opens three programs to answer. We build an AI assistant connected to your orders and shipments, which answers at once and hands over to a person the cases that need one.

  • Answers with the real order data
  • Hands over when needed
  • People know they are talking to an assistant
requests received this morning
  • 09:02 Where is my order 5531? out for delivery answered
  • 09:10 Can I change the address? not shipped to approve
  • 09:14 Is the 40 mm bracket available? 60 pieces answered
  • 09:21 How do I return an item? procedure sent answered
  • 09:30 The parcel arrived broken photo collected to a person

Closed with no wait 3 of 5

evenings and weekends too

Example with data that is not real. The answers come from your programs, not from the model’s memory.

3 hours a day to answer 30 requests, 6 minutes each between looking up and replying

60 hours a month, over 20 working days

Evenings, weekends simple questions get an answer even when the office is closed

Reference values for an online shop with 30 requests a day.

Free check

Free check: how many requests can an assistant close?

Tell us how many requests you receive, from which channels and which programs you use for orders and shipments. We reply in writing: which questions it can close alone and which must stay with a person.

Ask for the check Free, with no commitment.

What it costs today

Put your own numbers in. See what answering by hand costs.

Customer requests every day, times the minutes it takes to find the answer and write it.

Count the requests on order status, shipments, availability and returns, from every channel.

Try it with your numbers

An estimate: set it yourself, including contributions and overheads

a year of work back to the team

Today
After
Let us talk about these numbers
How the sum works

The sum: requests a day times minutes per request, over 240 days. After, about half stays with a person, which is the cases that need a decision. It is a reference value: the real share is measured on your requests.

The problem

The questions are always the same. The answers sit in three programs.

To tell a customer where the parcel is you need the order, the shipment and the courier’s site. Six minutes for an answer that already exists.

01

The same questions, every day

Where is the order, when does it arrive, is it available, how do returns work. Only the order number changes.

02

Three programs for one answer

Ecommerce, ERP, the courier’s site. Whoever answers is the bridge between all three.

03

Answers that come late

In the evening and at the weekend nobody answers. Meanwhile the customer writes again, or opens a dispute.

04

Little time for the real cases

The broken parcel and the angry customer wait in the queue behind twenty “where is my order?”.

Before switching it on

Six rules for an assistant that does no harm.

A chatbot that answers badly costs more than a late answer. These choices are made before any code is written.

It answers from data, not from memory

It reads the order status from your ecommerce and the shipment from the courier, at that moment.

For exampleOrder 5531: “shipped yesterday, out for delivery today”, with the link to follow it. Not “it usually takes 3 days”.

It checks who is asking

Before giving information about an order it verifies that the person is the right one.

For exampleOrder number plus the email of the purchase. Without a match, no data is shown.

It hands over

Complaints, damage, exceptions and customers who ask for it go to a person, with the conversation already summarised.

For example“The parcel arrived broken”: the assistant collects photo and order number, opens the request and says a person will reply.

It reads a lot, writes little

It starts read-only. Actions such as changing an address or opening a return go through a confirmation.

For exampleAddress change on an order not yet shipped: the assistant prepares the change, a person approves it.

It says what it is

People know they are writing to an automated assistant and can ask for a person at any time.

For exampleFirst message: “I am the shop’s automated assistant. To talk to a person, write operator”.

Everything stays on record

Every conversation is logged: what was asked, what it answered and from which data.

For exampleAt the end of the month you see the ten most frequent questions and the ones the assistant could not answer.

A morning of requests

What it closes alone, and what goes to a person.

Questions with data behind them get an answer at once. Those that need a decision reach a person, already prepared.

TimeRequestWhere it readsOutcome
09:02Where is my order 5531?Ecommerce and courier Answer with tracking
09:14Is the 40 mm bracket available?Stock Answer with availability
09:21How do I return an item?Terms of sale Procedure sent
09:10Can I change the address?Order not yet shipped Change ready, to approve
09:30The parcel arrived brokenPhoto and order number collected Passed to a person
09:41I would like a discount on my next orderNo rule Passed to a person

Example with data that is not real.

Ready-made or connected

A chatbot that answers with the FAQ, or one that reads the order?

Ready-made chatbots answer general questions well. The questions that weigh, though, are about one specific order.

The ready-made chatbot

  • Answers with the FAQ and the site pages
  • For the order it often points to the contact form
  • Connects to the platforms it supports
  • Monthly fee, sometimes per conversation

The assistant connected to your programs

  • Reads order, shipment and stock at that moment
  • Closes the simple questions alone
  • Connects to your ERP and your courier too
  • What it may say and do is your decision

If you sell on a common platform and tracking answers are all you need, a ready-made app can be the right choice: it costs less and installs quickly.

How we start

First the real questions, then the assistant.

We start from the requests you receive today, not from the ones we imagine.

  1. 01

    Free check

    You tell us volumes, channels and programs. We tell you in writing which questions an assistant can close.

  2. 02

    Trial on your requests

    A sample of real requests, anonymised: the assistant answers in test mode and we count the right answers. Fixed price, deducted from the project if you go ahead.

  3. 03

    Live, one channel at a time

    First the site chat or email, read-only. Actions and other channels are added later.

Customer data

Customer data, kept to the minimum needed.

An assistant that talks to customers handles personal data. What it reads and where it goes is written down first.

  • Only the order of whoever asksThe assistant reads one order at a time, after verifying who is writing.
  • Where the model runsOutside AI service, also with servers in Europe, or a model on your own servers: the choice is made at the start and is in the proposal.
  • Log and correctionsConversations stay logged and can be reviewed. Rules are corrected without redoing everything.

Before you write to us

With ten requests a week, you do not need it.

It makes sense if

  • You receive dozens of similar requests every day
  • The answers sit across ecommerce, ERP and courier
  • Customers also write in the evening and at the weekend
  • Whoever answers has no time for the hard cases

You do not need it if

  • You receive few requests, all different
  • A ready-made app for your platform is enough
  • You want to remove people from customer service altogether

Tell us about your case

What clients say

Verified clientClient, web application
Sebastiano is a true professional. The communication was excellent, and the results were flawless. If you need someone competent to handle complex issues, he is the right person. Highly recommended!
Maintenance and fixes on an existing application, 2026 (extract)

Verified review, anonymised for privacy.

Frequently asked

Questions on this topic.

Which channels can it answer on?

The site chat and email: those are the channels we connect. WhatsApp Business has rules and costs set by the platform: if you need it, we check them at the start, before promising it.

Which ecommerce platforms and ERPs does it work with?

With those that allow reading orders and shipments through an API, a database or files. WooCommerce and Shopify do. For the ERP and the courier we verify it case by case.

Can it give wrong answers?

On order status it answers with the data read at that moment, so making things up, the typical chatbot error, has little room here. When the question falls outside the rules, it goes to a person.

Do customers know they are talking to an AI?

Yes. Saying that it is an automated assistant is what the European rules on artificial intelligence ask for. Being able to talk to a person at any time is our own rule, and it is written in the proposal.

Can it take actions, such as a return or an address change?

Yes, with a confirmation. It starts read-only. Actions are added one at a time, and those that touch money or shipments go through a person.

What does it cost?

The AI cost per conversation is low. The cost of the project is in the connection to your programs and in the rules, with a fixed price agreed upfront. The initial trial is priced separately and deducted from the project if you go ahead.

Does it replace the people in customer service?

No. It automates the answers to the repetitive questions, so people have time for complaints, exceptions and important customers.

Start with the problem

Tell us how many requests you receive and where they come from.

We tell you in writing which ones an assistant can close, and which it cannot.

  • The first check is free and commits you to nothing
  • Every message gets read, there is no call centre
  • Fixed price and payment by milestone
  • Italian and English, VAT invoices
  • No phone call unless you want one
  • If nothing should be built, we will say so

Prefer to write directly? [email protected]

No newsletter, no unsolicited calls. A direct reply from the developer, within one working day.