All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Taxi / Ride-hailing Platform · Available now

Follow each ride from booking to verified completion.

Taxi / Ride-hailing Platform runs the operational record of a ride from a booking and pickup request through driver assignment, trip events and completion review. Dispatch teams prepare the ride interval, service zone and rider addresses.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewActive Bookings
Taxi / Ride-hailing Platform · Bookings

Active Bookings

Bookings in one list

New booking
Bookings in view
6
Approved
6
Record numberSubjectStatusStarts atEnds atService zone
BKN-92988Amina Yusuf, station to Elm StreetApproved17 Oct19 OctDowntown core
BKN-94886Carlos Vega, airport to North QuayApproved26 Oct29 OctAirport corridor
BKN-37628Mei Chen, Market Square to clinicApproved02 Nov07 NovNorth district
BKN-61547Darius Cole, hotel to West PierApproved19 Oct27 OctWest waterfront
BKN-56304Priya Shah, Cedar Lane to airportApproved18 Oct21 OctUniversity district
6 of 6 records
Amina Yusuf, station to Elm StreetBookings · BKN-92988
Approved
Starts at17 Oct
Ends at19 Oct
Service zoneDowntown core
OwnerAmina Yusuf
Review bookingBKN-92988 · Amina Yusuf, station to Elm Street

Operations Reviewer independently approves the current booking revision before dispatch.

Waiting for Operations Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
20
Saved views
15
Roles with set permissions
6
Reports and dashboards
8
Features

Your ride operations desk

Every feature works on the same records. Pick one to see the screen your team works in.

Ride bookings

Plan pickup requests, preserve the ride interval and give the reviewer a clear booking.

  • Prepare the request
  • Ask for review
  • Keep the journey visible
  • Bookings
  • Ride requests
  • Organizations
  • Team members
  • Resources
Explore ride bookings
OverviewBookings Awaiting Review
Taxi / Ride-hailing Platform · Ride bookings

Bookings Awaiting Review

Cancelled waits for the dispatcher

New
Record numberSubjectStarts atEnds atRequested unitsRevision
BKN-35129Amina Yusuf, station to Elm Street18 Oct27 Oct280220
BKN-34880Carlos Vega, airport to North Quay16 Oct23 Oct280730
BKN-69969Mei Chen, Market Square to clinic13 Oct22 Oct60610
BKN-36653Darius Cole, hotel to West Pier13 Oct19 Oct390670
BKN-32387Priya Shah, Cedar Lane to airport14 Oct21 Oct600550
6 of 6 records
Amina Yusuf, station to Elm StreetBookings · BKN-35129
Starts at18 Oct
Ends at27 Oct
Requested units280
Revision220
CounterpartyNorth district drivers
Example screen with sample data
Process

From booking to verified completion

Booking to verified completion ships ready to use. One step needs a named approval before the work moves on: Review booking (Operations Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Book ride

    Prepare the pickup, destination and planned interval for review.

    Amina Yusuf, station to Elm StreetBKN-92988 · Dispatcher
    Book rideBy Dispatcher
  2. Review booking

    Decide the current journey scope and retain the reason.

    Amina Yusuf, station to Elm StreetBKN-92988 · Operations Reviewer
    Review bookingBy Operations Reviewer
    ApprovalOperations Reviewer independently approves the current booking revision before dispatch.
  3. Match driver

    Confirm an accepted driver and vehicle against current availability.

    Amina Yusuf, station to Elm StreetBKN-92988 · Operations Reviewer
    Match driverBy Operations Reviewer
  4. Perform trip

    Follow pickup progress and record observed trip events.

    Amina Yusuf, station to Elm StreetBKN-92988 · Trip Coordinator
    Perform tripBy Trip Coordinator
  5. Capture completion

    Connect completion evidence to the booking and ride request.

    Amina Yusuf, station to Elm StreetBKN-92988 · Trip Coordinator
    Capture completionBy Trip Coordinator
  6. Reconcile evidence

    Verify complete, consistent completion evidence and follow up on missing or conflicting records.

    Amina Yusuf, station to Elm StreetBKN-92988 · Operations Reviewer
    Reconcile evidenceBy Operations Reviewer
Inside a record

Keep the journey and evidence together

Open any booking to see its booking resources, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Starts at, Ends at, Service zone and Owner.

  2. 2
    Booking resources

    Each line is linked to this booking.

  3. 3
    Who works on it

    Dispatcher, Operations Reviewer and Trip Coordinator, each with their own permissions.

  4. 4
    Process stages

    Book ride and Hold resources, with the role that acts.

  5. 5
    Approvals

    Review booking, with who decides.

Active BookingsAmina Yusuf, station to Elm Street
Taxi / Ride-hailing Platform · Bookings

Amina Yusuf, station to Elm Street

Downtown core · Approved

Log activity
1
Record details
Starts at17 Oct
Ends at19 Oct
Service zoneDowntown core
OwnerAmina Yusuf
2
Booking resources

Amina Yusuf, station to Elm Street

Line numberParentDriver
BR-43344Amina Yusuf, station to Elm StreetElias Park
BR-78922Priya Shah, Cedar Lane to airportDarius Cole
BR-75998Noura Haddad, library to South GateMei Chen
Booking resources
6
Total revision
3,340
3

Who works on it

  • DispatcherManage Bookings, booking resources, ride requests
  • Operations ReviewerManage review decisions, operation receipts
  • Trip CoordinatorManage ride requests, trip tracking events, trip completion…
4

Process stages

  • Book rideDispatcher
  • Hold resourcesDispatcher
5

Approvals

  • Review bookingOperations Reviewer
    Approved
Example screen with sample data
Approvals

Review the ride before dispatch

Dispatcher prepares the journey. Operations Reviewer independently decides its current revision and records the reason. Configure the boundary using staff accounts before the pilot.

OverviewApprovals
Taxi / Ride-hailing Platform · Overview

Approvals

Signed in as Operations Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • BKN-35129Amina Yusuf, station to Elm Street
    North district driversRequested by Noura Haddad
    Waiting3dActions
  • BKN-34880Carlos Vega, airport to North Quay
    Executive car poolRequested by Luca Moretti
    Waiting1dActions
  • BKN-69969Mei Chen, Market Square to clinic
    Campus pickup teamRequested by Priya Shah
    Waiting4dActions
  • BKN-36653Darius Cole, hotel to West Pier
    North district driversRequested by Elias Park
    Waiting5dActions

Who approves what

DecisionApprover
Review bookingDecide the current journey scope and retain the reason.Operations Reviewer
Approve Bookings, trip completion evidenceOperations Reviewer
Approve payment evidenceFinance Operator
3 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Taxi / Ride-hailing Platform to the work that is theirs. Pick a role to see what it starts with.

Dispatcher

Prepares ride bookings and confirms accepted driver and vehicle assignments.

This is the first screen this role sees.

OverviewRide booking schedule

Ride booking schedule

Bookings · Dispatcher

Review3
Amina Yusuf, station to Elm StreetDowntown core
14 Oct
Mei Chen, Market Square to clinicNorth district
16 Oct
Priya Shah, Cedar Lane to airportUniversity district
17 Oct
Add
Approved3
Carlos Vega, airport to North QuayAirport corridor
29 Oct
Darius Cole, hotel to West PierWest waterfront
24 Oct
Luca Moretti, campus to Old TownSouth residential
29 Oct
Add
Example screen with sample data
Reports

Find rides that need attention

Answer dispatch, completion and payment questions from the operating records.

Overview
Taxi / Ride-hailing Platform · Overview

Taxi / Ride-hailing Platform dashboard

This quarter

Payment evidence in view
6
Total amount USD
3,530
Base Fare
1
Surge Fare
1

Bookings by status

How far records got this quarter

StageReachedStep
Draft25
Review1144%
Approved655%
Executed467%

Number of bookings by status

Sample counts per stage

900
60Draft
80Review
90Approved
50Executed
80Rejected
Example screen with sample data
  1. 01Booking workload

    Which service zones have Draft, Review or Approved rides in the upcoming interval, and who owns the work?

  2. 02Driver assignment register

    Which driver and vehicle are attached to each resource line, and when was the assignment confirmed?

  3. 03Ride request outcomes

    Which requests completed and which were Missed in the period being examined?

  4. 04Trip event exceptions

    Which Delay or Exception observations need investigation, and which source supplied them?

  5. 05Completion evidence review

    Which completions are still Captured or Disputed, and what notes explain the issue?

  6. 06Fare evidence by booking

    Which components belong to the ride, and what currency and payment state apply to each amount?

  7. 07Fleet maintenance exposure

    Which due service plans and unresolved defects affect vehicles the desk may assign?

  8. 08Review and receipt exceptions

    Which returned decisions, escalations and Failed receipts need a named person to follow up?

Controls

Keep decisions tied to the right ride

Each stage of booking to verified completion names the role that acts and the status it records, so a change is never anonymous.

OverviewBooking to verified completion
Taxi / Ride-hailing Platform · Process

Booking to verified completion

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
16
Book ride
Dispatcher
StatusDraft → Review
RecordsRide requests, Bookings
Review bookingApproval
Operations Reviewer
StatusReview → Approved
RecordsReview decisions, Bookings
Match driver
Operations Reviewer, Dispatcher
StatusProposed → Assigned
RecordsBooking resources, Bookings, Vehicles
Booking to verified completion
  1. Start
    Book rideDraft → Review
    Ride requests
  2. Approval
    Review bookingReview → Approved
    Review decisions
  3. Step
    Match driverProposed → Assigned
    Booking resources
  4. Step
    Perform tripAssigned → Active
    Trip tracking events
  5. Step
    Capture completionActive → Completed
    Trip completion evidence
Example screen with sample data
AI agent

Help with your next operating decision

Use an assistant to prepare dispatch questions and evidence reviews for your team.

It can

  • Dispatcher: Find my upcoming bookings and show which ones still need a reviewed revision or a confirmed resource.
  • Operations Reviewer: Bring together the current booking revision, review reason and completion evidence for a disputed ride.
  • Trip Coordinator: Find Reported trip events for the booking and help explain their observed times and sources.
  • Finance Operator: Show the fare components and provider event identifiers for a booking before I review the charge evidence.

Stays with a person

  • The assistant needs configured access to the records and connections it uses.
  • Operations Reviewer remains responsible for booking decisions and authorized corrections.
  • Finance Operator checks the provider evidence before confirming a payment state.
  • Fleet Coordinator examines actual condition evidence before a vehicle returns to service.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Taxi / Ride-hailing Platform
  • Rider booking channels
  • Driver and partner channels
  • Telematics and trip events
  • Fare and payment providers
  • Fleet service records
  • Document storage
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 20 tables
20tables
  • Ride bookings5
  • Driver dispatch6
  • Trip tracking and completion7
  • Fare and payment evidence5
  • Fleet upkeep6
  • Review and operations7
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the operating scope

    Select the service zone, participating fleet and initial intake channel. Admin confirms organization and staff identity with Dispatcher and Operations Reviewer. Decide which external systems supply driver matches, fare components and payment outcomes.

  2. Prepare the records

    Fleet Coordinator checks driver activity, license details and vehicle condition. Dispatcher prepares open bookings with their ride requests and resource references. Follow the migration order and preserve the identifiers used by existing evidence.

  3. Configure authority and worklists

    Set up staff access and the screens each team uses. Operations Reviewer defines the booking review and correction policy. Finance Operator agrees the payment currency convention and the evidence required for each payment state.

  4. Rehearse the journey

    Run a booking from Draft through review, accepted match, trip events and completion verification. Include an unavailable vehicle, a no-show and completion evidence attached to the wrong request. Check the actual records after each handoff.

  5. Release the pilot

    Confirm that staff can find unresolved work and that connections retain the right booking identities. Reconcile imported open rides and test duplicate incoming events before enabling ordinary operations. Expand the scope after the operating owners accept the pilot results.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Taxi / Ride-hailing Platform.

All questions
How do I get started?

Click Get started, then use Proto to configure Taxi / Ride-hailing Platform for your business. Begin with a familiar service zone, current driver and vehicle records, and a representative booking. Rehearse its review, accepted match, completion and payment evidence before expanding the operating scope.

What does the dispatch desk work from?

Dispatcher uses the booking interval and linked ride request, then confirms the driver and vehicle through the booking resource. The request retains the rider's pickup and dropoff details. Operations Overview brings operating work and exceptions together for the desk's review.

Who approves a booking?

Operations Reviewer independently examines the booking in Review and records the decision, reason and source revision. Configure that authority separately from Dispatcher preparation access and rehearse a changed booking before the pilot begins.

How do we confirm a driver match?

Dispatcher checks an accepted match against current driver and vehicle availability, then confirms the resource and its time. If a suitable match cannot be confirmed, keep the request visible and record an escalation for Operations Reviewer.

How are pickup and completion recorded?

Trip Coordinator follows the request through En Route, Arrived and Completed as the journey occurs. Trip events retain observed time and source. Completion evidence connects the booking and request so Operations Reviewer can verify a complete, consistent result. Missing evidence stays Captured; discrepancies become Disputed. Both need an escalation and a Failed receipt for follow-up.

What happens when the rider does not travel?

Follow the agreed cancellation policy and record an evidenced no-show as Missed on the request. Release an existing assignment when appropriate and retain the cancellation review and receipt. Examine any performed work before choosing a correction path.

How do we review fare components?

Finance Operator links each supported component to its booking and provider event. Agree the currency convention and fare-provider connection during setup. Retain the fare breakdown when a Base Fare, Waiting Time Charge or Toll needs explanation.

When can payment evidence be marked Paid?

Use Paid when the corresponding provider evidence supports the outcome. Trip completion gives the payment review its journey context. Keep the provider event identifier available for investigation, and follow the provider's confirmation process for adjustments.

Can vehicle upkeep inform dispatch?

Fleet Coordinator maintains vehicle inspections, defects and maintenance plans. Dispatcher checks the selected vehicle's status and relevant condition evidence before confirming it. Agree the return-to-service policy and rehearse a vehicle withdrawn after it was proposed for a ride.

Can we bring existing bookings and evidence?

Yes. Prepare organization and staff identities, then load resources before open rides and their linked evidence. Preserve the source identifiers used by reviews and provider events. Reconcile the imported work and rehearse repeated incoming messages before enabling the pilot connections.

Set up Taxi / Ride-hailing Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appTaxi / Ride-hailing Platform

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.