Transport enquiries don’t wait for a quiet moment.
An AI assistant collects transport enquiries on WhatsApp and prepares the details for dispatch.
Route, cargo, preferred dates and contact details. Your team checks price and capacity.
Collect transport enquiries outside office hours.
Prepare route, cargo and preferred dates for assessment.
Keep your dispatch team in control of price, capacity and the response.
Your workflow. Your number. Your team stays in control.
For logistics teams that want enquiries ready to review.
Another way to receive transport enquiries. Built around your dispatch workflow.
Between route planning, phone calls and WhatsApp
The enquiry has arrived.
The details haven’t.
Before dispatch can assess it, the questions begin:
“Where is pickup and delivery?”
“How many pallets, and what weight?”
“When will the cargo be ready?”
The assistant asks for the agreed transport details in the WhatsApp conversation and summarises them for your team. Even while dispatch is coordinating a route or is away from the desk.
Your team starts its assessment with a prepared enquiry.
Four pallets. A new enquiry.
Fictional example. No price or capacity confirmed.
An example from everyday logistics work
From “4 pallets to Vienna” to a clear transport enquiry.
Fictional example. Questions and handover rules are agreed for your operation. This is not a live chat or a confirmed transport.
Fictional example. Questions and handover rules are agreed for your operation. This is not a live chat or a confirmed transport.
The assistant collects the enquiry. It does not promise a price or available capacity. Your dispatch team reviews it and responds.
Transport details at a glance.
Fictional example. Open questions are flagged for dispatch.
Give dispatch the details it needs
The details together. The next step clear.
The assistant asks the questions.
Dispatch takes over prepared.
Pickup and delivery locations, cargo details, preferred dates and contact details are collected according to your rules. Your team checks feasibility, capacity and price in its existing workflow.
Like a digital enquiry note:
The details are prepared. The transport decision stays with your team.
WhatsApp enquiry assistance for logistics
What does the assistant handle?
It guides customers through a structured transport enquiry on WhatsApp. It collects the agreed details, summarises open questions and hands over to your team. Exceptions and unclear requirements go to dispatch.
How would this fit your operation?
ROUTE
CARGO
DATES
CONTACT
HANDOVER
TEAM REVIEW
What this should change in daily work
Collect. Prepare. Take over.
Collect
Customers can start a transport enquiry in the evenings and outside office hours.
Prepare
The agreed transport details and open questions are summarised for your team.
Take over
Dispatch assesses feasibility, capacity and price, then responds to the customer.
How we get started together
A clear path to your logistics pilot.
STEP 1
Understand your enquiry workflow
We start with your dispatch team.
Which transport services do customers ask for? What details does your team need for an initial assessment? Together, we choose a clearly defined first use case.
What we agree on
Transport types and required details
Handover process and responsibility
WhatsApp number, data scope and pilot goal
STEP 2
Set up the assistant
We turn your rules into the conversation.
The assistant introduces itself as AI, asks for the agreed transport details and explains the next step. Special requirements are flagged for your team.
Before launch, we test typical enquiries and exceptions.
What we prepare
A conversation based on your dispatch rules
A structured enquiry and open questions
Test cases and clear handover rules
STEP 3
Support the pilot
Your dispatch team checks the process in daily work.
We review completeness, follow-up questions and the work involved in handover. You then decide on improvements and possible integrations.
What we review together
Complete, understandable details
Follow-up questions and dispatch feedback
Improvements and a possible TMS connection
Two stages. Clear expectations.
Start with enquiries. Assess a TMS connection next.
- Enquiry collection: The assistant collects transport details and prepares the handover. Your dispatch team reviews and responds.
- Optional TMS/ERP: Transfer or retrieve data after interfaces, permissions and data fields have been checked.
- Clear boundaries: No automatic price or capacity promise. Exceptions go to your team.
One workflow. Two stages.
Automatic data transfer is agreed only after a technical assessment.
Why epoint
From a WhatsApp conversation to your workflow.
epoint has developed digital solutions since 2000. We bring strategy, design and technical delivery together for businesses in Austria, Germany, Switzerland and Romania.
One team for conversation and handover
A useful assistant needs clear questions and a reliable handover. We design both with your operation and put them into practice.
Your dispatch workflow sets the direction.
Personal support
You have a point of contact throughout the setup. Your dispatch team contributes its experience so the questions and summaries fit daily work.
We document the scope, responsibilities and next steps together.
From a pilot to the right solution
We start with a clearly defined enquiry workflow. That gives us a basis for assessing which changes or interfaces would help your team.
After the pilot, you decide what happens next.
What does dispatch need for its first assessment?
- Which transport enquiries are suitable for a first step?
- What details does dispatch need?
- How does an enquiry reach the right person?
- Which WhatsApp number will be used?
- How will we assess the pilot together?
Daniel Ovidiu Banica
Founder & CEO · epoint
An introduction with clear rules
Your transport rules are the foundation.
An enquiry assistant needs to know which details are required and when dispatch must take over. We agree on those boundaries before launch.
We define suitable transport types, required details, responsibilities and the handover process. The assistant identifies itself as AI. It does not promise price or capacity. Dangerous goods, temperature requirements, unusual dimensions and unclear details are handed over to your team according to your rules.
Data scope, access, retention and required agreements are settled before use. Reading from or writing to a TMS or ERP is added only after interfaces and permissions have been checked.
Start small. Review together. Expand with purpose.
From conversation to dispatch.
No automatic price or capacity promise.
Is this right for your operation?
Useful assistance starts with the right use case.
Especially helpful when …
You handle recurring transport enquiries.
Customers often provide route, cargo or dates only after follow-up questions.
Dispatch wants enquiries together and ready to assess.
Before launch, we clarify …
Who reviews enquiries and checks price and capacity.
Which transport types and exceptions are in scope.
How the number, data, handover and possible interfaces will be set up.
Three rules for good enquiry assistance
Dispatch stays in control.
A good conversation makes things clear: Which route, cargo and dates? What is still missing? Who takes over the assessment?
Collect the required details in the conversation.
Hand open questions over to people.
Let your team assess price and capacity.
Frequently asked questions
What you’ll want to know before starting.
Key answers about WhatsApp enquiry assistance for logistics. We tailor the exact workflow to your operation.
Still have a question?
Does the assistant issue a quote or confirm a transport?
In the first stage, the assistant collects a transport enquiry. It does not produce an automatic price quote or promise available capacity. Dispatch reviews the details, clarifies open questions and agrees the next step with the customer.
Do we need a connection to our TMS or ERP?
No TMS or ERP connection is needed to collect an enquiry and hand it over as agreed. Transferring or retrieving data directly depends on your system, its interfaces and the necessary permissions. We check this before making a commitment.
What data is collected, and how are exceptions handled?
We agree on transport types and required details with you, such as pickup and delivery locations, cargo, quantity, weight, preferred dates and contact details. Dangerous goods, temperature requirements, unusual dimensions and unclear details are handed to dispatch according to your rules. We clarify use of an existing WhatsApp number, data access and retention before launch.
How do we get started, and what does the pilot cost?
After a discussion about your enquiry workflow, handover and technical requirements, you receive a proposal covering pilot scope and costs. Pricing depends on factors such as the conversation flow, message volume and requested integrations. Setup and ongoing costs are agreed before launch.
Start with a concrete use case
Another way for transport enquiries to reach you.
The workflow matters
Phone calls, email and personal coordination remain part of your business. WhatsApp adds a guided enquiry that customers can start outside office hours. What matters is that the details then reach the right person.
Does it help dispatch?
We agree on the assessment criteria together before the pilot.
That is why we plan the introduction with dispatch. Which transport types are suitable? Which fields are needed for the initial assessment? Which cases should go straight to the team? These decisions create a clear workflow with defined responsibilities.
Use the pilot to learn what helps
Before the pilot, we agree on how you want to assess its value: for example, complete enquiries, fewer follow-up questions or the work involved in handover. We do not promise a fixed time saving. Your team’s feedback determines the next steps.
Let’s discuss a logistics pilot for your team.
We’ll clarify your enquiry workflow, the handover to dispatch and the technical requirements.
You’ll then receive a proposal covering scope and costs.
Daniel Ovidiu Banica
Founder & CEO · epoint

