Driver cash shortfall: keep unpaid amounts visible
A move costs ₪3,200, but the customer hands the driver ₪3,000. Closing it with a simple “paid” flag can hide the remaining ₪200 among calls and messages.
Explore the case ↗MOVENTIS
Useful articles
20 practical cases from a mover’s daily work: money, customers, drivers and crews. Explore the problem, steps and checks in Moventis.
Editorial examples of typical work situations. Names, amounts and examples are illustrative, not verified company stories or customer testimonials.
No articles found. Change your search.
A late driver: one plan instead of a chain of calls
The first job overruns while the next customer expects the vehicle at 11:00. The owner receives calls with conflicting arrival times.
Explore the case ↗The previous job is unfinished when a driver starts another
The driver arrives at the next customer, but the previous job is still in progress. Completion may have been forgotten, or a crew may still be working.
Explore the case ↗A customer adds furniture after agreeing the price
The offer covers a sofa, wardrobe and boxes. Before departure, a bed and shelving unit are added, so the old estimate no longer describes the work.
Explore the case ↗Rescheduling a move without leaving the old plan behind
The customer confirmed Thursday but requests Sunday. A driver and crew are assigned and the date is on the calendar.
Explore the case ↗City entered, street missing: check before sending
The customer says “Tel Aviv to Holon” without streets. The price is calculated, but the driver cannot navigate to the right entrance.
Explore the case ↗Same customer phone: avoid a second profile
A returning customer’s name is entered differently. Two profiles would split job history, notes and personal discount.
Explore the case ↗Bank transfer: the driver completes work without cash
A business customer will pay by bank transfer. The driver must not confirm cash that was never received.
Explore the case ↗Cheque payment: completion is not a bank receipt
The customer pays by cheque after unloading. A completed job should not hide the wait for actual funds.
Explore the case ↗A worker is absent: rebuild the crew before departure
One crew member is absent in the morning. The old roster remains in the job, risking wrong workload and expense assumptions.
Explore the case ↗Vehicle breakdown: reassign jobs without losing details
A vehicle is unavailable before departure. Several jobs use it, while the spare vehicle has another driver.
Explore the case ↗The lift is unavailable: confirm conditions before unloading
The estimate includes a lift, but it cannot be used on arrival. Carrying furniture upstairs changes the workload.
Explore the case ↗Screenshot item lists: review recognition before quoting
A screenshot contains abbreviations and several lists. Automatic parsing may confuse box counts or wardrobe types.
Explore the case ↗Returning customer and discount: keep the context
A customer returns months later. There were arrival notes and a personal discount, but the operator does not remember them.
Explore the case ↗An operator handles enquiries without financial reports
The owner delegates calls and quotes. Sharing the owner account exposes more data than the role needs.
Explore the case ↗A driver works for two movers: check the company
One driver receives work from multiple companies. Jobs and cash confirmations must not be mixed.
Explore the case ↗Revenue rises but profit does not: review job expenses
More moves are completed this month, but available cash does not grow. Order totals alone do not show what remains after expenses.
Explore the case ↗How many jobs did a worker complete? Check assignments
Month-end staff workload is unclear. Outdated crews can attach completed work to the wrong person.
Explore the case ↗No driver push: the job must still be accessible
A job is assigned but no alert appears. Permission, account selection or device subscription may be missing.
Explore the case ↗A difficult customer: keep facts, not emotional labels
A move leaves a dispute over items or payment. A new operator may accept another enquiry without knowing the context.
Explore the case ↗