Tekion (vendor source) · Service voice AI

Toma AI phone assistant

Toma

Checked 2026-10-16 · reviewed · Public-source desk review

Marketplace or vendor integration claims do not establish customer authorization, exact endpoint access, fees or deployed performance. Recommendations below are editorial hypotheses.

Workflow and value hypothesis
Phone-driven appointment booking. Value hypothesis: reduce missed service requests without losing intent or overpromising.
Buyer and operating owner
Service BDC and service manager
Platform compatibility evidence
Vendor setup guide describes Toma in ARC Integration Hub and a dealer-requested connection. No dealer account was inspected.
Read/write and API depth
The guide describes reviewing data permissions during connection; those exact permissions are not publicly enumerated.
Public pricing
Unknown: no platform-specific dealer or connector price verified.
Competition, overlap and possible gaps
Compare Numa/STELLA and native service workflows. A setup guide is more concrete than a logo, but still does not prove operational fit.
Adoption evidence and limits
Marketing setup-time and uplift claims are not treated as measured results. No connection, account or authorization was used.
Next research step
Before activation, independently confirm the requested permission scope; then test rescheduling, cancellation, duplicates and human escalation in a bounded trial.

Evidence and sources

  1. Toma product/integration evidence — Vendor setup guide describes Toma in ARC Integration Hub and a dealer-requested connection. No dealer account was inspected.

Back to all records · Business-model and pilot primer

Provided as is, for information only, with no warranty and no liability. Not legal or professional advice. Security and radio material is for authorized, lawful use only. Full disclaimer.

Visits are logged on our own server: IP address, browser and device details, and pages viewed. We use them to understand traffic and spot attacks, and never share or sell them.