We’ve introduced a Cancellation Policy setting on the Dashboard that allows operators to control when customers can cancel their bookings. The available options are: never, before a booking is dispatched, before the driver starts approaching the first stop, or before arrival at the first stop. For more details, see the MotionTools API Announcements.

The previous policy was very strict and non-configurable, forcing customers to contact support almost every time they needed to cancel a booking, even in cases where cancellation wouldn't incur any penalty or cause any dispatching issues. This created unnecessary operational overhead.

We’re working on improving the experience for customers who use our platform programmatically by making the progress of bookings more transparent. Soon, we’ll introduce new webhooks to track booking progress, notifying when a tour carrying a booking’s stops becomes En Route, when drivers arrive, complete, or fail a stop, and when a driver’s location changes.

We’ve introduced the MotionTools API Announcements page, where our backend team shares API changelogs along with detailed instructions on using new platform features via the API. The page also includes deprecation announcements, and we recommend subscribing to the page to stay up to date with the latest changes and alerts.

Admins can now cancel bookings in the Dispatched status. This extends the feature released in May, which allowed cancellations for Partially Dispatched bookings. For more details about the feature and the possible outcomes of canceling a Dispatched booking, see the MotionTools API Announcements.

We’ve introduced a dedicated booking property for storing an external ID, for example, your system’s unique booking identifier. You can add the ID when creating a booking or update it at any time later. Bookings can be searched and filtered by this ID on the Dashboard and through the API, and the ID is also included in all booking-related webhook events. For more details on the corresponding API changes, see the MotionTools API Announcements.

Admins and customers can now provide driver instructions using predefined templates. These instructions give drivers extra guidance on tasks to complete at each stop, for example, verifying the recipient’s age. At the moment, only the age verification instruction is supported, but we plan to expand the list of templates and make them configurable in the Dashboard. For more details, see the MotionTools API Announcements.

We’ve started work on platform-wide support for tipping drivers. As a first step, we’ve introduced a new booking property for storing the tip amount. Customers can add this only when creating a booking. Sending and accessing tip information is currently available only through the API. To learn more, see the MotionTools API Announcements.

We’ve introduced a dedicated webhook for tour earnings updates. Use this webhook instead of relying on the broader “tour.modified” webhook if you only need notifications about earnings changes. To learn more about supported webhooks, see the MotionTools API Documentation.