Completed / in field use
- Production telephony, human transfer, and call records
- Fleet back office, extensions, and human voice review
- Field use of order and dispatch engines
Flagship product
AnyTaxi
AI Voice Fleet Operations Platform
Starting with the phone call, AnyTaxi converts inbound orders into traceable, structured records and connects them to dispatch and fleet operations. It is deployed in fleet operations, with AI and dispatch capabilities still under validation.
Positioning
Not just transcription — turning calls into executable orders.
AnyTaxi is designed to preserve the phone-based ordering habits fleets already have, while producing structured and traceable operations data. That requires voice processing, order workflows, and dispatch systems to be designed together.
Keep the phone channel
Passengers keep calling as usual, reducing behaviour change at adoption.
Turn speech into fields
Extract pickup, time, and passenger details, while flagging information that needs human confirmation.
Make operations reviewable
Orders, processing states, and review records form traceable operations data.
Order workflow
Five inspectable stages from call to dispatch.
This is the current workflow design. Each stage includes failure handling and human intervention points so ambiguous information does not flow directly into dispatch.
-
01
Inbound call
A voice workflow guides the caller to provide pickup, time, and trip details.
-
02
Speech-to-text
Call audio becomes text, creating a traceable processing record.
-
03
Field extraction
Address, time, passenger count, and notes are extracted into structured fields.
-
04
Human review
Low-confidence or ambiguous details are confirmed by a person before proceeding.
-
05
Order & dispatch
The order is created and connected to dispatch, producing traceable operations data.
The workflow is used in operational settings. The degree of automation and human intervention varies by deployment.
Capability status
What is deployed, and what is still being validated.
The table reflects the October 2026 internal audit and field evidence. AnyTaxi is deployed in operations; recognition, dispatch, and end-to-end workflows remain under validation. Recognition rates, SLAs, and customer outcome figures are not published.
-
Voice order intake and call recordsCompleted
Production phone lines, human transfer, and call records are in operational use. SLA and concurrent-call capacity are not published.
Completed -
Address and destination parsingIn validation
Field use continues alongside low-confidence follow-up design. Per-language recognition and order-creation rates are not published.
In validation -
Order management and dispatchIn validation
The dispatch engine and fleet back office are used in the field. End-to-end reconciliation from voice to order to dispatch remains under validation.
In validation -
Fleet back office and operations dataCompleted
Call handling, extensions, and human voice review have release and operating records. Page-level permissions and latest releases still require periodic acceptance.
Completed -
Driver and passenger appsIn validation
Device and field acceptance continue. Code existence is not treated as proof of full rollout.
In validation -
Voice learning and automated candidatesIn development
Observation and manual annotation continue. Automated candidates are not yet activated in production.
In development -
Multi-fleet and white-label expansionIn development
Multi-tenant isolation and onboarding a second fleet still require testing and field evidence.
In development
Field validation and limits
Completed, in validation, and not yet commercial are separated.
Telephony and the fleet back office have operating records; speech, addresses, dispatch, and end-to-end reconciliation remain under validation. None of these should be read as full automation or commercial rollout.
In validation
- Address and destination parsing
- End-to-end reconciliation from voice to order to dispatch
- Driver, passenger, and multi-fleet isolation
Not yet commercial
- Full-automation dispatch and large multi-fleet operations
- Production deployment of automated voice-learning candidates
- Public SLAs, recognition rates, and customer outcomes
Website build/static/browser tests validate website engineering only, not AnyTaxi technology. See the technical brief for full limits and evidence.
Concept architecture
Layered design so voice, orders, and dispatch can be validated separately.
Voice processing and the operations core are separated by clear interfaces, so human review, testing, and future replacement do not require rewriting the whole system. Deployment details and sensitive information are not disclosed publicly.
- Call audio pre-processing and speech-to-text
- Spoken address variants and field normalisation
- Human review for low-confidence information
- Decoupled order service and dispatch interface
- Access control and data minimisation
Voice entry
Inbound callVoice workflow
Voice processing
Speech-to-textIntent & field extraction
Operations core
Order serviceDispatch interfaceHuman review
Data & observability
Operations dataEvent logTest samples
Cross-cutting: access control · logging · monitoring · data minimisation
Commercialisation and cooperation
Fleet field cooperation and custom integration.
AnyTaxi remains at Pilot; pricing, revenue, customer count, and signed contracts are not published. The following distinguishes current activity from planned work.
Taxi fleets and transport operators
Phone orders depend on staff, addresses are re-keyed, and dispatch and operations data are fragmented.
Small-bus, rehabilitation, and care transport
Scheduling, mileage, fares, and subsidy reporting require heavy manual reconciliation.
Airport transfer and corporate charter
Bookings, dispatch, notifications, and reconciliation need a consistent data source.
Enterprises adopting AI automation and integration
Voice, documents, and existing systems lack traceable automation.
Fleet field cooperation and pilots
Validate AnyTaxi in a defined field with agreed metrics; customer names and field data are not published.
Custom software and system integration
Progress through discovery, milestones, and acceptance criteria; no fixed online quote.
Multi-fleet and white-label cooperation
Multi-tenant isolation, second-fleet onboarding, and white-label workflows still require testing and field evidence.
Technology and research partnership
Speech, address handling, dispatch integration, and AI governance are assessed with ownership and data boundaries.
Planned / R&D items are not realised revenue or live services.
Fleet cooperation process
Deployed in operations, expanding fleet cooperation.
AnyTaxi is deployed in fleet operations and continues to validate additional workflows with partners. Commercial pricing is not published. The best fit is an operations team with an existing phone order workflow, willing to define metrics and provide de-identified feedback.
Discuss fleet cooperationPartner names, logos, and customer data are not published without written permission.
- 01
Define pilot scope
Agree on order scenarios, participants, data boundaries, and success metrics.
- 02
Sample testing
Use de-identified call samples to check the voice and field extraction workflow.
- 03
Set up review
Define how low-confidence information is handled and where humans intervene.
- 04
Iterate from feedback
Adjust workflows, fields, and integrations based on real usage feedback.
Work with us
Turn phone orders into traceable operations data.
Fleet operators and enterprise partners are welcome to discuss a pilot or request publicly shareable product and R&D information.