Skip to main content

Rider Guide

Version: v1.0
Last Updated: June 6, 2026

How riders work with BookMaMe: joining a delivery company, handling active jobs, completing pickup and delivery handoffs, returning failed jobs, and understanding mixed-source task flows.

The rider app​

The rider app is available on iOS, Android, and web. Riders log in using the account created or approved through their delivery company.

From the rider app you can:

  • receive jobs
  • go online or offline
  • open task details
  • navigate to pickup and drop-off points
  • complete handoff confirmations
  • fail and return tasks when needed

Joining a delivery company​

Riders work through a delivery company, not directly as an independent marketplace actor inside the customer apps.

Typical onboarding includes:

  • name and phone number
  • vehicle or transport mode
  • ID or verification details
  • delivery-company approval before jobs can be received

Your job list​

The rider app can now show a broader set of source types, such as:

  • restaurant deliveries
  • shop deliveries
  • rental outbound or return jobs
  • second-hand deliveries
  • parcel delivery jobs
  • retry or return tasks

Each job card may include:

  • source reference
  • pickup location
  • drop-off location
  • status
  • package or fulfillment context

📸 Screenshot: Rider app — assigned jobs list

Assigned jobs are operationally ordered by the dispatch flow, with older assigned work typically appearing first.

Job details​

Open a job to review:

  • source reference / request number
  • pickup and drop-off information
  • customer / sender / recipient context where relevant
  • status and instructions
  • package details where supported

For some jobs, especially parcel delivery, you may also see:

  • delivery class
  • computed total weight
  • computed total volume
  • parcel notes or images

Pickup handoff​

Pickup is not identical across all task types, but the rider app guides you through the handoff steps relevant to the source.

Typical pattern:

  1. Navigate to the pickup point
  2. Follow the pickup instructions shown in the job
  3. Complete the pickup confirmation step
  4. Start the delivery leg

Depending on the source, the confirmation may involve:

  • a partner-side confirmation
  • a customer/sender-side confirmation
  • a code/PIN handoff

Only confirm pickup when the item or parcel is genuinely in your possession.

Delivery confirmation​

At drop-off, the rider app uses the delivery-confirmation step shown for that job.

Depending on the source, this may involve:

  • entering a customer or recipient PIN
  • waiting for an in-app confirmation on the other side
  • following source-specific handoff prompts

The important rule is the same:

  • do not mark the job delivered until the real handoff has happened

Parcel delivery specifics​

Parcel delivery adds a few rider-specific differences:

  • sender-side pickup start / confirmation can be part of the collection flow
  • recipient confirmation may happen through a linked recipient flow or a sender-assisted relay flow
  • parcel tasks may later move into retry or return-to-sender states
  • job details can include richer package metadata than older delivery flows

So parcel work often feels more like operational logistics than a simple restaurant drop-off.

Cash and card collections​

Some rider jobs require collecting payment during fulfillment, such as:

  • cash on delivery
  • card on delivery
  • other rider-collected handoff payments where supported

When a job includes a collection:

  1. collect the required amount
  2. confirm the collection in the rider app
  3. complete the delivery only after both the money and the handoff are correct

These amounts are tracked separately from rider earnings.

Failed deliveries and depot return​

If you cannot complete a delivery:

  1. mark the failure in the app
  2. choose the right failure reason
  3. return the item or parcel to the delivery company when instructed
  4. complete the depot/company handoff step

The delivery company then decides the next operational outcome:

  • retry
  • return
  • return to sender
  • another source-appropriate resolution

Return tasks​

Some jobs are explicitly return-oriented rather than normal outbound delivery.

Examples include:

  • rental return-related movement
  • second-hand reverse movement
  • parcel return-to-sender flows

These tasks still use the same rider app, but the pickup/drop-off semantics are different from a normal forward delivery.

Live location and monitoring​

While a job is active, the platform may use rider location for:

  • customer-facing tracking
  • delivery-company dispatch visibility
  • ETA monitoring

Keep location permissions enabled while delivering.