Request, negotiate, accept, ride, and resolve from one clear flow.

Passenger navigation

1. Open Passenger, sign in or create an account, and prepare your ride request.
2. Use Ride request for pickup, destination, optional stops, timing, vehicle preference, negotiation mode, route estimate, and fare offer.
3. Use My trips to review matched, active, completed, cancelled, and rating-ready rides.
4. Use Payment before publishing paid rides, then use Profile, Notices, Rewards, and Support for account operations.
5. After match, watch rider approach before pickup when live GPS is available, then follow ride status through arrival, start, completion, rating, and support.
6. Use support or safety reporting for wrong pickup, wrong vehicle, no-show, fare, route, payment, cancellation, rating, or account issues.

Choosing fare mode

The fare mode is chosen before the passenger publishes the request. It tells riders whether they can bargain or only accept the published fare.

• Negotiate: choose this when you want riders to accept your offer or send counteroffers. The conversation is capped at three passenger proposals and three rider proposals.
• No negotiation: choose this only when you are comfortable publishing the displayed fare as a firm offer. Riders can accept or decline, but they should not need to counter.
• If the proposed no-negotiation fare does not work: switch to Negotiate before publishing. That is the correct path for passengers who want a lower, higher, or rider-reviewed fare.
• After acceptance: the accepted fare is shown before the ride proceeds, and the request leaves the open marketplace for other riders.

Rider navigation

1. Open Rider, sign in or apply to drive with Waka.
2. Use Overview and Eligibility checks to understand approval, payment access, license, insurance, tax, and document requirements.
3. Use Initialize rider availability to go active and share live GPS only when ready to receive requests.
4. Use Ride requests to review nearby eligible rides, accept a passenger fare, or make a counteroffer within the proposal limit.
5. Use Destination, Earnings, Payout, Ratings, Notices, Support, and Profile to manage the rider account.
6. After match, follow navigation, mark arrival, start the ride, continue through stops, complete the ride at drop-off, and rate the matched passenger.
7. Use support for wrong passenger, unsafe pickup, no-show, route-change, payment, payout, document, account, cancellation, or rating concerns.

Operations navigation

The operations workspace is the private command center. It is intended for approved platform operators, not public signup.

• Overview, alerts, and diagnostics: monitor platform health, blockers, runtime warnings, and readiness.
• Rider approvals, tax and checks, passengers, and riders: review identity, documents, eligibility, and account state.
• Support inbox, reports, safety, messages, and broadcasts: resolve user issues and send one-way notices.
• Accounting, telemetry, audit, controls, and geography: inspect payments, mileage, operator actions, feature flags, and service areas.
• Cost and safety controls: use map tile limits, feature flags, account restrictions, support review, and service-area gates when needed.

Fare acceptance and limits

Acceptance is the handoff from marketplace to matched ride. Whether the passenger accepts a rider proposal or the rider accepts the passenger fare, WakaGood shows the accepted fare, closes the fare conversation for that request, removes it from the open marketplace for other riders, and takes both matched users into the active ride flow.

Negotiation is capped at three passenger proposals and three rider proposals. No-negotiation requests are firm-fare requests; if the passenger does not agree with the displayed fare, the passenger should use Negotiate before publishing. If the pickup, destination, stops, timing, or other route-affecting details change, fare guidance must be recalculated instead of sticking to the previous route.

Maps and ride visibility

Before pickup and destination are entered, the passenger request page can use a no-cost fallback. After both are entered, the request page can show a real map behind the form. After match, the passenger can see the rider approaching pickup with a live marker or line when GPS is fresh; approach tracking stops after pickup/start.

Policies to know

• Privacy Policy: explains account, location, payment-reference, support, notification, and retention practices.
• Terms and Community Guidelines: explains passenger responsibilities, rider responsibilities, fare negotiation, payment, safety, and conduct.
• Project Scope: explains the platform vision, role workspaces, backend systems, and operating principles.