From the Transportation edition of November 8, 2026
Berkshire transit board hears Spare's AI call-taker pitch, with a vendor-cited MBTA on-time jump from 88% to 95% unverified
Berkshire Regional Transit Authority (BRTA) / Spare Labs · Transit, paratransit and demand-response · Berkshire County, Massachusetts, United States
- Publisher
- iBerkshires
- Original publication
- November 3, 2026
- Source retrieved
- 2026-11-09
What happened
Spare Labs presented a demand-response and fixed-route platform to BRTA's board, including an AI phone agent for routine booking, cancellation and status requests. A Spare representative said MBTA paratransit on-time performance rose from 88 percent before Spare to 95 percent within 24 hours of launch. Board questions focused on rider data sales and protection; Spare said it does not sell rider data and that BRTA would control permissions, but was unsure about government data requests. BRTA is in a study with Spare and the regional planning commission, with implementation targeted by July.
Why it matters
Typical small-transit procurement scenario: vendor-led pitch with a headline performance claim, an AI call-taker, and board concern about rider data. Useful for agencies weighing AI phone agents in paratransit and demand response.
Evidence and measured results
The 88-to-95 percent figure is a verbal vendor claim reported by a local newspaper, with no baseline period, measurement method or independent verification. The AI call-taker has no BRTA performance data yet.
Limitations and uncertainty
Vendor statements relayed through a news article; no documents or contract reviewed. The MBTA figure is not agency-validated here. The article says a decision on fare payment for riders without smartphones is not made.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Small transit agencies need to improve paratransit scheduling and call handling with limited staff and board concern about data.
- Stakeholders
- Transit administrator
- Board members
- Dispatch supervisor
- Regional planning commission
- Discovery questions
- How was the vendor's on-time figure measured and over what period?
- Who owns and can export rider data?
- What happens when the AI agent cannot resolve a call?
- Value hypothesis
- A baseline-driven pilot can test whether AI call-taking reduces wait times; no gain is evidenced.
- Potential engagement
- Independent pilot design and vendor-claim validation before contract award.
- Unsupported claims
- 88-to-95 percent on-time gains at BRTA
- Cost savings
- Government-data-request handling
Pre-sales engineering
Role takeaway
- Fit
- Relevant to demand-response and paratransit operators evaluating AI call-taking and scheduling platforms.
- Architecture and integration
- Integrate scheduling platform with existing dispatch, vehicle and passenger-counting systems, with human escalation from the AI agent.
- Prerequisites
- Baseline on-time and call metrics
- Data export terms
- Accessible channel inventory
- Constraints
- Vendor claims unverified
- Rider without smartphone access
- Google traffic data dependency
- Security
- Confirm data ownership, permissioning, retention and handling of government data requests in writing.
- Proof of value
- Measure resolution and handoff rates
- Compare on-time performance to baseline
- Audit escalation logs
Delivery
Role takeaway
- Work
- Migrate data, integrate hardware, train staff and run a staged cutover with human dispatch retained.
- Dependencies
- Fare payment decision
- Data ownership terms
- Hardware integrations
- Ownership
- Transit operations director.
- Skills and adoption
- Role-based training for dispatchers, drivers and administrators.
- Governance checkpoints
- Contract data terms reviewed by counsel
- Pilot go/no-go on baseline metrics
- Monthly escalation log review
- Acceptance criteria
- On-time performance reported against agreed baseline
- AI-agent handoff rate within threshold
- All data export tests passed
- Risks
- Vendor claim not replicated
- Riders without smartphones underserved
- Data-sharing terms unclear
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Platform integrates passenger-counting hardware, real-time vehicle data, traffic-aware routing that could use Google traffic data, and an AI phone agent alongside human dispatch.
Governance
Who approves, reviews and stays accountable for outcomes?
Board asked about data sale, ownership and government access; the vendor's answer on law enforcement or government data requests was unresolved pending verification.
Security and privacy
What data, permissions and controls need testing?
Rider data ownership and permissions, and response to government data requests, were open questions; vendor says BRTA would own and permission its data.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Spare says it supports riders without smartphones through web booking and phone booking with a human dispatcher, and states ADA compliance; unverified.
Procurement
What should contracts, pricing and exit terms secure?
BRTA is in a study phase before procurement; the article gives no contract value or competitive process.
Operating model
Which teams own the service once it runs?
Vendor describes role-based training for dispatchers, drivers and admins and on-site implementation support, which implies significant change management.
Publication history
- 2026-11-08Transportation · Issue 116 resources
Stable resource ID: brta-spare-ai-call-taker-mbta-paratransit-otp-claim-2026-11-03