Features

Location is at the heart of business automation. Whether managing deliveries, field service or gig work, your logistics applications will need app user location to make your business better.

  • Track app users: Tracking app users generates a location timeline organized as activities and outages. Tracking app users involves setting up and managing users, managing permissions for privacy, implementing tracking controls so users are tracked only when working, consuming tracked data through views, webhooks and APIs, and avoiding common pitfalls to improve tracking rates.

  • Automate distance-based payouts: Actual distances covered by app users is an important input to financial systems for field workers. Distances are used to bill customers and pay out partners. Accurate map-matched distances are automatically generated for drives, durations for stops, steps for walks, estimated distances for system-driven outages, and durations of user-driven outages. Accurate distance computation for actual movement builds trust with customers and partners, and saves money by eliminating expensive maps costs involved in distance estimation. That means, a better solution at lower cost.

  • Dispatch work to Nearby drivers for on-demand orders. Proprietary order assignment systems can search nearest users through Nearby API, get a nearest first list of users sorted by live ETA, and merge those results with skills, vehicles, or other business considerations to significantly improve dispatch efficiency.

  • Manage driver availability when drivers are available to receive orders you need to track their location so you can assign relevant orders that are nearby. Prior to assigning them orders, you only need to track the latest driver location and not the other aspects like distance travelled, stop times etc which are relevant when they are fulfilling orders. The HyperTrack SDK allows you to do just that through the 'availability' method. Its the easiest way to track recent driver location for your available drivers to assign orders.

  • Track live route and ETA delays with Trips: Trips may be used for tracking orders with live routes, ETAs, delays and no-shows. Order tracking with live location is a popular use case across industries and regions. From high growth startups to enterprises delivering products and services to customers, "where's my order?" is a moment of anxiety for customers and ops teams. Operations teams can proactive handle delays & no shows, reduce customer support cost, improve NPS scores, and power a great customer experience with this feature.

  • Track arrival, exit, route with Geofences: Geofences help track arrivals, exits and routes to places of interest. Set up geofences when you expect app users to frequently visit places of interest. These could be your offices, partners, branches, or other places of interest that a group of users might visit over the course of the week or month. Or these could be customer or commercial areas that specific users are expected to visit during the day or week.

  • Track work day with Geotags: Geotags help annotate the location timeline with actions performed by the app user in the app. Every important work done by the app user can be captured as a geotag with a payload that represents it.

  • Assign and route orders through the order assignment dashboard. Orders may be uploaded as CSV or posted through an API. Store managers can accept or decline orders, plan the accepted orders into trips, and then assign trips to available users. Live trip progress is tracked relative to plan, and all downstream tracking features come alive automatically. Fleets using Visits app will automatically see their trips with orders show up in the app, with auto checkin and checkout at arrival and exit respectively, and ability to add geotags to each visit.

  • Track progress with Scoreboard: Scoreboard provides charts that track progress of operations through the day, in comparison with the past 7 or 30 days. Scoreboard views may be securely embedded into your own operations dashboards by region, team or custom metadata. They may be viewed and embedded by region, team or any other application metadata of your choosing.