MapPoint: Route-Based Pricing

With Microsoft MapPoint integration it is possible to provide accurate prices to customers for all bookings, based on the predicted route for the journey.

Additionally, Evocab can display the route on-screen in the office, showing the route that MapPoint has used to calculate the distance for the journey.  This also provides step-by-step directions which can be printed out for drivers if required (or indeed relayed over the radio, should a driver be lost).

CLI Advanced

Evocab's existing CLI (Caller Line Identification) package detects the incoming phone number, and can populate the Booking Screen (pick-up details, etc) using data saved to the phone number record, but CLI Advanced expands upon the functionality of the existing Caller Line Identification (CLI) system by allowing telephonists to see a list of the most Recent Journeys booked from this phone number.  The telephonist can then choose to apply the pick-up, destination, or entire journey (including Vias) to the current booking, making it possible to increase the speed of making bookings.

Additionally, when viewing the Recent Journeys list, the telephonist can also see the frequency of each journey, and the % of no-shows from each pick-up.  Obviously the latter is an incredibly useful tool for avoiding No-Jobs.

'Blacklisting'

It is now possible to 'blacklist' addresses and phone numbers, so that when that address or phone number is entered on to the Booking Screen a warning flashes to alert the telephonist, which can be clicked on to find out the reason why the record is Blacklisted.  If necessary, the Blacklist can be overridden in order to process the booking, and can be edited or removed for future bookings.

Crucially, if the customer has IVR, it is possible to connect the Blacklist feature to IVR so that the caller will hear a (configurable) message explaining why their number has been blocked, and then hang up.  Where necessary, IVR can even hang up without playing a message, so the caller thinks there is a fault on the line and stops calling.

Queue Positions for Data Unit 'Flags'

When a driver sends a 'flag' (e.g. RTS, No Job, Booking Request etc) to the office, it is possible to let the driver know his or her position in the queue for that flag.  So for example, if a driver sends an RTS, this will tell them how many RTS requests are ahead of them in the queue.

This is extremely useful for instances such as driver RTS messages on a busy Friday night because often the driver won't immediately get a response from the office, and so will re-send the flag because they don't think the first one got through.

With this feature the can see exactly where they are in the queue for the flag, so they know it got through and can estimate how long it might take to get to them.

Credit Cards For Everyone

We have added a new Card Payment System to Evocab, to allow all sites to accept card payments for bookings, either at the point of booking, or later from the Enquiry Screen.  It is even possible to initiate a partial refund (e.g. for applying No-Job charges), and the entire system is underpinned by the latest security card features.  Best of all, this module is now included as standard with all Evocab systems, with no hardware requirements; or implementation, support or ongoing monthly costs.