Short answer: KiloDrive ride offers begin with a route-based quote, but the rider and an eligible driver can agree on a different offer before assignment. The app keeps the system estimate, current rider offer and driver counter-offer distinct. A match occurs only after a valid acceptance; an estimate, viewer count or response prediction is not a guaranteed driver, pickup time or final trip outcome.
What this means Review the route, stops, currency, payment method and expiry before requesting. If a fare changes, look at the latest amount and status rather than relying on an old notification. Drivers should accept or counter only when stationary or when it is safe to interact.
1. Build the same trip the quote will price
A useful quote depends on useful inputs. KiloDrive's ride request can include pickup, destination, intermediate stops, vehicle category, ride product, accessibility options, waiting time and—where an hourly ride is available—an intended duration. The server resolves the route and calculates in integer minor currency units.
The quote may reflect configured distance, time, base-fare and demand inputs. It is a decision aid, not a promise: traffic, a changed stop, an expired quote, unavailable mapping data or a later route can alter what is valid. The screen should identify the ISO currency instead of assuming dollars means USD. Read the rider workflow and current pricing information for the country-specific context shown in your account.
2. Choose the dispatch scope and current offer
Any driver is the broad dispatch option previously described as the general bidding hall. Depending on the live feature policy, other scopes may narrow who can view the request. The search experience can show an expiry countdown, dispatch scope and privacy-safe response information. These values should include freshness and confidence because a driver may go offline, take another trip or move outside the service area.
A rider can retain the quote or submit a permitted adjusted offer. KiloDrive preserves the immutable system quote separately from Your current offer. If the rider changes the fare, an earlier driver's exact-fare acceptance is not silently rewritten to the new amount; it must expire or be reconfirmed. This protects consent when the offer is lowered as well as when it is raised.
Optional auto-acceptance applies only when a driver accepts the rider's exact active offer and all locked eligibility checks pass. It does not make a driver appear, bypass payment validation or override a stale ride version.
3. Drivers review, accept or counter
An eligible driver may accept the rider amount or submit a counter-offer. The offer card can show the amount, driver rating context, verified-trip count and vehicle context to the rider. A driver may withdraw an offer and, while the ride is still actionable, submit a replacement. The actionable bid count should reflect current offers—not a lifetime count of withdrawn and rejected attempts.
Eligibility is checked again inside acceptance. Online status, fresh permitted telemetry, active assignments, duty state, membership rules, required documents, trust level and the selected vehicle can change after a bid was made. Rechecking prevents an old offer from assigning a driver whose position or compliance is no longer valid. The accepted vehicle and compliance version are snapshotted onto the trip so later profile edits do not rewrite the historical trip record.
4. Acceptance, cancellation and recovery
The rider selects one valid offer. The server uses an idempotency key and current lifecycle version so a double tap, late response or retry cannot create two assignments. Once committed, durable events let both devices recover after a SignalR disconnect or API recycle. A notification is a prompt to refresh; the authoritative trip state comes from the server.
If a request expires, the offer screen must close even when stale bid records exist. If the rider presses Back while cancellation is uncertain, the app should remain in a clear cancelling state or keep a durable cancellation pending until the server confirms it. Quietly leaving a live request visible to drivers would be misleading. Cancellation conditions and possible charges remain subject to the current Terms.
5. Live trip, chat, payment and receipt
After assignment, both participants see the active trip. The driver progresses through permitted states such as arrived, started and completed; each transition is versioned and recorded. Chat messages use a client message identifier so a retry after a lost response does not duplicate a message. Chat is participant-scoped and closes after cancellation or according to the trip policy. Review the Safety Centre before relying on live-location or emergency controls.
The accepted payment method must be validated transactionally. Available choices vary by country, wallet eligibility and provider readiness; a cash-only choice should not force a meaningless one-option picker. Completion records the agreed fare and payment context, and a receipt can show ISO-aware money, vehicle snapshot and trip details. If refresh fails, the app should label the last-known data as stale and disable actions whose preconditions cannot be revalidated.
What is still uncertain
Driver supply, response estimates, route-provider availability, payment methods and optional features vary by country and operational readiness. A displayed probability, viewer count or suggested fare cannot guarantee acceptance. Exact cancellation, waiting, toll, hourly and payment rules must come from the active quote, country settings and accepted terms—not from this general guide. See the Privacy Policy for how trip and location data are handled.
Sources
Frequently asked questions
Is the first fare estimate the price a driver must accept?
No. It is a route- and configuration-based estimate. The rider may make a permitted offer and an eligible driver may accept it or counter before assignment.
What does Any driver mean?
It is the broad dispatch scope for eligible drivers who meet the live country, location, vehicle, membership and safety rules; it does not mean literally every account can see or accept the ride.
What happens when the rider changes the offer?
The app keeps the system quote and current rider offer separate. A pending exact-fare acceptance must expire or be reconfirmed rather than silently changing to the new amount.
Can two taps create two trips or bids?
Protected mutations use idempotency and state versions so the same operation can be replayed safely or rejected as stale instead of being duplicated.
Is a response-time estimate guaranteed?
No. It is a freshness- and confidence-qualified estimate based on available signals. Driver movement, connectivity, eligibility and demand can change.