Agentic Index
Numa vs Toma (2026)
Both vendors last verified
Numa and Toma both sell AI agents to car dealerships through sales, with no public rates, so the choice rests on what each does. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Numa writes resolved requests back to the dealer management system, naming CDK, Reynolds, Dealertrack, Tekion and Xtime, and adds a Smart Inbox, LiveCSI tracking of customer satisfaction and separate agents for service advisors, heat cases and opportunities, and it counts more than 1,300 dealership locations. Toma answers every call, works leads and books service directly in Xtime and other dealer systems, routes frustrated or keyword triggered calls to staff, and learns store policies through Toma IQ, which managers approve. Numa gives managers a transcript and task record for every handled call, and Toma reviews every call for recurring edge cases and holds a SOC 2 Type II report. Choose Numa for DMS write back and packaged agents. Choose Toma for manager approved learning and an audited security posture.
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Numa and Toma are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,084 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Numa if
- Resolved requests must write back to your DMS, whether CDK, Reynolds, Dealertrack, Tekion or Xtime.
- Satisfaction monitoring and a shared inbox for calls and texts are part of how you run service.
- Named agents for service advisors, heat cases and sales opportunities match your workflows.
Choose Toma if
- Store policies the agent learns should go live only after a manager approves them.
- Frustrated or keyword triggered calls must route to staff automatically.
- SOC 2 Type II and ISO 27001 certification are on your vendor checklist.
| Feature | N Numa |
T Toma |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
NumaIntegrations & Tool Calling Voice AI connects to the DMS in real time, resolves the caller's request and writes it back to the DMS, booking appointments into open service bays without double booking and giving repair order status, with integrations covering CDK, Reynolds, Dealertrack, Tekion and Xtime and 90% DMS coverage across the industry by Numa's count. It also connects to the dealership's CRM and scheduler. SourceNuma, numa.com and /blog/ai-voice-agents-dealerships-buyers-guideread 2026-10-06 |
||
|
TomaIntegrations & Tool Calling The agent books service appointments directly in Xtime, joined as a partner in the dealer's Xtime configuration. It sees exactly the availability of the dealer's web scheduler, cannot exceed the shop and advisor capacity set there, and books by VIN when it can. Toma also integrates with Affinitiv, CDK, Dealer-FX, myKaarma, PBS, Tekion, Total Customer Connect and Homenet. SourceToma, kb.toma.com/how-to-integrate-toma-with-xtime and kb.toma.comread 2026-10-06 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
NumaWorkflow Orchestration Voice AI runs each call from context lookup to booking and DMS write back, and when a customer hangs up Numa can send a text offering help, then follow up with a call if the text gets no answer. Separate agents draft advisor replies, rescue heat cases and surface declined work. These are the product's own flows, set up by Numa's team, and Numa describes no branching, workflow builder or coordination between agents that the dealership configures. SourceNuma, numa.com and /casestudies/team-gillman-uses-ai-agents-to-increase-revenue-reduce-headcount-and-boost-csiread 2026-10-06 |
||
|
TomaWorkflow Orchestration Each call runs the agent's own flow, answering, booking service and routing to staff, with transfer triggers on frustration or keywords, follow up alerts and transfer clawback as safeguards, and reminder calls turn a likely cancellation into a rescheduled visit on the same call. Toma names no branching workflow builder or multi agent routing that the dealership operates. SourceToma, toma.com/blog/a-new-chapter-for-toma and /blog/save-service-revenue-with-appointment-remindersread 2026-10-06 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
NumaTriggers & Channel Coverage Voice AI answers inbound calls and texts and recovers missed calls, and Numa can start outbound calls for appointment reminders, declined service follow up and recall notices without staff starting them. One store sent 31,389 outbound messages in 13 weeks and rescues 78.5% of callers who would otherwise reach voicemail. SourceNuma, numa.com/blog/ai-voice-agents-dealerships-buyers-guide and /casestudies/mike-rezi-nissan-atlanta-turns-voicemail-problem-into-complete-visibilityread 2026-10-06 |
||
|
TomaTriggers & Channel Coverage The agent answers every inbound call and works leads, and reminder calls go out on schedules the dealer configures for all appointments or specific service types, to customers who have opted in, with calls, voicemails and texts in one inbox. Neither kind of call needs a staff member to start it. SourceToma, toma.com/ai-agents-for-dealerships, /blog/save-service-revenue-with-appointment-reminders and /blog/a-new-chapter-for-toma; toma.com/blog/save-service-revenue-with-appointment-remindersread 2026-10-06 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
NumaKnowledge Grounding & RAG Numa pulls full customer, vehicle and repair order context from the DMS into every call and text, with real time sentiment. Docs, the CRM and the help center are named as sources, but Numa describes no index or retrieval over them. The context is gathered for each conversation. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaKnowledge Grounding & RAG Toma IQ reviews every call for patterns and drafts policy recommendations, and once a manager approves them they join the My Policies hub, the library of every policy the AI coworker operates under, organized by topic such as loaner policy, after hours handling, recall escalation and transfer rules. Admins open it under Team Settings, can also write a policy directly and apply it to the AI coworker, and can remove or revert any policy at any time, with full version history and every change logged. Toma does not say how the agent retrieves from that library or whether dealers can upload their own documents. SourceToma, toma.com/blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operatesread 2026-10-06 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
NumaMemory & State Persistence The customer history Numa surfaces comes from the DMS and the Smart Inbox's conversation record, which hold the dealership's business record. Numa describes no memory the agent keeps with its own scope and lifetime. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaMemory & State Persistence The library Toma IQ builds holds dealership policies that guide the agent. Toma does not say whether the agent keeps any memory of individual customers or conversations. SourceToma, toma.com/blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operatesread 2026-10-06 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
NumaHuman Oversight & Guardrails Voice AI recognizes when a call needs a person and hands the receiving representative the full conversation transcript and relevant customer information, Numa flags threads that need a human to follow up, and staff work the same Smart Inbox as the AI. At one store the team answered 93.8% of flagged threads. Numa names no step where an advisor approves an agent action or reply before it goes out. SourceNuma, numa.com/blog/ai-voice-agents-dealerships-buyers-guide and /casestudies/mike-rezi-nissan-atlanta-turns-voicemail-problem-into-complete-visibilityread 2026-10-06 |
||
|
TomaHuman Oversight & Guardrails Safeguards route calls to staff on detected frustration or chosen keywords, flag conversations for human follow up with context and reclaim unanswered transfers so callers are not left waiting. Managers must approve any policy change Toma IQ proposes to the agent's configuration, accepting or rejecting it in one click. Toma names no step where staff approve an agent action on a call before it goes through. SourceToma, toma.com/blog/a-new-chapter-for-toma and /blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operatesread 2026-10-06 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
NumaSecurity, Identity & Governance No security or trust page is published, and the only published policies are the terms and the privacy policy. Numa names no attestation, SSO, roles or permissions for the inbox or the mobile app. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaSecurity, Identity & Governance Toma reports SOC 2 Type II compliance with zero exceptions on its most recent independent audit. The report is available during evaluation and on request at trust.toma.com. Toma has also announced ISO 27001 and PCI DSS certification. It names no SSO, roles or permissions for dealership users. SourceToma, toma.com/blog/soc-2-type-ii-compliance-dealer-group-automotive-airead 2026-10-06 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
NumaObservability & Auditability Every handled call produces a full transcript and a task record, and a manager dashboard reports call volume, escalation rate and AI success rate by location beside real time CSI monitoring. Each team member gets a Numa number for calls and texts, so every customer conversation is kept in one record instead of across the CRM, scheduler, chat and call tracking. SourceNuma, numa.com/blog/ai-voice-agents-dealerships-buyers-guide and /casestudies/mike-rezi-nissan-atlanta-turns-voicemail-problem-into-complete-visibilityread 2026-10-06 |
||
|
TomaObservability & Auditability The Inbox shows every call, voicemail and text in one queue with transcripts, summaries, recordings and sentiment, where teams triage and assign requests with full conversation context. Every Toma IQ policy change is logged with version history. Toma does not say whether teams can see the actions the agent took within a call. SourceToma, toma.com/blog/a-new-chapter-for-toma and /blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operatesread 2026-10-06 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
NumaDeployment & Data Residency Delivery is hosted, with a web inbox and a mobile app. Numa's team sets it up in two to three weeks, and most teams are proficient within 90 days. Numa names no region, choice of region, or dedicated or customer hosted option. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaDeployment & Data Residency The product is a hosted service run from the dealer's Toma account. No hosting region is published, and Toma names no region choice or dedicated or customer hosted option. SourceToma, toma.com/blog/soc-2-type-ii-compliance-dealer-group-automotive-ai and /ai-agents-for-dealershipsread 2026-10-06 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
NumaPrebuilt Agents, Templates & Packs Named agents with separate jobs ship beside Voice AI. A Service Advisor Agent writes replies, surfaces the full history and chases follow ups, a Heat Case Agent rescues deals going sideways, an Opportunity Agent surfaces and books declined and unsold work, and an AI Appointment Agent engages customers and books service. Case studies name dealers such as Courtesy Auto, Willis Automotive, Norm Reeves, Team Gillman and Mike Rezi Nissan Atlanta. SourceNuma, numa.com, /casestudies and /casestudies/mike-rezi-nissan-atlanta-turns-voicemail-problem-into-complete-visibilityread 2026-10-06 |
||
|
TomaPrebuilt Agents, Templates & Packs Toma deploys one AI coworker personalized to each dealership that answers every call, books service and routes to the team with safeguards specific to the dealer, and publishes no named packaged agents or templates. Toma says its agents have automated more than a million customer calls since launch. SourceToma, toma.com/ai-agents-for-dealerships and /blog/a-new-chapter-for-tomaread 2026-10-06 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
NumaModel Flexibility & Routing The models behind the agents are not published, and no model choice is offered. Numa describes the AI by what it does, such as reading full history and real time sentiment, not by what it runs on. SourceNuma, numa.com and /blog/ai-voice-agents-dealerships-buyers-guideread 2026-10-06 |
||
|
TomaModel Flexibility & Routing No model provider is named, and Toma does not say whether customers can choose a model. Toma IQ adapts the agent to each store through approved policies. SourceToma, toma.com/blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operates and /ai-agents-for-dealershipsread 2026-10-06 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
NumaAPIs, SDKs & MCP Extensibility No API, SDK, developer documentation or MCP server for calling Numa is published. Integrations run from Numa into the dealership's DMS, CRM and scheduler. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaAPIs, SDKs & MCP Extensibility The help center covers getting started, general use and integrations into dealer systems. No API, SDK or MCP server for calling Toma is published. Dealers connect Toma to Xtime by entering a partner invitation code, not through an API of Toma's own. SourceToma, kb.toma.com and /how-to-integrate-toma-with-xtimeread 2026-10-06 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
NumaTesting, Debugging & Optimization LiveCSI scores customer satisfaction across the dealership's conversations and an AI success rate is reported by location. Numa describes no test, scoring of agent changes or experiment surface. Its own figures include response time cut from 23 hours to under 10 minutes, an appointment booking rate above 80%, 70% of heat cases resolved and repair order dollars per advisor up by more than 35%. SourceNuma, numa.com and /blog/ai-voice-agents-dealerships-buyers-guideread 2026-10-06 |
||
|
TomaTesting, Debugging & Optimization Toma IQ reviews every call for scenarios where a human intervened, edge cases that recur and responses that consistently produced a better outcome, then drafts changes that managers accept or reject in one click, with every change logged and reversible. That loop improves the deployed agent. Toma names no test harness for checking the agent before release. SourceToma, toma.com/blog/toma-iq-the-ai-that-actually-learns-how-your-dealership-operatesread 2026-10-06 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
NumaBrowser & Computer Use Dealer systems are reached through DMS, CRM and scheduler integrations. Numa describes no browser, desktop or computer control. SourceNuma, numa.comread 2026-10-06 |
||
|
TomaBrowser & Computer Use Dealer systems are reached through partner integrations such as Xtime, where Toma reads the web scheduler's availability. Toma names no browser, desktop or computer control. SourceToma, kb.toma.com/how-to-integrate-toma-with-xtimeread 2026-10-06 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | N Numa |
T Toma |
|---|---|---|
|
Entry price Lowest public entry point |
Contact sales | Contact sales |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
not captured | not captured |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tier
|
|
Buying motion Self-serve vs sales call |
Sales call | Sales call |
|
Pricing verified When this pricing was last checked |
More comparisons with Numa or Toma
Other matchups in voice agents
Not the pairing you were after? These compare a different set of voice agents on the same 14 capabilities.