Hermes in a light cloak holding a parcel and tablet in a modern dispatch space

A solution for logistics and delivery

JediDesk for logistics and delivery

From “how much does delivery cost?” to an enquiry ready for your team.

Try for freeExplore the scenarios

Enquiry · shipment details · operator

The same delivery questions take up your team's time. JediDesk explains your terms, clarifies the route and cargo details, and passes a prepared enquiry to an operator. The customer gets a clear next step, while your team moves on to pricing and arranging transport with the context they need.

Hermes + digital communication. An artistic AI concept, not a photograph of a carrier customer.

For delivery services, carriers and freight forwardersUpdated

Communication in logistics

While your operator gathers details, other customers wait.

“How much does it cost?”, “When will it arrive?”, “Can I change the day?” Each short question involves a different task. JediDesk helps explain known terms and gather the details needed for a conversation with an operator.

One route, different enquiries

The sender asks about cargo acceptance; the recipient asks about receipt. The assistant clarifies the enquiry before directing it to your team.

Pricing needs details

Cities, contents, number of packages, weight and dimensions help an operator assess the enquiry. Incomplete enquiries lead to more follow-up questions.

Status needs a reliable source

“Where is my shipment?” requires current data. General delivery terms do not confirm the progress of a particular parcel.

Changes need approval

A request to reschedule delivery or change an address still needs checking. Customers need to know when a change has actually been confirmed.

Before automation

Repeated questions take up your team's attention

Your operator starts with the same questions

Without a route and cargo description, transport cannot be discussed in detail. The initial questions recur in every conversation.

General terms are taken as a promise

Standard delivery times and rates in company materials may need clarification for a particular cargo and service.

A problem report has no assigned recipient

A delay, damage or question about receipt needs a responsible employee and a retained enquiry history.

A change request is confused with a completed action

A simple “received” can make someone think delivery has already been rescheduled. The status of the arrangement needs to be clear.

Automation use cases

Five situations where AI helps your team

Let the assistant handle routine explanations and gather details. Your operator receives context for pricing, arranging delivery or resolving a problem; data for specific shipments requires a separate connection.

01

Explain your company's terms

“Do you deliver to my city, and how should I prepare the cargo?”

AI uses your materials on coverage, services, packaging and the enquiry process. It passes unusual cargo or questions not covered in the knowledge base to an operator.

Knowledge base answers

The customer understands which terms apply to their enquiry.

02

Prepare a pricing enquiry

Several boxes need transporting, but the message only gives the cities.

Following your scenario, the assistant asks the customer for contents, number of packages, weight and dimensions. It passes the details to an operator to check feasibility, cost and transport terms.

Enquiries with context

Your team receives a prepared enquiry, and the customer knows pricing is still being agreed.

03

Route a status question

“What is happening with my shipment?”

After customer verification under your company's rules, AI can use a current connected source. If data is missing, outdated or ambiguous, it clarifies the enquiry and involves an operator.

Data sources and integrations

The answer is based on data; your team checks an unknown status.

04

Collect a delivery change request

The recipient wants a different delivery day or address.

The assistant records the request and passes it to the responsible person. An operator verifies the customer, checks whether the change is possible and confirms the result. A chat message alone does not change the cargo's route.

Operator handover scenario

The customer can distinguish a submitted request from an approved change.

05

Pass a problem on with context

A customer reports a delay or damage.

AI asks for the agreed identifier and a description, explains the enquiry process using your materials, and passes the conversation to the responsible team. A specialist checks causes and solutions.

AI and an operator in one conversation

The problem has a description and a review route, without an invented cause or promised compensation.

How the solution works

Enquiry → cargo details → prepared request → agreement

Four steps to preparing an enquiry. The information collected supports the conversation; an operator confirms cargo acceptance and transport terms.

  1. 01

    The customer writes

    Asks about delivery or describes what needs transporting and where.

  2. 02

    AI gathers details

    Collects the route and required cargo details from the customer.

  3. 03

    Prepares the enquiry

    Explains known terms and passes the collected context to an operator.

  4. 04

    The operator agrees the arrangements

    Checks feasibility, cost and timing, and confirms the next action.

Company materialsCustomer-provided detailsHandover rulesResponsible operator

Capability map

What the assistant handles in logistics

Each answer needs company materials, customer details or a responsible person. The map shows how to organise communication around a shipment.

The customer writes in a connected chat or messenger

Hermes with a parcel and blue chat symbol — an artistic metaphor for a logistics assistant
JediDesk AIA link between the customer and delivery team

  • Services and terms

    Explains coverage and the enquiry process.

    Source: Current company materials

  • Cargo details

    Asks for the route, contents and required dimensions.

    Source: Customer answers in the conversation

  • Pricing enquiry

    Prepares details for agreeing the rate and timing.

    Source: Rules + operator confirmation

  • Status questions

    Finds data or passes the question to your team.

    Source: Connected source after verification

  • Change requests

    Records a request for another day or address.

    Source: Customer + team approval

  • Operator handover

    Retains the history and description of a complex enquiry.

    Source: Conversation + handover rules

The customer understands the next step; the operator has context and agrees what delivery arrangements are actually possible.

Illustrative diagram. Shipment statuses and actions depend on a defined source and configured connection.

Channels and integrations

Customers use their preferred channel. Your team sees what matters.

Start with company materials and operator handover. Access to shipments and actions in your system are defined separately.

Website chat

An enquiry alongside route, service and transport term descriptions.

About the channel

Telegram

An enquiry through your company's connected bot.

About the channel

Instagram

Questions following posts about services and delivery destinations.

About the channel

Company knowledge base

Coverage, services, terms, contacts and the enquiry process. Assign someone to update the materials so answers reflect your current rules.

How to connect

CRM or logistics system

Recording enquiries, reading status and permitted changes are agreed for your system and its API. The required connection is checked before a particular scenario launches.

How to connect
Hermes with a tablet beside a modern dispatch centre — an artistic scene of handing an enquiry to the team
From messenger to operator. An artistic AI scene, not a photograph of a logistics customer company.

Example conversations

Your operator picks up the conversation with the details they need

Illustrative dialogues show the proposed workflow. These are hypothetical situations, not customer conversations or a case study of a particular carrier.

  1. 01Purpose of the enquiry
  2. 02Shipment details
  3. 03Arrangements agreed with an operator

Prepare a transport enquiry

Company website chat
  1. Customer

    I need to send two boxes from Kyiv to Lviv. How much will it cost?

  2. JediDesk AI

    Please tell me what is inside and the weight and dimensions of each box. I'll pass the details to an operator for pricing.

  3. Customer

    Clothes, each about 5 kg, 40 × 30 × 30 cm. I'd like to send them on Thursday.

  4. JediDesk AI

    I'm passing on your enquiry: Kyiv → Lviv, two boxes of clothes, the weight and dimensions you provided, preferred day — Thursday. An operator will check the terms and pricing. The shipment has not been booked yet.

Details are as reported by the customer. Your team agrees acceptance, rate and date.

The operator starts with a specific enquiry, without having to gather every detail again.

Request a different delivery day

Connected messenger
  1. Customer

    I'd like to receive the parcel the following day. Can delivery be rescheduled?

  2. JediDesk AI

    Please provide the agreed enquiry reference and your preferred day. I'll pass your request to an operator to check whether the change is possible.

  3. Customer

    Enquiry L-123; I'd like to receive it on Friday.

  4. JediDesk AI

    I'm passing on the request for L-123: preferred delivery on Friday. An operator will check the enquiry and agree possible actions. Rescheduling has not been confirmed yet.

L-123 is a fictional reference for this example. An operator verifies the customer and confirms the change.

The request is recorded; the AI message is not presented as completed rerouting or a schedule change.

Results and benefits

A prepared enquiry makes the customer conversation more focused

The route, cargo and preferences are collected in one enquiry. Your operator can move on to checking and arranging transport. During the trial, assess which repeated questions your team no longer asks manually.

Free up time spent on repeated explanations

The assistant takes delivery terms and enquiry procedures from your materials. Your team joins where a decision is needed.

Start pricing with context

The customer's route, contents, weight and dimensions stay in one enquiry. Your operator sees what is known and what needs clarification.

Help customers understand the arrangement

The person sees what has been submitted for checking and who will confirm the terms. This makes agreeing the next step easier.

Continue difficult conversations with their history

Your operator receives the problem description and previous clarifications. The customer does not have to explain everything from scratch.

Built around your process

Start with your rules and a familiar channel

Your company's knowledge

The assistant uses prepared rules and service descriptions. You define answer boundaries and when to hand over to a person.

AI assistant capabilities

Context shared by AI and your operator

Your team continues the conversation with its retained history. Customers can explain the situation and agree the next action more easily.

Chat for AI and your team

Connections for a specific task

Guidance can be supplemented with data from your system after checking the source, access and required actions.

Integrations and data

Launching the solution

Launch one scenario and test it in practice

Choose one enquiry route and test it with an operator. Launch timing depends on the readiness of your materials and required connections.

  1. 1

    Prepare your materials

    Collect services, coverage, acceptance terms, pricing rules and contacts. Decide who keeps them up to date.

  2. 2

    Choose the details to collect

    Agree enquiry fields: route, cargo, packages, weight, dimensions, preferred time and contact method. Collect only the data the scenario needs.

  3. 3

    Assign responsibilities

    Separate new enquiries, shipment questions and problems. Define the process for customer verification and action confirmation.

  4. 4

    Run trial dialogues

    Test an incomplete enquiry, unknown status, unusual cargo and delivery change request. Assess whether an operator joins at the right time.

AI setup guide

Before you start

Frequently asked questions

About enquiries, rates, statuses and agreeing actions with an operator.

Does AI book shipments independently?

In the basic scenario on this page, the assistant collects details and passes the enquiry to an operator. A collected enquiry does not mean a booked shipment, confirmed pickup or dispatched courier. Automatic execution requires a separately configured connection, a permitted action in your system and confirmation that it succeeded. Your team should define these conditions before launch and explain the enquiry's stage to the customer.

Which cargo details can be collected?

The list depends on your company's services and rules. An initial enquiry can collect origin and destination cities, contents, number of packages, weight, dimensions and preferred time. These are customer-reported details, not verified measurements. Agree the questions with an operator and keep only those needed: complex cargo or incomplete details require further clarification before transport is agreed.

Will the bot give an exact price and delivery date?

AI can explain current pricing rules and standard times from your materials. Pricing a particular cargo requires enough details and a confirmed source: an operator or a separately connected system. A preliminary estimate, preferred day and agreed date must be clearly distinguished. If data is unavailable, the assistant passes the enquiry to your team without inventing a price, arrival forecast or fulfilment guarantee.

Where does the assistant get shipment status?

A defined, current source and a configured data retrieval method are needed. Answers about a particular shipment are provided after customer verification under company rules; the reference alone is not universal permission to disclose data. If there is no connection, information is outdated or the record is missing, the assistant clarifies the enquiry and passes it to an operator. It does not invent the cargo's location, a delay reason or delivery time.

Can a customer change delivery through chat?

In the proposed scenario, the customer states their preference and AI passes it to the responsible person. An operator verifies the customer, checks whether the change is possible and reports the result. Automatic rerouting or rescheduling requires a separately agreed integration and successful execution of a permitted action. Until then, the enquiry remains a request. Similarly, a damage report does not mean compensation has automatically been approved.

Must the logistics system be connected straight away?

For answers based on company materials and operator handover, you can start with a knowledge base and connected channel. For statuses, enquiries created in an external system or delivery actions, its API, permissions and required scenario need separate checks. General integration support does not mean ready-made access to any TMS, WMS or every carrier. Capabilities are defined for your process.

Other industries

Find your next use case

Next step: your company

Test JediDesk with your delivery enquiries

Choose a frequent question or pricing enquiry. Add your terms, configure operator handover and check whether your team receives the details they need. Try this scenario during the free trial.

Try for freeSign up

The free trial lasts 14 days. Answers, handover and integrations are configured for your process.

  • Your real questions
  • Enquiries with context
  • A clear next step
Top