Solutions · Sectors · Logistics
The delivery that did not happen is the one nobody can explain at 5pm.
In a carrier or a distribution centre, the day runs fine until the first incident — and then the information disappears between the driver, dispatch, customer service and the customer who calls. Skyller brings a ready-made deliveries board, with stages, owners and due dates, and publishes the procedure that says what to do when things go wrong. It does not track the cargo: what the board shows is what your team recorded.
- A ready-made deliveries board
- Evidence before moving on
- Logistics profiles
- Status recorded by the team
Who works here
From dispatch to customer service.
Deliveries, incidents and procedures available to the people coordinating operations and answering customers.
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 each delivery as a card at a stage, with route, driver, estimate and priority as fields.
Answers from the record
How it works today
Promises to call back because the information is missing, then calls dispatch again to find out what happened.
With Skyller
Asks in the chat what is open for a customer or a route and gets the list, with stage and owner.
Procedures at hand
How it works today
Rewrites the same incident procedure for every new hire and becomes the spoken source of the rule.
With Skyller
Publishes the procedure once, with second-person review, and it starts answering.
Deadlines in view
How it works today
Tracks maintenance, vehicle paperwork and licence expiry across scattered reminders.
With Skyller
Every document carries an expiry date and leaves the answer once it passes; the renewal becomes a card with an owner and a due date.
The operation's routine
From the order to the incident, with the limit written down.
See what Skyller does, what needs configuration and what stays with your team.
Select a routine to see the details.
Skyller does it
Following the day
The deliveries board template comes ready: Order, Pickup, In transit, Out for delivery, Delivered and Incident, with customer, route, driver, delivery estimate, freight cost and cargo priority as fields.
The incident that needs a reason
You make the field mandatory at the incident stage and the card will 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 board by stage, by owner and by overdue date and returns the list of what is stuck, respecting the visibility configured. It counts cards; it does not add up freight or calculate indicators.
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 second-person review and are published.
A due date that warns on its own
The reminder goes out 24 hours before the due date and on the day itself, once in each case, to whoever is on the card. If the due date changes or the card leaves the final stage, the reminder applies again.
Vehicle, driver and cargo paperwork
Licences, inspection reports, insurance policies and permits carry effective and expiry dates. Once the expiry passes, the document stops answering and leaves the assistant's inventory, and the renewal becomes a card with an owner and a due date.
New people in dispatch
From the published procedure itself comes an assessment of 3 to 20 questions, assigned to people and teams with a deadline. The Driver Recruitment Policy is also in the template library.
Depends on configuration
The check that has to repeat
Fleet checks, paperwork reviews and month-end routines can be 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. Your operation's TMS, WMS or routing system may not be among them — and that does not close the door: any system that exposes a bridge comes in through its address, with a secure connection required and function-by-function clearance, built by the system's vendor, by your IT or by a partner — or by Skyller as a separate service.
Stays with the team
Tracking, routing and transport documents
Vehicle position, live tracking, route planning, freight calculation and issuing transport documents stay in your system, with your team. Skyller does not talk to the carrier or to the tracking device.
Some routines require connecting a system or adjusting your company settings.
Live proof
Thursday, 16:20. A failed delivery and a customer on the phone.
A delivery operation is not tested on the day the procedure is written: it is tested on the Thursday when the driver could not deliver, the customer called before any internal notice and nobody can say what has already been done.
Starting point
A delivery on the Southern route came back undelivered: nobody was at the address to receive it. The driver messaged the checker, who told the coordinator. Customer service knows nothing, and the customer has just called to ask.
What happens
- The operation had already built the deliveries board from the ready-made template — Order, Pickup, In transit, Out for delivery, Delivered and Incident — with customer, route, driver, estimate and cargo priority as fields, and the reason marked as mandatory at the Incident stage.
- The checker moves the card to Incident. Skyller opens what is missing: without the reason filled in, the card does not advance. He writes «recipient absent», sets the re-delivery for tomorrow, and the card keeps an owner and a due date.
- Customer service asks in the chat what is open on the Southern route. Skyller returns the cards by stage and owner, with the overdue ones first. Before calling back, the agent checks the published procedure for what the company promises when nobody is there to receive — and the answer arrives with the document alongside.
Result
What happened to that delivery sits on a card, with a reason, an owner and a due date, rather than across three conversations. The customer hears what the company actually committed to, because the procedure is published. Vehicle position and transport paperwork stay in the usual system.
What this scene does not promise
- Skyller does not track. There is no integration with telemetry, tracking devices, vehicle position or carrier status: the card shows what your team recorded.
- It does not plan routes, does not calculate freight, does not issue transport documents and does not contact the customer on its own. None of that exists in the product.
- Your TMS, WMS or routing system may have no ready-made connector in the catalogue. Beyond it, the route is the system's own bridge address — built by the vendor, by your IT or by a partner, or by Skyller separately.
- Moving the card is an action taken by a person, with their own permissions. The confirmation Skyller asks for before acting appears in other actions, such as creating a board, removing a stage or archiving one.
Scene with a fictional carrier, route and customer; the ready-made deliveries board, the mandatory field at the stage, the due-date reminder, the board query and the published procedure are the product's own.
What holds the routine together
Nine pieces the operation uses from the order to the incident.
Select a feature to see how it works.
A deliveries board that comes ready
Among Skyller's board templates there is one for deliveries: Order, Pickup, In transit, Out for delivery, Delivered and Incident, with customer, route, driver, delivery estimate, freight cost and cargo priority — normal, express or urgent — already configured. You start from it and adjust whatever belongs to your operation.
A mandatory field that holds the card at the stage
You choose which fields are mandatory at each stage, from fifteen field types. On the move, Skyller opens what is missing and only then advances; cancelling leaves the card where it was. That is how 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 due date itself, 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 — a card warned once does not go silent forever.
The question that sweeps the board
«What is overdue?», «what is open on the Southern route?», «what is with João?» — Skyller reads the board by stage, by owner and by overdue date and returns the list, respecting the visibility configured. It counts cards; it does not add up amounts or build indicators.
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 are already in the library. Skyller fills in company, owner and date; anything missing stays in the text as a field for you 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 stops answering and leaves the assistant's inventory — the same criterion in both places, so the assistant never cites what retrieval will refuse.
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 platform library. On the agents screen you filter by Segment and see the profiles for your sector. They talk about the routine; they do not query your system.
Recurrence for what happens every time
Fleet checks, paperwork reviews and month-end close can be 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 — the queue stops growing on its own.
Where Skyller stops
It does not track cargo, does not receive vehicle position, does not plan routes, does not quote or calculate freight and does not issue transport documents — none of that exists in the product. Connecting is a separate matter: a TMS, WMS or routing system that is not in the catalogue comes in through its own bridge address, function by function.
How this enters the operation
Start with one route, not with the whole operation.
The first week needs no project. Pick one route, build the board from the ready-made template and publish the procedure the team asks for most often by phone.
Operation
Creates the operation's hub and the workspaces that make sense: one for procedures and another for fleet and driver paperwork.
Owner, editor and reader roles per person or per team. A private workspace answers only to the people inside it; a public hub is read by the whole company.
Operation
Opens a board from the deliveries template and adjusts stages and fields, making the reason mandatory at the incident stage.
Fifteen field types available; the mandatory field at a stage is what stops the card from advancing without the evidence.
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.
Whoever wrote the text does not review it when the document type requires review. Only the published version enters the answers.
Dispatch
Starts moving the cards on the chosen route and recording the incident on the card, rather than in a conversation.
The person moves the card with their own permissions; the due-date reminder goes to whoever is on the card.
Customer service
Asks in the chat what is open by route or by customer before returning the call.
Skyller returns the cards visible to whoever asked, by stage, owner and overdue date.
Comes ready
- A deliveries board template with six stages and six fields, including driver, delivery estimate and cargo priority
- Mandatory fields per stage, reminders 24 hours before the due date and on the day, and three board views
- Procedure templates in Portuguese for delivery incidents, shipping, returns, emergencies and driver recruitment
- Sector profiles to install: Supply Chain Analyst, Routing and Deliveries Analyst, Fleet Manager and Transport Compliance Analyst
- Effective and expiry dates on every document, with automatic removal from the answers once the expiry passes
Your company decides
- Which stages and fields the board has, and which fields are mandatory at each stage
- Which workspaces exist, who joins each one and with which role
- Which document types require review and approval before publishing
- Whether the spreadsheet or the internal system come in as connections, and which functions stay cleared
Questions from the people running the operation
The doubts that come up before the first route goes into Skyller.
Start with one route
Open the deliveries board. Record the first incident where it belongs.
Create the account, open a board from the deliveries template, publish the incident procedure and ask dispatch to record one week of a route there. By the end of it, customer service can answer without calling anyone — which is the only proof that matters here.