The Greater Dayton Regional Transit Authority has selected ConnXAI to deploy the vendor's Maestro Unified Customer Communications Platform across the agency's transit network in Ohio, consolidating rider messaging, operations data and front-line coordination into a single orchestration layer.

Neither party disclosed financial terms, contract length, or a deployment schedule.

What does the platform connect?

Maestro functions as a shared intelligence layer that ties back-end transportation operations to customer-facing channels. GDRTA's deployment will span ten distribution points:

• mobile applications
• agency websites
• SMS
• push notifications
• email
• transit-center signage
• onboard displays
• public-address systems
• third-party applications
• GTFS and Open Data feeds

The platform extends the agency's existing technology stack rather than replacing it, consistent with the vendor's pitch to help agencies operationalize prior investments.

Who is on each side?

GDRTA, the public transit operator serving the Dayton region, is the buyer. ConnXAI, the platform vendor, is supplying Maestro. Both parties announced the selection jointly.

What are the parties saying?

ConnXAI Chief Client Officer Steve Pitchon tied the selection to consolidation. "GDRTA's selection of ConnXAI demonstrates a forward-looking approach that connects and extends the systems already in place," Pitchon said. "Maestro helps transform fragmented operational information into coordinated, measurable customer communications."

GDRTA Director of Mobility and Customer Service Sally Brown framed the platform as an internal-coordination tool as much as a rider-facing one. The system "gives our teams a single source of truth, helping us work smarter and stay better coordinated across operations, maintenance, safety and scheduling," Brown said.

The platform also "strengthens our communications foundation and supports our commitment to delivering a more efficient and predictable experience for our passengers," she added.

ConnXAI Chief Executive Officer Indrajit Ghosh described the vendor's market position in broader terms. "We help transportation agencies operationalize their existing technology investments and convert fragmented systems and data into actionable outcomes," Ghosh said. For GDRTA, he added, the deployment targets "better operational awareness, greater predictability and an enhanced rider and workforce experience."

What changes for riders and staff?

The vendor's stated outcomes — operational awareness, service predictability, and rider plus workforce experience — are framed as measurable rather than aspirational. GDRTA's own description emphasizes coordination across operations, maintenance, safety and scheduling, four functions that today rely on separate data sources. Bringing those onto a common orchestration layer should shorten the gap between a service disruption and the rider notification that follows.

The platform's GTFS and Open Data feeds will let third-party applications ingest the same schedule and service-alert information GDRTA distributes directly, narrowing the data gap that often appears in third-party apps during incidents.

What comes next?

GDRTA has not disclosed a contract value, a phased rollout schedule, or an expected go-live date. Both parties describe the engagement as an extension of existing systems rather than a replacement, which points to first cutovers on the customer-facing side before the platform reaches deeper into back-office functions.