AIstap

Use case · Wholesale · Logistics

Stop looking up where your customer's order is.

A customer asks where their order is. Someone looks it up in the order system (ERP) and the planning software (TMS) and calls the warehouse. The automation looks up the status and prepares a draft reply; your order desk checks it and sends it.

ERP: the system that holds your orders, stock and invoices. TMS: the software you plan your trips in.

Show us your process See the difference

Free · 30 minutes online · one process · no obligation After that: pilot from €2,450 · monthly package from €295 · excl. VAT

How the work runs

  • Email
  • Question

AIstap

the automation

  • Reads
  • Looks up
  • Prepares

Your mailboxFICTIONAL EXAMPLE

Reply · order 58307Draft

Order
58307
Status
On its way
Trip
R-2214
Delivery
02-1002-10 or 03-10?

In doubt? To your team first.

The order system says delivery 02-10, the planning says 03-10. Your order desk decides.

Sound familiar?

  • Phone rings, work stops

    An employee puts their work down again and again for the same customer question: where is my order?

  • Two systems, one answer

    The answer is scattered: the order in one system, the trip in another.

  • Call warehouse, call customer

    Someone calls the warehouse to ask for the expected delivery, and then calls the customer back.

Today. And with AIstap.

Today

4 steps by hand

  1. Customer's question
  2. Look up order
  3. Check the planning
  4. Call the warehouse
  5. Type the reply

With AIstap

1 step for your team

  1. Customer's question
  2. The automation reads
  3. Looks up the status
  4. Draft reply is ready
  5. Your order desk sendsyour team

Possible impact

  • Less searching in several systems
  • Fewer interruptions for your team
  • A better view of open questions

Possible impact, not a promise: what it brings depends on your process.

What AIstap can build.

An example. What we build for you is agreed upfront.

  • Mailbox connection

    Where your customers' questions arrive.

    A connection to the mailbox your customers' questions arrive in.

  • Looking up status

    Order, shipment and expected delivery from your systems.

    Looking up order, shipment and expected delivery in your order system and planning software.

  • Check when in doubt

    Two systems disagree? To your team first.

    A check: if two systems disagree, your order desk sees the question first.

  • Draft reply

    Draft in your mailbox. Your order desk sends.

    A draft reply in the mailbox; it only goes out once your order desk sends it.

Checked by your team.

The automation prepares. Your people approve and decide when something is unclear.

The automation

Your order desk

  1. DetectThe automation sees what arrives.
  2. PrepareReading, checking and getting it ready.
  3. ApproveSomeone on your team approves, or decides when in doubt.
  4. ExecuteAfter approval it is final in your system.
  5. Follow upWhatever is open stays in view.

Your team stays in control.

  • Try it yourself

    Reply · order 58307Draft

    Delivery02-10 or 03-10?

    02-10 or 03-10?

    Your order desk decides in doubt

    If the order system and the planning disagree, your order desk sees that first. The automation does not pick a date itself.

  • The automation

    • Reads
    • Looks up
    • Prepares

    Your team

    • Explaining delays
    • Offering solutions
    • Sending replies

    Explaining and solving stays with people

    Explaining a delay or offering a solution is done by your order desk. In this set-up the automation decides nothing about your customer.

  • Sending stays with your team

    In this set-up no reply goes to your customer without your order desk. The draft stays a draft until your team sends it.

In the systems you already have.

Which connection is possible is something we look at in the free analysis.

The questions arrive in your own mailbox; the status is in your own order system and planning software. Whether and how they can be connected is something we look at in the free analysis.

  • Mailbox (In this example)
  • Order system (In this example)
  • Planning software (In this example)
  • Spreadsheet
  • Accounting
  • Customer portal

In this example

What it costs to start.

From email question to draft reply: one process, three systems. A pilot-sized job.

  1. STEP 0

    Free analysis

    €0

    You show us one process.

    • 30 minutes online
    • A one-page summary
    • Free, no obligation
  2. STEP 1 Recommended first step

    Pilot

    from€2,450

    One working automation.

    • Max. 2 systems
    • 1 to 2 weeks
    • Fixed price, upfront
  3. ONGOING · AFTER A PILOT

    Monthly package

    from€295/month

    We keep it running.

    • Hosting and monitoring
    • Fixes and AI costs
    • Cancel any month

Prices excl. VAT

All prices and steps

Questions about this use case.

Can customers get the answer directly themselves?

Not in this set-up: your team reads the draft reply and sends it. The automation looks things up; the contact with your customer stays yours.

What if the status in our system is wrong?

The automation only knows what is in your systems. If two systems disagree or the status is missing, your team sees that first.

Does this work for questions by phone too?

This example is about questions by email. Whether phone or chat can work too is something we look at in the free analysis.

More use cases.

Email from your customer to Your TMS

Stop retyping transport orders.

Prepared in your planning software (TMS). Your planner decides.

Logistics

See all use cases

Step 0 · free

Show us your process.

  1. We call or emailTo schedule a time
  2. You show us30 minutes online
  3. You get a summaryOne page

Free, no obligation

Prefer to email directly? [email protected]

All fields are required. We will call or email you back.