· Planet01
Restaurant chains shopping for dispatch software often get a tour of a map. Maps are necessary and they are not the product. The product is the set of decisions the branch repeats every night.
Ask how assignment works in plain language. Can the rule combine closest rider and longest wait, and can each branch set its own radius? If the answer is a fixed algorithm you cannot see, peak hour will be full of manual exceptions and the software will be blamed for them.
Ask where cash lives. If COD is “a report tomorrow,” the branch will keep a parallel notebook. Ask how an incident is written down when a phone is snatched or a rider is in an accident. Ask whether your POS can create the ticket without a second entry, and whether your customer app can show the rider.
Then ask who stays after go-live. Rider Desk is implemented by Planet01 with analysis, training, and maintenance because a dispatch tool without that support becomes another login. If you are comparing options, use one real branch as the script and make every vendor run that script, not theirs.