Onde

Create a dedicated page or FAQ section about background check integrations, specifically mentioning whether Onde integrates with providers like Checkr or Sterling, or if manual verification and document upload is required.

Create a dedicated FAQ or feature page explaining the maximum advance booking window for scheduled rides, including whether 30-day advance bookings are supported for airport transfers.

Create a dedicated API documentation page that specifies rate limits per endpoint (requests per second/minute) and explains quota increase options for high-volume integrations. Consider adding this to a developer portal or technical documentation section.

Create a dedicated page or FAQ section explaining the Driver app's offline capabilities, specifically addressing whether drivers can accept rides and complete trips without cellular connectivity, or if constant connectivity is required.

Create a technical documentation page or FAQ entry that specifies the push notification infrastructure: whether Onde uses FCM, APNs directly, or a third-party provider like OneSignal, and include details on delivery rates and reliability metrics.

Clarify explicitly whether Onde creates developer accounts under the client's own Apple/Google developer accounts (with client as account owner) or creates managed accounts that Onde controls on behalf of clients. Buyers need to know who owns the account, who pays the annual developer fees, and what happens if they leave Onde.

Add a specific example or documentation showing whether tiered percentage commissions (e.g., 80% for first N rides, 75% thereafter) can be configured, or clarify if only flat fees and simple per-order percentages are supported.

Create a dedicated page or FAQ entry specifically addressing multi-currency support, regulatory compliance localization (e.g., data residency, local tax rules), and whether these require separate instances or can be handled within a single deployment with multiple operational areas.

Add a dedicated support/SLA page with specific response time commitments for enterprise customers (e.g., '30 minutes for critical outages') and clearly state available escalation channels (phone, ticketing, dedicated account manager).

Add a technical specifications page or FAQ entry that explicitly states the GPS location update frequency (e.g., 'every 2 seconds', 'adaptive 1-5 seconds based on speed'), or document the minimum/maximum update intervals and whether the frequency is configurable.