delivery slot booking software in Kenya is bought to stop the arguments at the gate, not to fill a calendar. A customer chooses Tuesday between nine and noon, the depot confirms, and both sides write the same promise in different places.
The promise then meets the road. Two lorries, one blocked access road in Kahawa, and a driver who has not eaten since six in the morning.
A delivery slot booking software in Kenya system earns its fee on the days that promise is hardest to keep, not on the quiet ones.
The Promise a Slot Makes to a Customer
When a customer books a window they are not buying a time. They are buying the right to stop worrying for a few hours.
A shop in Nyeri moves two staff off the floor for a Tuesday delivery. A clinic in Upper Hill clears a store room and locks the door behind it.
Both have shifted real work to be ready, and neither will forgive a lorry that turns up at four in the afternoon.
delivery slot booking software in Kenya turns that arrangement into a record: who booked, which window, which vehicle, which day.
Without the record the promise lives in a WhatsApp thread and dies in a shift handover at seven in the evening.
The confirmation should carry the facts the driver will see: date, window, address landmark, contact number, and what happens if nobody answers the door.
A slot is a small contract. Treat it like one from the first booking.
Most depots learn this after a dispute, when the customer produces a clean screenshot and the depot produces nothing at all.
Ask a customer to describe the last late delivery and they will name the hour, not the day. That memory is what the next booking is measured against, and delivery slot booking software in Kenya has to overwrite it with a kept window.
Capacity Is Counted in Vans, Not Orders
A booking screen that counts orders will oversell every single morning. Capacity belongs to the vehicle, the driver’s legal hours, and the route the depot can physically run.
A three-tonne lorry working Kayole and Umoja can take about eighteen drops before two o’clock. The page should know that number before it offers a window.
delivery slot booking software in Kenya has to hold capacity at the level of the run, not the order. Twelve vans at nine drops each is a hundred and eight promises, not an infinite diary.
The count changes with the load. A palletised delivery to a hardware shop takes twenty-five minutes at the gate and forty inside.
Mix that with six envelope drops in the same estate and the morning is gone before the driver reaches the third street.
Good systems let the dispatcher set a weight, a volume, and a service time per stop type. A parcel is not a mattress.
They also let the depot block a vehicle for a service, a county inspection, or a driver’s day off, and watch the available windows shrink honestly.
delivery slot booking software in Kenya that ignores service times is a calendar with optimistic handwriting. It looks tidy until the first Thursday.
A dispatcher who cannot see how full a van already is will promise the next slot to whoever calls loudest. delivery slot booking software in Kenya should show the load before it shows the calendar.
The Cut-Off Hour That Protects Tomorrow
Same-day cut-offs are where most depots lie to themselves. The page says order by two, while the picking team actually needs the paperwork by eleven.
The gap gets filled by shouting. A supervisor walks the aisles looking for an order that arrived after the pick list closed.
delivery slot booking software in Kenya should publish the real hour, not the marketing one. If the last van leaves at two-thirty, the cut-off is when the last pick can still be loaded, not when the office closes.
Different services deserve different clocks. A document run across Nairobi can accept a booking at one o’clock. A furniture delivery to Kitengela cannot.
The cut-off also has to survive month end, when order volume doubles and every customer believes their request is small.
A hard stop at eleven is kinder than a soft promise at two. Customers plan around a rule they can see.
delivery slot booking software in Kenya can show the next available window the moment a cut-off passes, which removes the argument before it starts.
The dispatcher still needs an override for the account that pays for the privilege. That override should be logged with a name.
The cut-off should be a visible countdown on the page, not a rule discovered at the counter. delivery slot booking software in Kenya that hides it invites the argument it was built to prevent.
Why the Call Centre Still Wins Some Bookings
A regular customer with a difficult address will pick up the phone. The booking page assumes a clean street name, a working landmark, and a number that answers.
Kenyan addresses rarely cooperate. A shop may be known as “opposite the old post office” long after the post office has moved.
delivery slot booking software in Kenya works best when the call centre and the page write to the same diary instead of running parallel ones.
The agent can hear the uncertainty in a voice. She knows that Kangemi means something different on a rainy Friday.
That judgement is valuable and should not be thrown away in the name of self-service.
The sensible arrangement gives repeat customers a login and gives the agent the same screen, with the same capacity, and a note field for the landmark.
Without that, the depot runs two truths and the driver receives both.
delivery slot booking software in Kenya should make the phone channel faster, not obsolete. An agent who can see the whole week books in ninety seconds.
A page that takes four minutes and three failed address searches sends everyone back to the phone anyway.
Agents also need a script for the customer who insists on a window that is already full. Offer two alternatives and let delivery slot booking software in Kenya hold the booking while the caller decides.
Slot Windows Customers Actually Believe
Two-hour windows are believed. Four-hour windows are tolerated. The word “morning” is a rumour that nobody plans around.
The width of the window is a promise about precision, and customers price it accordingly. A two-hour window is worth more than a vague day.
delivery slot booking software in Kenya should let the depot sell the narrow window and charge for it, rather than offer a wide one and apologise.
Narrow windows cost capacity. A van waiting inside a two-hour band cannot also cover a wide one across the same estate.
The honest compromise is a narrow window plus a live position, so the customer can see the lorry two stops away.
A message that says “your driver is at the Total station on Thika Road” is worth more than a countdown timer that resets.
delivery slot booking software in Kenya that only sends “out for delivery” has done half the job. The customer still does not know whether to wait or step out.
Windows also need to match the customer’s day. A restaurant wants stock before eleven. A school wants nothing during assembly.
A window that arrives early is almost as disruptive as one that arrives late. delivery slot booking software in Kenya should respect the start of the band, not just the end.
Rescheduling and the Number That Never Answers
Rescheduling is not a button. It is a negotiation with a customer who has already moved their day once.
The first failure is usually the phone. The number rings out, the line is busy, or the person who booked is in a meeting and the phone belongs to the office.
delivery slot booking software in Kenya should record every attempt with a timestamp, not just the final note that says “no answer”.
Three attempts across two hours is a pattern. One attempt at lunchtime is a guess.
When contact fails the depot needs a rule, not a mood. Hold the parcel, attempt once more tomorrow, and charge a realistic redelivery fee.
The reschedule itself should move the booking into a new capacity slot, not quietly squeeze it beside an existing run.
That squeeze is how a nine-stop morning becomes a fourteen-stop afternoon and every later customer pays for it.
delivery slot booking software in Kenya that allows an unlimited reschedule for free teaches customers to treat the window as a suggestion.
A small, published fee after the second change is not hostile. It is the price of a promise that holds.
Customers respect a rule that is explained once, clearly, at the point of booking.
Record why each reschedule happened, even when the reason is embarrassing. A pattern of Monday failures in one zone is a routing fact, and delivery slot booking software in Kenya should surface it before the customer does.
Peak Days, Blackout Dates and the Fair Share Rule
End month is not a normal day. Neither is the Friday before Christmas, the school opening week, or the last three days of December.
On those days the depot can sell the same capacity five times over and still disappoint people. The question is who gets served.
delivery slot booking software in Kenya should carry a calendar of peak dates that the dispatcher sets in advance, not a scramble invented at eight in the morning.
Blackout dates work better when they are visible. A customer who sees that 24 December is full will book the 22nd and complain less.
The fair share rule matters for contract clients. A supermarket with a standing order should not be able to swallow every slot in the week.
Reserve a percentage for walk-in and small accounts, and publish the reserve internally so the sales team stops promising it away.
delivery slot booking software in Kenya can enforce that reserve automatically, which removes the awkward conversation with a large customer.
Peak pricing is normal in transport and should be normal on the page. A premium window on 31 December is not greed.
What customers resent is a quiet failure. They will accept a higher price far more easily than a van that never comes.
Publish the peak calendar a month ahead and let the sales team quote it. delivery slot booking software in Kenya that only the dispatch desk can see will not stop a promise made on the road.
The Run Sheet a Driver Reads at Six in the Morning
At six in the morning the driver does not want a dashboard. He wants a sheet he can read with one hand while the engine warms up.
The run sheet should list the stops in the order they will be attempted, with the window beside each one and the contact number in a readable size.
delivery slot booking software in Kenya that prints a run sheet by booking time rather than by route is asking the driver to re-plan the day in traffic.
A good sheet groups by estate, respects the first window, and shows the load order so the last parcel is not buried under the first.
The driver also needs to know which stops are cash on delivery, which are already paid, and which need a signature.
Put that on the sheet and the arguments at the gate drop sharply, because the customer is not told one thing and shown another.
delivery slot booking software in Kenya should print a version the depot can hand over at the counter, and a phone view for the driver who prefers a screen.
Both must come from the same record. A reprinted sheet that disagrees with the app is worse than no sheet at all.
The sheet also carries the exception column: gate closed, customer absent, wrong item, refused.
That column is the raw material for tomorrow’s plan, and it is usually left blank because nobody asks for it.
Failed Attempts and the Cost of the Second Visit
A failed drop is not one cost. It is the fuel out, the driver’s hour, the phone calls, the return trip, and the space the parcel takes up in a depot that is already full.
Price it once and the number is uncomfortable. A van trip across Nairobi and back can easily cost KES 1,800 before anyone counts the wages.
delivery slot booking software in Kenya should make that cost visible on the order, so the dispatcher sees the second attempt as money rather than admin.
The commonest failures are predictable: nobody at home, a guard who will not accept a parcel, a gate code that changed, a customer who went to a funeral.
Each has a different fix. The gate code belongs in the address record. The absent customer belongs in a call before dispatch.
The funeral cannot be fixed, but it can be recorded as a reason code that stops the depot blaming the driver.
After three failed attempts the parcel should move to a holding decision: return to sender, hold for collection, or write off.
delivery slot booking software in Kenya with a clear failure workflow turns a repeated loss into a single, expensive lesson.
A sheet that fits on one page is read. One that runs to three pages is folded into a pocket by the second stop, and delivery slot booking software in Kenya should print the summary first and the detail behind it.
Same-Day Work Sits in a Different Queue
Same-day delivery is a different business from scheduled delivery, even when one company runs both.
A boda rider carrying a phone charger across Westlands can leave in ten minutes. A van delivering a fridge to Syokimau needs a window, a helper, and a clear staircase.
delivery slot booking software in Kenya should keep the two queues separate, because mixing them wrecks the scheduled promise.
The same-day queue is measured in minutes and priced per trip. The scheduled queue is measured in windows and priced per drop.
Put a same-day urgent into a scheduled run and the driver decides, at the roadside, whose promise to break.
The dispatcher should be able to see both queues on one screen and still keep the capacity pools apart.
delivery slot booking software in Kenya that blends them will always favour the loudest customer, which is rarely the most profitable one.
Some depots run same-day only before eleven, then close the queue to protect the afternoon schedule.
That is a policy decision, and the software should be able to enforce it with a time rule rather than a verbal warning.
The two queues should share a customer record but never a vehicle slot. delivery slot booking software in Kenya can keep the pools apart while letting the dispatcher see one day’s work in one place.
Holding Capacity for Contract Clients
A contract client does not buy a slot. They buy the certainty of a slot, every weekday, for a year.
That certainty has to be carved out of the diary before the public page opens, or the sales team will sell it twice.
delivery slot booking software in Kenya should support standing bookings that repeat by weekday, with a holiday pause and a review date.
The review matters. A client who once needed five drops a day may now need two, and the reserved capacity should follow the actual volume.
Reserved slots should also have a release rule. If the client has not confirmed by four the previous afternoon, the slot returns to the pool.
That single rule recovers a surprising amount of capacity on quiet weeks without upsetting anyone who plans properly.
delivery slot booking software in Kenya that cannot release unused reservations is really a spreadsheet with better colours.
The dispatcher needs a weekly view of reserved versus used, or the reserve quietly becomes a permanent gift.
Telling the Customer Before They Call
At ten forty the dispatch desk knows the lorry is stuck behind a breakdown at Mlolongo. At one fifteen the customer calls to ask where the delivery is.
Those two and a half hours are the whole difference between a professional operation and a reactive one.
delivery slot booking software in Kenya should trigger a message the moment a window is at risk, not when it has already failed.
The message needs a new time, not an apology. “We are running about ninety minutes late, expect us between two and three” is useful. “Sorry for the inconvenience” is not.
A customer who is told early can reorganise the afternoon. A customer who is told at five o’clock has lost a day and will remember it.
The trigger can be manual, and often should be. A dispatcher who sees the queue at Mlolongo can press one button and warn eleven customers.
delivery slot booking software in Kenya that automates the warning from live position data is better, as long as the estimate is honest.
An automated message that promises three o’clock and delivers at five is worse than silence, because it was believed.
The best depots warn early even when the delay is uncertain. A range is respected. A false certainty is punished.
The warning should reach the person who booked, not just the number on the account. delivery slot booking software in Kenya should send it to a phone that someone answers, or the delay is discovered at the gate.
Deposits, Penalties and the Cancellation Argument
A booking with no commitment is a wish. Customers cancel, and the van that was held for them goes out half empty.
A small deposit changes behaviour, especially on high-value or bulky deliveries where the empty run is expensive.
delivery slot booking software in Kenya should tie the deposit to the slot, refund it on delivery, and show the rule before the customer pays.
Penalties need to be proportionate. Charging a full delivery fee for a cancellation two days early is a good way to lose the account.
Charging nothing for a cancellation at six on the morning of delivery is a good way to lose the van.
The usual middle ground is a free change up to twenty-four hours before the window, then a fee that covers the wasted run.
Publish it in one paragraph on the booking page and repeat it in the confirmation message.
delivery slot booking software in Kenya should apply the rule the same way for the phone customer and the web customer, or the desk will be accused of favouritism.
The finance team also needs the deposit to reconcile against the invoice without a manual hunt through M-PESA messages.
Estates, Gates and the Last Hundred Metres
The last hundred metres decide whether the window was kept. A gated estate in Kileleshwa can add fifteen minutes that nobody planned for.
The guard needs a name, a unit number, and a reason. Without them the lorry waits at the barrier while the driver calls an office that is also waiting.
delivery slot booking software in Kenya should store the gate instructions with the address: barrier code, visiting hours, the side entrance for vans over three tonnes.
Apartment blocks add a second problem. The lift may be reserved for moving, the staircase may be narrow, and the customer may be on the sixth floor with a sofa.
That is a two-person job, and the run sheet should say so before the driver arrives alone.
Estate roads also flood. A route that works in February is a different route in April, and the booking page should not pretend otherwise.
delivery slot booking software in Kenya can attach a note to a zone so every future booking carries the warning about the murram section.
Customers appreciate being asked which gate. It signals that the depot has actually been there before.
The alternative is a driver circling a perimeter wall for twenty minutes while a two-hour window drains away.
Ask the driver to photograph the gate on the first visit and attach it to the address. delivery slot booking software in Kenya can hold that photo beside the booking, so the next driver arrives already knowing the way in.
When the Booking Page and the Order Book Disagree
Two systems that both claim to know the truth will produce one loser: the driver at the gate with the wrong address.
The common cause is a booking page that writes to a marketing tool while the order book lives in the accounting software.
delivery slot booking software in Kenya should write the slot into the same order record that carries the invoice, the items, and the payment status.
Where a full replacement is not possible, a sync with a clear owner and a visible failure alert is the minimum.
Silent sync failures are the worst kind. The page says booked, the order book says nothing, and the parcel never leaves the shelf.
Test the sync on a public holiday, when nobody is watching, and see whether the failure is noticed.
delivery slot booking software in Kenya that cannot survive a two-hour internet outage should at least allow the desk to work offline and reconcile later.
The reconciliation should be automatic where possible, and flagged where not.
A depot that runs a paper backup without a merge rule ends up with duplicate bookings and two vans at the same gate.
The sync should run in both directions, because a change made in the order book must reach the diary before the customer is told a different time.
A tool that pushes one way will drift within a week. delivery slot booking software in Kenya should reconcile both sides nightly.
What the Dispatch Desk Should Review Each Friday
Friday afternoon is the only quiet hour in a delivery week, and it is usually wasted.
Thirty minutes with the week’s numbers prevents most of next week’s arguments.
Start with utilisation by window. If the nine-to-eleven band is always sold out and the two-to-four band never is, the pricing is wrong.
delivery slot booking software in Kenya should report failed attempts by reason, not just a total. Six “gate locked” failures in one estate is an address problem, not a driver problem.
Then look at reschedules. A customer who has moved a delivery four times is costing more than the margin on the order.
Check the overrides too. Every manual slot pushed past capacity is a promise someone else will break.
delivery slot booking software in Kenya can rank overrides by dispatcher and by customer, which usually reveals one account causing most of the damage.
Finish with the second-attempt cost. It is the number that turns a polite discussion about service into a decision about fees.
The review should end with one change for Monday, written down, with a name beside it.
Training Staff to Refuse a Slot
The hardest skill at a dispatch desk is saying no to a customer who is being pleasant and persistent.
Staff default to yes because a refusal feels like a lost sale, and the cost of the broken promise lands on someone else, later.
delivery slot booking software in Kenya helps only if the desk is trained to trust the capacity number on the screen.
That means a written rule: when the band is full, offer the next band, the next day, or the collection option. Never oversell.
Role-play the conversation once a month. “I can do Thursday morning or Friday between two and four, which suits you better?” is a refusal that still sells.
The desk also needs permission to escalate. A large account demanding an exception should reach a supervisor, not a junior with a mouse.
delivery slot booking software in Kenya should show who approved an override, so the conversation about the exception happens with the right person.
Reward the desk for promises kept, not for slots filled. The two numbers diverge quickly in a busy depot.
A team that is measured on bookings will always beat a team that is measured on deliveries, and the customer pays for the difference.
Give the desk a short written script and review two calls a week. Confidence comes from practice, and delivery slot booking software in Kenya cannot supply the tone of a polite refusal.
The Slot Record That Survives a Dispute
Three weeks later the customer says the delivery was booked for the morning and arrived after dark. The depot says the window was always two to five.
Without a record, the argument is settled by whoever is more senior or more tired.
delivery slot booking software in Kenya should keep an immutable log: the window offered, the window accepted, the confirmation sent, the arrival time, the name of the person who signed.
Keep it for at least ninety days, and keep it somewhere the customer service team can reach without asking IT.
The log should also record the messages sent, because “we told you” is only credible with a timestamp.
A depot that can produce that record within two minutes ends most disputes at the first phone call.
delivery slot booking software in Kenya that overwrites the original window when a delivery is rescheduled has destroyed the very evidence it needs.
Version history is not a technical nicety. It is the difference between a fair outcome and a goodwill credit.
The final operational point is simple: the promise is the product, and the record is the proof. Everything else is transport.
