Solutions · Sectors · Logistics
The delivery that did not happen is the one nobody can explain at 5pm.
For a carrier or a distribution centre, Skyller brings a ready-made deliveries Kanban, with stage, owner and due date, and publishes the procedure that says what to do when it goes wrong. Whoever serves the customer asks in the chat what is open and gets the list, with the procedure alongside.
- A ready-made deliveries Kanban
- Evidence before moving on
- Logistics profiles
- Status recorded by the team
Deliveries · South route
Issue1
Aurora delivery
HighIssue reason
DocsRedelivery scheduled0
Demonstration · illustrative data
Who works here
From dispatch to customer service.
Visible open tasks
How it works today
Runs the day from a spreadsheet updated at night and finds out about the incident when the customer calls.
With Skyller
Sees every delivery as a card at a stage, with route, driver, estimate and priority as fields.
Answers from the record
How it works today
Promises a call back for lack of information and phones dispatch to find out what happened.
With Skyller
Asks in the chat what is open by customer or by route and gets the list, with stage and owner.
Procedures at hand
How it works today
Rewrites the same incident procedure for every new person and becomes the rule's oral source.
With Skyller
Publishes the procedure once, with a second person's review, and it starts answering.
Deadlines in view
How it works today
Tracks maintenance, vehicle paperwork and licence expiry in scattered reminders.
With Skyller
Every document comes in with an expiry date and leaves the answers when it lapses; the renewal becomes a card with an owner and a due date, and vehicle maintenance runs on the maintenance Kanban, with the next preventive date worked out from each vehicle's interval.
The operation's routine
Where Skyller comes in — and what stays with the team.
Select a routine to see the details.
Skyller does it
Following the day
The deliveries Kanban comes ready: Order, Pickup, In transit, Out for delivery, Delivered and Incident, plus Returned and Cancelled, with the recipient from the customer registry, the carrier from the supplier registry, invoice, tracking code, delivery estimate and proof of delivery. The recipient gets an e-mail at dispatch, when it goes out for delivery and on delivery, and the due-date reminder goes out 24 hours before and on the day to whoever is on the card.
The incident that needs a reason
With the reason mandatory at the incident stage, the card does not advance without it: Skyller opens what is missing and only then moves it; cancelling leaves the card where it was.
«What is open on the Southern route?»
Skyller reads the Kanban by stage, owner and overdue date and returns what is stuck, respecting the configured visibility. It counts cards; adding up freight and building metrics stay with the spreadsheet or the system.
The procedure for when it goes wrong
How to Resolve a Delivery Problem, the Shipping and Logistics Process, the Returns and Exchanges Process and the Emergency Response Procedure start from ready-made templates in Portuguese, go through review and are published; the published procedure also produces the assessment for whoever joins dispatch.
Vehicle, driver and cargo paperwork
Driving licences, inspection reports, insurance policies and permits carry effective and expiry dates; once expired, the document stops answering, and the renewal becomes a card with an owner and a due date.
Depends on configuration
The check that has to repeat
Fleet checks, paperwork reviews and month-end routines are created by recurrence, with frequency, time zone, entry stage and a due date in days; with five open occurrences of the same card, the next one is not created.
The system that already runs the operation
The catalogue carries ready-made label, shipping and spreadsheet connections. A TMS, WMS or routing system outside the catalogue comes in through the address of a bridge, with a secure connection and function-by-function enabling, built by the vendor, your IT, a partner or Skyller as a separate service.
Stays with the team
Tracking, routing and transport documents
Vehicle position, tracking, route planning, freight calculation and issuing transport documents stay in your system, with your team.
Live proof
Thursday, 16:20. A failed delivery and a customer on the phone.
Starting point
A delivery on the Southern route came back undelivered: nobody was at the address. The driver messaged the checker, who told the coordinator; customer service knows nothing, and the customer has just called.
What happens
- The operation had already built the Kanban from the deliveries template, with the reason marked as mandatory at the Incident stage.
- The checker moves the card to Incident, and Skyller opens what is missing. He writes «recipient absent», sets the re-delivery for tomorrow, and the card has an owner and a due date.
- Customer service asks in the chat what is open on the Southern route and gets the cards by stage and owner, overdue first. Before calling back, the agent checks in the published procedure what the company promises when nobody is home, with the document alongside.
Result
What happened to the delivery is on a card, with reason, owner and due date, and the customer hears what the company agreed to do.
Good to know
- Tracking, telemetry, vehicle position and carrier status stay in the tracker and your system; the card shows what your team recorded.
- Route planning, freight calculation and issuing transport documents stay in your system, and calling the customer back is customer service's job.
Fictional carrier, route and customer; real product features.
Delivery issues · South routeWhat is still open on the South route?
Delivery Procedure
Record the issue reason, owner and redelivery deadline on the operation’s card.
Skyller is an AI and can make mistakes. Remember to check.
Demonstration · illustrative data
Features
What supports the operation's routine.
Select a feature to see how it works.
A deliveries Kanban that comes ready
Among the Kanban templates there is one for deliveries: Order, Pickup, In transit, Out for delivery, Delivered and Incident, with recipient and carrier linked to the registries, route, driver, delivery estimate, freight cost and cargo priority (normal, express or urgent) already set up. On an incident, the AI classifies what happened and drafts the claim to the carrier and the message to the customer, and the Kanban works out the 10-day deadline to report damage that could not be seen on delivery. You start from it and adjust whatever is specific to your operation. The same Kanban has six views, among them Kanban board, Table and Calendar.
A mandatory field that holds the card at the stage
You choose which fields are mandatory at each stage, from 23 field types. On the move, Skyller opens what is missing and only then advances, so an incident never lacks its reason and a delivery never lacks its proof.
A due-date reminder for whoever is on the card
The reminder goes out 24 hours before the due date and on the day, once in each case, to the people on the card. If the due date changes or the card comes back from the final stage, the reminder applies again.
The question that sweeps the Kanban
«What is overdue?», «what is open on the Southern route?», «what is with João?»: Skyller reads the Kanban by stage, owner and overdue date and returns the list, respecting the configured visibility.
Templates in Portuguese for the procedure
How to Resolve a Delivery Problem, the Shipping and Logistics Process, the Returns and Exchanges Process, the Emergency Response Procedure, the Driver Recruitment Policy and Creating and Modifying Procedures, on every plan. Skyller fills in company, owner and date; anything missing stays as a field to complete.
An expiry date that pulls the lapsed document out of the answer
Driving licences, inspection reports, insurance policies, permits and contracts carry effective and expiry dates; once the expiry passes, the document leaves the answers.
Sector profiles ready to install
Supply Chain Analyst, Routing and Deliveries Analyst, Fleet Manager, Transport Compliance Analyst and Accountant for Transport and Logistics sit in the agent library, filterable by Segment. They talk about the routine based on what the company published.
Recurrence for what happens every time
Fleet checks, paperwork reviews and month-end close are created by recurrence: frequency, time zone, entry stage and a due date in days. With five open occurrences of the same card, the next one is not created.
How to start
Start with one route, not with the whole operation.
Pick one route, build the Kanban from the ready-made template and publish the procedure the team most often asks for by phone, with no project.
Operation
Creates the operation's hub with one workspace for procedures and another for fleet and driver paperwork, defining who joins each; a private workspace answers only the people inside it, and a public hub is readable by the whole company.
Operation
Opens a Kanban from the deliveries template, adjusts stages and fields and makes the reason mandatory at the incident stage.
Transport analyst
Picks How to Resolve a Delivery Problem from the library, adjusts it to what the company promises customers and sends it for review.
Dispatch
Starts moving the cards on the chosen route, each person with their own permission, and recording the incident on the card rather than in a conversation.
Customer service
Asks in the chat what is open by route or by customer before returning the call.
Operations questions
The doubts before the first route goes into Skyller.
Start with one route
Open the deliveries Kanban. Record the first incident where it belongs.
Create your account, open a Kanban from the deliveries template, publish the incident procedure and ask dispatch to record the route there.