Inquiry entry
Before
The inquiry in a customer's email is retyped into the form, line by line.
With Copilot
Paste the sentence; route, equipment, weight, incoterm and dangerous-goods details arrive as a suggestion card.
LojiMind turns a customer's sentence into an inquiry, a carrier email into file updates and a scanned bill of lading into data. It explains exceptions before you ask and proposes the next steps. The AI suggests, the code verifies, you always decide.
Built on 30+ years of software and business analysis experience
A traditional TMS stores what happened; the operator carries the work itself. As volume grows, it is the headcount that grows, not the software. In an AI-native TMS, copilots and agents run the routine.
| Topic | Traditional TMS | AI-Native TMS |
|---|---|---|
| Data entry | Traditional TMSThe operator fills in the form by hand. | AI-Native TMSThe customer's sentence, the supplier's rate sheet and the bill of lading become records with your approval. |
| Process | Traditional TMSHard-coded; every change is a software project. | AI-Native TMSThe process definition is data; your company's definition is created from a ready template. |
| Exceptions | Traditional TMSKnown only if someone notices. | AI-Native TMSThe rule engine and the agent catch them; an overdue record escalates to the next level. |
| Audit | Traditional TMSA manager checks a sample. | AI-Native TMSESA runs the check you wrote on every file, the moment it enters the step. |
| Estimates | Traditional TMSBased on experience. | AI-Native TMSHorizon calculates the expected finish of every step and opens an exception on deviation. |
| Reporting | Traditional TMSRequested from IT, waits in a queue. | AI-Native TMSA dashboard is described in one sentence; lists and widgets are built from it. |
| Routine work | Traditional TMSDone by whoever remembers. | AI-Native TMSA playbook runs on a schedule or on an event. |
Volume is rising, margins are shrinking and customers expect an instant answer. A logistics company that moves to an AI-native setup handles more work with the same team, faster and with fewer errors.
Copilots take over data entry and follow-up; the team returns to its real work.
Inquiries, quotes and documents move without waiting in a queue.
Less manual copying; code verifies the model's output and an agent checks the steps.
Delays and exceptions are visible before the customer calls.
Four jobs your operations team repeats every day, and how the Copilot takes them over.
Before
The inquiry in a customer's email is retyped into the form, line by line.
With Copilot
Paste the sentence; route, equipment, weight, incoterm and dangerous-goods details arrive as a suggestion card.
Before
ETA, vessel and cut-off changes from the carrier are keyed into the file by hand.
With Copilot
Paste the email; every changed field is proposed as old → new and applied in one click.
Before
B/L number, vessel, voyage and on-board date are read off a scanned B/L one by one.
With Copilot
Upload the document; the AI reads the fields, writes them to the file and logs every step in the audit trail.
Before
A cut-off missed at midnight is only noticed the next morning.
With Copilot
The moment the exception opens, the AI reads the file; its “what happened, why it matters, what to do” note is ready at 00:25.
Nine AI capabilities take over your team's repetitive work, from inquiry entry to exception handling. None of them writes a record without your approval.
Turns a customer's sentence into a validated inquiry. When a port is ambiguous it asks instead of guessing: “Izmir — Alsancak or Aliaga?”
Extracts ETA, vessel/voyage, cut-off and free-time updates from carrier and agent emails. Answers “Am I at risk of demurrage?” with figures computed from the file.
Reads bills of lading (HBL/MBL) field by field, even when scanned. PDF, Word, Excel and email files become suggestions too.
The moment an exception opens, the assistant reads the file and writes its own “What happened / Why it matters / Next steps” note. Unowned exceptions escalate automatically.
If a departure confirmation is missing, the AI drafts the request to the carrier, a supervisor approves it, and the flow keeps watching for days until it closes itself.
Say “two forty HC” and it writes 2x40HC. The help assistant (F1) knows which screen you're on and answers with citations from the user guide.
Reads the rate table in an agent's or carrier's email and asks about columns or values it cannot match, learning the answer. After your approval it writes to the buy tariff and applies the delta against the previous sheet.
Runs the check you wrote in plain language on a process step against the file's data; if something is wrong it opens an exception and assigns a task to the right person. It never edits the file.
Writes each step's estimated completion from a rule such as “median duration over the last 90 days”, and opens a deviation exception in the Control Tower when the step overruns.
Road, air, sea and intermodal operations share one AI architecture: the inquiry Copilot, document reading, the Control Tower and approved workflows each speak that mode's language.
An AI-powered road freight TMS that manages FTL and LTL shipments from inquiry to delivery, reads CMRs and explains delays the moment they happen.
An AI-powered air freight TMS that calculates chargeable weight automatically, reads air waybills and explains flight disruptions as they happen.
A TMS that runs sea freight end to end with an AI Copilot, from FCL and LCL inquiries and multi-option quotes to bookings and bills of lading.
An AI-powered intermodal TMS that combines sea, rail and road legs in one file, reads each leg's documents and explains delays at transfer points.
LojiMind keeps the whole operation in one chain: inquiry, quote, load, operations and invoice are linked together.
Requests arrive by email, the customer portal, the Partner API or a phone note.
Copilot: Fills the form from a sentence and asks about gaps.
Tariffs and carrier rates are compared; a multi-option quote goes out by PDF, email or WhatsApp.
Copilot: Just say “search rates”; supplier rate sheets are also read from email into the buy tariff.
An accepted quote becomes a load file; the booking and position open and the process engine ticks off the steps.
Copilot: Reads carrier confirmations and bills of lading and proposes them for the file.
Cut-offs, departure, arrival and delivery are tracked; exceptions collect in the Control Tower.
Copilot: Explains exceptions before you ask, checks steps against your rules and flags delays early.
Costs, profitability and the invoice come from the same file; every record traces back to its inquiry.
Copilot: Ask “What's my margin on this file?” and get an answer computed from the file.
AI only adds value to your operation if you can trust it. In LojiMind every suggestion is visible, reversible and auditable.
The Copilot fills in the form but never saves. Every change shows old → new; the record is created by your Save, and Undo is always there.
Model output is re-checked in code: an invented port fails the catalogue check, and date maths is done by code, not the model.
Customer names and identities are never sent to the language model; uploaded files are converted to text inside the platform.
Gemini, Groq or Ollama on your own server: you pick the model per screen. With a local model, data never leaves.
Every customer's data lives on its own physical database server and in its own document archive; API keys are stored encrypted.
Every applied suggestion is logged under the user's name. The AI Usage screen shows tokens and estimated cost per copilot, model and user.
LojiMind is built on an AI-native architecture: the copilots run on an event-driven backbone and a knowledge graph, built from proven open technologies.
Separate microservices for inquiries, sea, air, road, finance and pricing, on a scalable backend with virtual threads.
The inquiry → quote → load → position → container → invoice chain is stored as a graph. “Which inquiry did this invoice come from?” is a single traversal.
Each Copilot turn is a small graph: the model extracts, the code validates. Long-running AI flows can pause for human approval and resume days later.
Google Gemini, Groq or fully local Ollama; each Copilot screen gets its own model, and prompts can be tailored per company.
Event-driven backbone: Copilot replies stream live, services work without blocking each other, and model settings change without a restart.
Import/export and FCL/LCL processes run from JSON definitions; steps are completed by the system, a human approval or the AI; ESA checks the steps and Horizon estimates when they finish.
Let's try the Copilot together on your own inquiry emails and documents.
[email protected]
+90 544 961 65 61
Phone
Chat on WhatsApp
+90 544 961 65 61
Elite Park Plaza, Atatürk, Alemdağ Cd No:140-144 Floor 5, 34764 Ümraniye/Istanbul, Türkiye
Address