Route Capture
Pickup and destination details are captured alongside map context and approximate travel distance.
Connected Passenger Transport Case Study
Connected Booking, School-Run Attendance and AI Support for Rickshaw
Isoft delivered three connected digital capabilities for Rickshaw: a responsive customer booking workflow, IoT-assisted attendance capture for school runs and AI chatbot integration.
Three connected capabilitiesbooking, attendance capture and AI-assisted support
ClientRickshaw
IndustryPassenger Transport
SolutionBooking, IoT & AI
DeliveryConnected Digital Workflows
The booking challenge
Capture complete journey requirements without forcing customers to call
A passenger-transport booking contains more than a name and phone number. The service needs accurate pickup and drop-off details, timing, passenger and luggage counts, vehicle requirements and information that can affect the journey.
Rickshaw needed a customer-facing form that could guide users through these decisions and convert the information into a consistent digital booking request.
The goal was to turn a multi-step transport enquiry into one clear, responsive customer journey.
Information the workflow needed to capture
- Pickup and drop-off locations
- Immediate or scheduled travel
- Vehicle and fixed-price preferences
- Passenger and luggage quantities
- Flight details and driver instructions
- Baby-seat and accessible-vehicle requirements
What Isoft delivered
A guided booking workflow built around real passenger requirements
The interface combines route context, pricing information and service requirements in a form customers can use across desktop and mobile devices.
Journey Scheduling
Customers can request transport immediately or choose a later date and time.
Vehicle Selection
Car and van choices communicate passenger capacity and the estimated journey information.
Fare Estimation
The booking experience presents the estimated fare and supports a fixed-price preference.
Passenger Requirements
Passenger numbers, luggage, flight information and special instructions are captured before submission.
Accessible Options
Customers can identify baby-seat and hoist-van requirements within the same booking flow.
IoT-assisted school-run attendance
Connecting physical QR scans with the School Run application
Rickshaw also required a practical way to capture attendance during school transport operations. Isoft integrated a barcode or QR scanner with a compact Wi-Fi-enabled edge device so scanned identifiers could be transmitted to the School Run application through an API.
This connected a physical action at the transport point with a structured digital attendance event in the operational system.
The value was not the scanner alone—it was connecting the scan reliably with the application where attendance information was required.
Delivered integration scope
- Barcode or QR scanner connected to a Wi-Fi-enabled edge device
- Scanned identifier prepared for API transmission
- Integration with the School Run application
- End-to-end scan and data-transmission testing
- Configuration for use within the operational environment
AI Chatbot Integration
Isoft also integrated an AI chatbot into Rickshaw's digital environment, creating a conversational entry point that could support customer interactions alongside the existing web experience.
The case study does not assign enquiry-reduction, conversion or service-level results because those outcomes have not been independently confirmed.
Applied AI within the service experience
Adding conversational support without disconnecting it from the wider customer journey
The chatbot integration demonstrates how applied AI can sit alongside structured booking and operational workflows rather than operating as an isolated technology experiment.
- Conversational interface integrated into the client's digital environment
- A complementary channel alongside the structured booking experience
- A foundation that can be refined around confirmed customer-service use cases
Connected workflow examples
Turning physical and digital interactions into structured operational information
Capture
Receive route details, passenger requirements, QR data or a chatbot interaction.
Structure
Convert the interaction into information the relevant workflow can process.
Transmit
Move the information through the booking interface, API or integrated digital channel.
Use
Make the captured information available to the corresponding transport operation.
Responsive customer experience
The same structured booking journey across desktop and mobile
The responsive interface keeps route entry, vehicle choice, fare information and passenger requirements accessible on the devices customers use when arranging transport.
The project image is based on Rickshaw's live booking workflow and uses the genuine Rickshaw identity with non-personal sample information.
View Rickshaw's Booking Form
Delivered outcome
A broader connected foundation for passenger transport interactions
Across the three initiatives, Isoft helped Rickshaw capture and move information through customer booking, school-run attendance and AI-assisted customer interaction workflows.
Digital bookingcovering route, scheduling, vehicle choice and passenger requirements
IoT attendance captureconnecting QR or barcode scans with the School Run application
AI chatbot integrationadding a conversational channel to the wider digital experience
This case study describes the Rickshaw booking workflow, School Run scanner integration and AI chatbot integration delivered by Isoft. It does not claim ownership of the wider dispatch platform or attach unverified attendance, enquiry-reduction, booking-volume, conversion, revenue or administration-saving figures. Hardware features that were discussed but not confirmed as delivered—including offline queuing, duplicate suppression and specific status indicators—are not claimed.
Related capabilities
Explore the work behind these connected transport workflows
Are customer, device and operational workflows still disconnected?
Book an Operational Systems Review to identify how booking, field capture, APIs and customer-service tools can work as one connected system.