Choose the Waka Cameroon service you need, then follow the right 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.

Negotiating fares

Cameroon ride requests use negotiated fare agreement. The passenger enters an FCFA offer before publishing, and riders decide whether to accept, decline, or counter.

• Passenger offer: enter the FCFA amount you want riders to consider before publishing.
• Rider response: riders can accept, decline, or send counteroffers. The conversation is capped at three passenger proposals and three rider proposals.
• Trip context: passenger count, luggage, vehicle type, stops, pickup, and destination are shown so riders can judge the offer.
• 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.

Inter-city travel

1. Open Inter-city travel, search by agency, travel date, departure city, and destination city.
2. Review the agency, route, boarding point, available seats, fare, and payment choice before booking.
3. Agencies manage departures, traveler messages, payment status, and reports from their own workspace.

Lodging and stays

1. Guests search Waka-reviewed stays by city, dates, and guest count.
2. Room cards show photos, features, rules, rates, and availability before the reservation form opens.
3. Lodging owners manage rooms, public profiles, reservations, reports, rules, visibility, and payment preferences.

Approved local adverts

Businesses submit their name, contact details, business type, advert message, reason, run window, and payment note. Waka reviews the request before it can appear as a public one-line advert.

Support, review, and public trust

Waka Cameroon separates each service doorway so passengers, riders, travelers, agencies, lodging owners, guests, and advertisers are not crowded with information that belongs to another task.

• Public agency and lodging information should be reviewed before visitors rely on it.
• Ride, travel, stay, and advert feedback should be specific enough that users know what changed.
• Support and safety reports stay tied to the service action that created them.

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.