{ "checked_at": "2026-10-16", "coverage": { "published_records": 20, "reviewed_records": 20, "official_catalogs_imported": 0, "current_live_integrations_verified": 0, "exhaustive": false, "limits": "20 original desk reviews: nine Fortellis/CDK-related product assessments, one explicitly outside-filter CDK comparator and ten Tekion-related vendor assessments. Neither official catalog is reproduced. Full eligible-catalog denominators and percentage completion are not established for this publication. All compatibility claims are source-reported; no live integration was verified. Review depth varies, including partial module evidence and schema-only relationship evidence.", "platforms": [ { "name": "Fortellis / CDK Drive", "summary": "Nine targeted vendor-source assessments plus one outside-filter comparator. No bulk catalog import. Current filtered membership is not asserted for every reviewed product.", "source_url": "https://marketplace.fortellis.io/?Int=CDK+Drive" }, { "name": "Tekion", "summary": "Ten vendor-source assessments; no directory records, Live/InProgress statuses or tiers imported. These do not establish current official marketplace availability.", "source_url": "https://tekion.com/technology-partners" } ] }, "products": [ { "id": "xtime-cdk", "name": "Xtime Enhanced Repair Order Integration", "vendor": "Xtime", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Repair-order workflow", "workflow": "Service staff work on repair orders in Xtime with changes passed into CDK. Value hypothesis: less repeated entry and fewer conflicting versions.", "buyer": "Fixed-operations director and service manager", "compatibility": "Vendor updates describe enhanced CDK DMS integration and automatic flow of Xtime work into CDK; the integration directory lists CDK Global.", "access": "RO change flow is vendor-described. Exact create/update operations, fields, permissions and dealer activation remain unverified.", "pricing": "Unknown: no current generally applicable quote verified. Historical OEM brochures are not universal current prices.", "overlap": "Compare Dealerlogix and native CDK service workflows. Evaluate the whole RO lifecycle, not an integration label.", "evidence_limits": "Vendor evidence supports the CDK family; installed-version compatibility and production performance were not tested.", "next_step": "Confirm parts/labor overrides and supported operations, then test reconciliation after failed writes and concurrent edits.", "sources": [ { "url": "https://xtime.com/client-resource-center/product-news-updates/", "title": "Xtime product evidence", "claim": "Vendor updates describe enhanced CDK DMS integration and automatic flow of Xtime work into CDK; the integration directory lists CDK Global." }, { "url": "https://xtime.com/integrations/", "title": "Xtime supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "stella-cdk", "name": "STELLA Service", "vendor": "STELLA Automotive AI", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Service voice AI", "workflow": "Handle inbound service calls and scheduler bookings. Value hypothesis: recover missed or after-hours requests with reliable staff handoff.", "buyer": "Service BDC manager and fixed-operations director", "compatibility": "Product page describes scheduler booking; vendor FAQ names CDK Global. Exact CDK Drive versus CDK Service path needs confirmation.", "access": "Direct booking/updates are product claims; endpoint-level CDK access and cancel/change support are unverified.", "pricing": "Vendor FAQ describes setup fee plus monthly subscription; no amount verified, quote required.", "overlap": "Compare CDK AIVA, Numa and Toma. Count completed eligible appointments and successful escalation, not merely calls answered.", "evidence_limits": "No live connection, independent certification audit or measured uplift. Do not assume vendor-level compatibility applies to every module.", "next_step": "Verify capacity rules, outage fallback, booking changes and the precise CDK integration path before a bounded trial.", "sources": [ { "url": "https://stellaautomotive.com/stella-service/", "title": "STELLA Automotive AI product evidence", "claim": "Product page describes scheduler booking; vendor FAQ names CDK Global. Exact CDK Drive versus CDK Service path needs confirmation." }, { "url": "https://stellaautomotive.com/resources/frequently-asked-questions/", "title": "STELLA Automotive AI supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "goto-cdk", "name": "GoTo Connect - DMS", "vendor": "GoTo Connect", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Telephony and SMS", "workflow": "Combine dealership communications with customer/service context. Value hypothesis: reduce manual context lookup and communication fragmentation.", "buyer": "BDC manager and IT/telephony leader", "compatibility": "Official vendor release-community announcement explicitly names CDK Drive among integrations.", "access": "CDK Drive integration is named; its field-level features, sync direction and refresh interval are unverified.", "pricing": "Unknown: no current numeric connector price verified.", "overlap": "Compare native communications and CallRevu analytics. A DMS connector and a CRM connector may expose different features.", "evidence_limits": "Vendor announcement does not establish dealership activation, number migration feasibility or current permissions.", "next_step": "Map required fields, reminder behavior, per-location charges and number migration before comparing total delivery cost.", "sources": [ { "url": "https://community.goto.com/discussion/325726/whats-new-with-goto-connect-march", "title": "GoTo Connect product evidence", "claim": "Official vendor release-community announcement explicitly names CDK Drive among integrations." }, { "url": "https://www.goto.com/blog/goto-connect-for-automotive", "title": "GoTo Connect supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "aiva-cdk", "name": "AIVA for Fixed Operations Suite", "vendor": "CDK Global", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Service voice AI", "workflow": "Conversational service scheduling with capacity settings and staff transfers. Value hypothesis: use an existing suite capability before adding another assistant.", "buyer": "CDK fixed-operations customer and service manager", "compatibility": "CDK product page describes native scheduler integration and inclusion in Fixed Operations Suite.", "access": "Scheduler integration is vendor-supported; this grants no independent CDK Drive API access. Exact endpoint permissions were not tested.", "pricing": "Vendor says included in Fixed Operations Suite. Suite price, included usage, overages and contract eligibility remain unverified.", "overlap": "Compare STELLA and other booking agents against the capability already purchased. Duplicate functionality can erase the business case.", "evidence_limits": "No operational or language-coverage test; inclusion is not a zero-total-cost claim.", "next_step": "Confirm included usage and appointment types, then test capacity exceptions, transfers and unsupported requests.", "sources": [ { "url": "https://www.cdkglobal.com/aiva-fixed-operations", "title": "CDK Global product evidence", "claim": "CDK product page describes native scheduler integration and inclusion in Fixed Operations Suite." }, { "url": "https://www2.cdkglobal.com/fixedops-updates", "title": "CDK Global supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "bmw-cdk", "name": "BMW Connected Vehicle", "vendor": "CDK Global", "platform": "Fortellis / CDK Drive (vendor source)", "category": "OEM service information", "workflow": "Use connected-vehicle information during service preparation and write-up. Value hypothesis: reduce separate OEM lookups while preserving provenance.", "buyer": "BMW franchise service manager and advisors", "compatibility": "CDK BMW page describes Connected Vehicle / Vehicle Query via BMW SPARQ for recalls, campaigns, coverage and history.", "access": "Information lookup is described; exact API schema, dealer eligibility and package mapping are unverified.", "pricing": "Unknown: no current numeric price verified.", "overlap": "Compare existing OEM portal lookup. The potential advantage depends on eligible vehicles and timely data, not generic access to all BMW information.", "evidence_limits": "Exact marketplace-package mapping and current VIN coverage were not independently established. No vehicle query was executed.", "next_step": "Verify franchise eligibility, supported VINs, freshness and exceptions; compare lookup accuracy and time on authorized representative cases.", "sources": [ { "url": "https://www.cdkglobal.com/oem-integrations/bmw", "title": "CDK Global product evidence", "claim": "CDK BMW page describes Connected Vehicle / Vehicle Query via BMW SPARQ for recalls, campaigns, coverage and history." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "revolutionparts-cdk", "name": "RevolutionParts CDK DMS Integration", "vendor": "RevolutionParts", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Parts commerce", "workflow": "Parts inventory and online-order coordination is the workflow to assess. Value hypothesis: less duplicate entry and fewer stock mismatches; exact synchronization behavior still needs verification.", "buyer": "Parts director and parts ecommerce manager", "compatibility": "Vendor OEM plans list a Fortellis DMS integration add-on. The exact CDK configuration and activation scope remain to be established.", "access": "Two-way inventory/order synchronization was reported in research, but the support article returned HTTP 401 during final verification. Treat read/write direction and fields as unverified pending accessible documentation.", "pricing": "OEM plans vary and integration is an eligible add-on; no universally applicable current quote established. Confirm billing start and setup costs.", "overlap": "Compare authorized batch imports and native order entry. Gross online sales alone conceal fulfillment and return costs.", "evidence_limits": "No production sync or dealer entitlement verified. The inaccessible support article is not used as confirmed capability evidence; current public evidence establishes an integration add-on, not endpoint detail.", "next_step": "Test inventory lag, cancellations, returns, multiple warehouses and failed-write reconciliation before accepting a quote.", "sources": [ { "url": "https://www.revolutionparts.com/oem-plans/", "title": "RevolutionParts OEM plans", "claim": "Vendor plan page lists a Fortellis DMS integration add-on; exact operation scope remains unknown." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "dealerlogix-cdk", "name": "Dealerlogix Create and Update RO — comparator", "vendor": "Dealerlogix", "platform": "CDK comparator (vendor source)", "category": "Repair-order workflow", "workflow": "Coordinate service write-up, approvals and parts handling. Value hypothesis: consolidate operational handoffs and reduce duplicate edits.", "buyer": "Service manager and fixed-operations director", "compatibility": "Outside the requested filtered snapshot: included only as a vendor-sourced comparator. Vendor pages name CDK integration; exact listing-to-product mapping remains uncertain.", "access": "Generic parts-writeback documentation describes DMS updates, but CDK-specific create/update/parts scope is not established.", "pricing": "Vendor says cost varies with advisor count and DMS/OEM integrations; no fixed price verified.", "overlap": "Compare Xtime and the native suite on full lifecycle support. Do not count this as a verified product in the CDK Drive filter.", "evidence_limits": "Vendor certification is a claim, not an independently audited scope. Current listing eligibility and functional compatibility remain unverified.", "next_step": "Confirm each required operation specifically for CDK, licensing, and reconciliation after failures before a trial.", "sources": [ { "url": "https://dealerlogix.com/pricing/", "title": "Dealerlogix product evidence", "claim": "Outside the requested filtered snapshot: included only as a vendor-sourced comparator. Vendor pages name CDK integration; exact listing-to-product mapping remains uncertain." }, { "url": "https://faq.dealerlogix.com/article/6-what-dms-providers-is-dealerlogix-integrated-with", "title": "Dealerlogix supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." }, { "url": "https://faq.dealerlogix.com/article/415-parts-writeback-faq", "title": "Dealerlogix parts-writeback FAQ", "claim": "General writeback description; CDK-specific support still requires confirmation." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "autotext-cdk", "name": "AutoText - Denied Work Module — partial evidence", "vendor": "VenueVision", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Customer messaging", "workflow": "Base autoTEXT supports two-way messaging and DMS-triggered updates. Potential denied-work follow-up is a research question, not a verified add-on capability.", "buyer": "Service manager and customer-retention lead", "compatibility": "Vendor sources support base autoTEXT and a CDK relationship; the specific denied-work module is only partially corroborated.", "access": "Vendor describes customer, appointment and RO-status data integration. Denied-work capture, automation and write-back are not established.", "pricing": "Unknown: no current numeric price or separate module fee verified.", "overlap": "Compare native follow-up and advisor queues. Vendor competitor comparisons are not treated as independent facts.", "evidence_limits": "Base-product evidence must not be substituted for module-specific proof. No follow-up automation, consent controls or production integration tested.", "next_step": "Find permissible module-specific evidence, then verify consent, opt-outs, follow-up timing and incremental completed work before evaluating purchase.", "sources": [ { "url": "https://www3.venuevision.com/autotext/", "title": "VenueVision product evidence", "claim": "Vendor sources support base autoTEXT and a CDK relationship; the specific denied-work module is only partially corroborated." }, { "url": "https://www3.venuevision.com/venuevision-vs-fleetlane/", "title": "VenueVision supporting integration evidence", "claim": "Supporting vendor description; not a functional or certification audit." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "kimoby-cdk", "name": "Kimoby Pay CDK Integration", "vendor": "Kimoby", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Payment reconciliation", "workflow": "Post successful payments to the matching CDK repair order while staff retain final closure. Value hypothesis: reduce cashier reconciliation errors and manual entry.", "buyer": "Service cashier, controller and fixed-operations director", "compatibility": "Vendor documents CDK payment writeback, tender mapping and paid-status updates.", "access": "Payment posting is not RO closure or repair-line writeback. An August 4, 2026 vendor article says repair-line writeback is still in development.", "pricing": "Vendor states payment-writeback integration is free for existing Kimoby Pay users on CDK. Kimoby Pay and payment processing are not established as free.", "overlap": "Compare existing payment posting and reconciliation. Evaluate exception queues and reversals rather than accepting a broad two-way integration label.", "evidence_limits": "No payment, production posting or dealer activation was performed. Fees, eligibility and production recovery behavior remain unverified.", "next_step": "Verify failed-posting queues, refunds/reversals, duplicate prevention, tender mapping and audit evidence before a controlled trial.", "sources": [ { "url": "https://www.kimoby.com/products/payment-cdk-writeback", "title": "Kimoby product evidence", "claim": "Vendor documents CDK payment writeback, tender mapping and paid-status updates." }, { "url": "https://www.kimoby.com/blog/kimoby-cdk-integration", "title": "Kimoby CDK integration explanation", "claim": "August 4, 2026 distinction between payment posting and repair-line writeback." }, { "url": "https://help.kimoby.com/fortellis-automatic-payment-settling", "title": "Kimoby automatic payment settling documentation", "claim": "Vendor setup and settlement description; no activation performed." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "curbee-cdk", "name": "Curbee", "vendor": "Curbee", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Mobile service", "workflow": "Coordinate mobile-service bookings, routes, technician work and customer updates. Value hypothesis: improve route density and first-visit completion.", "buyer": "Mobile-service manager and fixed-operations director", "compatibility": "Vendor M.A.R.S. platform page names native CDK integration.", "access": "The page describes booking, routing and technician workflows, but does not establish precise CDK Drive read/write operations.", "pricing": "Unknown: an illustrative ROI-calculator cost input is not a binding quote.", "overlap": "Compare current dispatch tools and native scheduling. Mobile routing, travel time and van capacity can matter more than appointment volume.", "evidence_limits": "No endpoint test, offline workflow assessment or independent productivity measurement. Vendor ROI assumptions are not customer results.", "next_step": "Clarify supported CDK records, service-area constraints, offline behavior, dispatch exceptions and van-level pricing before testing route economics.", "sources": [ { "url": "https://www.curbee.com/platform", "title": "Curbee product evidence", "claim": "Vendor M.A.R.S. platform page names native CDK integration." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "numa-tekion", "name": "AI Appointment Agent / service operations", "vendor": "Numa", "platform": "Tekion (vendor source)", "category": "Service scheduling", "workflow": "Identify callers, consult customer/service context and book appointments. Value hypothesis: fewer abandoned requests without overbooking.", "buyer": "Fixed-operations director and service BDC", "compatibility": "Vendor guide names Tekion and describes native scheduling/cloud DMS connectivity.", "access": "Vendor describes customer/appointment reads and end-to-end booking; endpoint schemas and dealer permissions remain unverified.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare with STELLA, Toma and the native scheduler. A gap would be reliable handling of complex service constraints, not simply answering calls.", "evidence_limits": "No deployment test, price or permission scope verified. The source expands APC incorrectly; that expansion is not relied upon.", "next_step": "With authorization, test unavailable slots, duplicate callers, parts prerequisites and staff handoff; measure completed eligible ROs and correction time.", "sources": [ { "url": "https://numa.com/blog/numa-dealership-integrations-dms-schedulers-crm-guide", "title": "Numa product/integration evidence", "claim": "Vendor guide names Tekion and describes native scheduling/cloud DMS connectivity." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "goto-tekion", "name": "GoTo Connect", "vendor": "GoTo", "platform": "Tekion (vendor source)", "category": "Telephony and SMS", "workflow": "Call or text from customer and lead context in ARC. Value hypothesis: less manual dialing and fewer disconnected communication histories.", "buyer": "BDC, sales and service managers", "compatibility": "Dedicated vendor integration page describes ARC calling/texting and configurable account modes.", "access": "Vendor describes calls/SMS initiated within ARC. Full calling/texting and managed text-only configurations differ; exact field rights are unknown.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare with CallRevu for call analysis and native ARC communication. Test whether the actual gap is routing, logging completeness or conversation quality.", "evidence_limits": "Country availability, retention, recording permissions and dealership enablement not verified. Product claims are not independent performance evidence.", "next_step": "Document the intended account mode and retention requirements, then test identity matching, staff transfer and duplicate message prevention in an authorized trial.", "sources": [ { "url": "https://www.goto.com/integrations/tekion", "title": "GoTo product/integration evidence", "claim": "Dedicated vendor integration page describes ARC calling/texting and configurable account modes." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "callrevu-tekion", "name": "CallRevu CRM integration", "vendor": "CallRevu", "platform": "Tekion (vendor source)", "category": "Conversation intelligence", "workflow": "Use call outcomes and appointment activity in dealership tools. Value hypothesis: fewer missed follow-ups and better management visibility.", "buyer": "BDC and fixed-operations managers", "compatibility": "Vendor integration roster names Tekion. This is roster evidence, not a product-specific API specification.", "access": "The page describes general call/lead/appointment data delivery; Tekion-specific writes are not established.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Overlaps GoTo communication logging and native CRM reports. Distinguish analytics from actionable closed-loop follow-up.", "evidence_limits": "Do not transfer every platform-wide capability to Tekion. Certification scope, adoption, customer permissions and measured benefit remain unknown.", "next_step": "Identify the exact Tekion module and event/field mapping from permissible documentation before designing an outcome test.", "sources": [ { "url": "https://www.callrevu.com/partnerships/", "title": "CallRevu product/integration evidence", "claim": "Vendor integration roster names Tekion. This is roster evidence, not a product-specific API specification." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "uveye-tekion", "name": "UVeye inspection integration", "vendor": "UVeye", "platform": "Tekion (vendor source)", "category": "Vehicle inspection", "workflow": "Bring scan evidence into advisor and customer workflows. Value hypothesis: clearer findings with less manual report handling.", "buyer": "Service director and service advisors", "compatibility": "Dedicated vendor page describes inspection reports within ARC repair orders.", "access": "Vendor says scan results enter repair orders and can be shared through the consumer portal. Reverse direction and field schemas are unspecified.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Overlaps manual inspections and existing inspection-report tools. Explore evidence quality and advisor adoption, not a claim that scans replace technician judgment.", "evidence_limits": "Vendor describes authorization and coordinated activation. No hardware fit, fee, integration activation or accuracy test was verified.", "next_step": "Evaluate false findings, report-to-vehicle matching, latency and human sign-off on a representative authorized vehicle sample.", "sources": [ { "url": "https://uveye.com/integration/tekion/", "title": "UVeye product/integration evidence", "claim": "Dedicated vendor page describes inspection reports within ARC repair orders." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "sharebox-tekion", "name": "Key Lounge / self-service kiosks", "vendor": "Sharebox", "platform": "Tekion (vendor source)", "category": "Key handover", "workflow": "After-hours key drop-off and collection. Value hypothesis: convenient handover without weakening custody or identity checks.", "buyer": "Service manager and fixed-operations director", "compatibility": "Vendor product landing page names Tekion integration.", "access": "Physical handover is described; API objects, read/write directions and notification payloads are unknown.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare staffed key handover and other lockers. The differentiator must include safe exception handling and auditable custody, not only unattended hours.", "evidence_limits": "Hardware prerequisites, per-dealer terms and rollout details not established. No independent reliability or adoption result reviewed.", "next_step": "Map lost-code, wrong-key, power/network failure and disputed-collection cases before an authorized site trial.", "sources": [ { "url": "https://sharebox.global/int/key-lounge/", "title": "Sharebox product/integration evidence", "claim": "Vendor product landing page names Tekion integration." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "lyft-tekion", "name": "Lyft Concierge service transportation", "vendor": "Lyft Business", "platform": "Tekion (vendor source)", "category": "Customer transportation", "workflow": "Request service-customer rides from a dealership workflow or customer link. Value hypothesis: reduce advisor coordination burden while controlling transportation spend.", "buyer": "Service director and service advisors", "compatibility": "Vendor customer case study describes an ARC/APC ride-request workflow introduced in 2022.", "access": "Ride creation is described; exact fields and reverse status writes are unspecified.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare shuttle, loaner and existing ride coordination. Analyze completed rides and guest experience against total transportation cost.", "evidence_limits": "One historical customer story is not current universal availability or causal evidence. Per-ride charges and integration fees are unknown.", "next_step": "Verify current availability for the intended market, then test cancellation, duplicate rides, accessibility needs and spending limits with authorization.", "sources": [ { "url": "https://www.lyft.com/business/customer-stories/walser-buick", "title": "Lyft Business product/integration evidence", "claim": "Vendor customer case study describes an ARC/APC ride-request workflow introduced in 2022." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "stella-tekion", "name": "STELLA service agents", "vendor": "STELLA Automotive AI", "platform": "Tekion (vendor source)", "category": "Service voice AI", "workflow": "Answer calls and support service booking. Value hypothesis: recover qualified requests while preserving staff escalation.", "buyer": "Service BDC and fixed-operations leaders", "compatibility": "Vendor identifies Tekion under certified integrations. Certification is a vendor claim; scope was not independently audited.", "access": "General service-agent scheduling is advertised. Exact Tekion appointment writes or RO reads are not separately established.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare Numa, Toma and native scheduling. Evaluate complex requests, handoffs and capacity constraints on the same cases.", "evidence_limits": "Do not infer every STELLA module has identical access. No measured adoption, appointment uplift or production reliability verified.", "next_step": "Obtain product-specific published scope where available and define held-out calls including unavailable capacity and ambiguous requests.", "sources": [ { "url": "https://stellaautomotive.com/integrations/", "title": "STELLA Automotive AI product/integration evidence", "claim": "Vendor identifies Tekion under certified integrations. Certification is a vendor claim; scope was not independently audited." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "toma-tekion", "name": "Toma AI phone assistant", "vendor": "Toma", "platform": "Tekion (vendor source)", "category": "Service voice AI", "workflow": "Phone-driven appointment booking. Value hypothesis: reduce missed service requests without losing intent or overpromising.", "buyer": "Service BDC and service manager", "compatibility": "Vendor setup guide describes Toma in ARC Integration Hub and a dealer-requested connection. No dealer account was inspected.", "access": "The guide describes reviewing data permissions during connection; those exact permissions are not publicly enumerated.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare Numa/STELLA and native service workflows. A setup guide is more concrete than a logo, but still does not prove operational fit.", "evidence_limits": "Marketing setup-time and uplift claims are not treated as measured results. No connection, account or authorization was used.", "next_step": "Before activation, independently confirm the requested permission scope; then test rescheduling, cancellation, duplicates and human escalation in a bounded trial.", "sources": [ { "url": "https://kb.toma.com/how-to-integrate-toma-with-tekion", "title": "Toma product/integration evidence", "claim": "Vendor setup guide describes Toma in ARC Integration Hub and a dealer-requested connection. No dealer account was inspected." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "mykaarma-tekion", "name": "myKaarma order-data interoperability", "vendor": "myKaarma", "platform": "Tekion (vendor source)", "category": "Service order data", "workflow": "Retrieve normalized service-order data through myKaarma APIs. Value hypothesis: a consistent read interface for approved operational tools.", "buyer": "Fixed-operations technology lead and integration engineer", "compatibility": "Public schema includes Tekion as a possible DMS value. This is weak relationship evidence, not proof of current certified connectivity.", "access": "Order retrieval schema contains status, amount and vehicle/customer references. It does not establish that each field is populated for Tekion or that write-back exists.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare direct platform APIs and authorized exports. Prefer the least complex interface that supplies accurate, permissioned fields.", "evidence_limits": "Schema enumeration alone does not prove availability, full product coverage, dealer enablement or certification. No functional request was executed.", "next_step": "First establish supported Tekion data fields and customer eligibility; then test missing values, stale status and tenant isolation.", "sources": [ { "url": "https://docs.mykaarma.com/API_references/integration/order/API_reference/get-standard-order-for-uuid", "title": "myKaarma product/integration evidence", "claim": "Public schema includes Tekion as a possible DMS value. This is weak relationship evidence, not proof of current certified connectivity." } ], "checked_at": "2026-10-16", "status": "reviewed" }, { "id": "sunbit-tekion", "name": "Sunbit service financing", "vendor": "Sunbit", "platform": "Tekion (vendor source)", "category": "Service financing", "workflow": "Offer pay-over-time financing for service purchases. Value hypothesis: a clear customer option within an approved service purchase flow.", "buyer": "Fixed-operations management", "compatibility": "Vendor-authored June 2025 fact sheet names Tekion among SaaS integrations. Historical roster evidence only.", "access": "The fact sheet does not establish read/write operations or embedded workflow details.", "pricing": "Unknown: no platform-specific dealer or connector price verified.", "overlap": "Compare other financing offerings and the existing payment flow. Evaluate comprehension, completion and operational burden without assuming financing is suitable for every customer.", "evidence_limits": "Customer financing terms differ from dealer software or integration pricing. Current activation, field access and causal commercial benefit are unverified.", "next_step": "Confirm current program availability and applicable disclosures through authorized review; examine cancellation, refund and reconciliation behavior before launch.", "sources": [ { "url": "https://sunbit.com/wp-content/uploads/2025/06/Sunbit-Media-Fact-Sheet.pdf", "title": "Sunbit product/integration evidence", "claim": "Vendor-authored June 2025 fact sheet names Tekion among SaaS integrations. Historical roster evidence only." } ], "checked_at": "2026-10-16", "status": "reviewed" } ], "inventory": [ { "id": "xtime-cdk", "name": "Xtime Enhanced Repair Order Integration", "vendor": "Xtime", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Repair-order workflow", "summary": "Service staff work on repair orders in Xtime with changes passed into CDK. Value hypothesis: less repeated entry and fewer conflicting versions.", "url": "https://xtime.com/client-resource-center/product-news-updates/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "stella-cdk", "name": "STELLA Service", "vendor": "STELLA Automotive AI", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Service voice AI", "summary": "Handle inbound service calls and scheduler bookings. Value hypothesis: recover missed or after-hours requests with reliable staff handoff.", "url": "https://stellaautomotive.com/stella-service/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "goto-cdk", "name": "GoTo Connect - DMS", "vendor": "GoTo Connect", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Telephony and SMS", "summary": "Combine dealership communications with customer/service context. Value hypothesis: reduce manual context lookup and communication fragmentation.", "url": "https://community.goto.com/discussion/325726/whats-new-with-goto-connect-march", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "aiva-cdk", "name": "AIVA for Fixed Operations Suite", "vendor": "CDK Global", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Service voice AI", "summary": "Conversational service scheduling with capacity settings and staff transfers. Value hypothesis: use an existing suite capability before adding another assistant.", "url": "https://www.cdkglobal.com/aiva-fixed-operations", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "bmw-cdk", "name": "BMW Connected Vehicle", "vendor": "CDK Global", "platform": "Fortellis / CDK Drive (vendor source)", "category": "OEM service information", "summary": "Use connected-vehicle information during service preparation and write-up. Value hypothesis: reduce separate OEM lookups while preserving provenance.", "url": "https://www.cdkglobal.com/oem-integrations/bmw", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "revolutionparts-cdk", "name": "RevolutionParts CDK DMS Integration", "vendor": "RevolutionParts", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Parts commerce", "summary": "Parts inventory and online-order coordination is the workflow to assess. Value hypothesis: less duplicate entry and fewer stock mismatches; exact synchronization behavior still needs verification.", "url": "https://www.revolutionparts.com/oem-plans/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "dealerlogix-cdk", "name": "Dealerlogix Create and Update RO — comparator", "vendor": "Dealerlogix", "platform": "CDK comparator (vendor source)", "category": "Repair-order workflow", "summary": "Coordinate service write-up, approvals and parts handling. Value hypothesis: consolidate operational handoffs and reduce duplicate edits.", "url": "https://dealerlogix.com/pricing/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "autotext-cdk", "name": "AutoText - Denied Work Module — partial evidence", "vendor": "VenueVision", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Customer messaging", "summary": "Base autoTEXT supports two-way messaging and DMS-triggered updates. Potential denied-work follow-up is a research question, not a verified add-on capability.", "url": "https://www3.venuevision.com/autotext/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "kimoby-cdk", "name": "Kimoby Pay CDK Integration", "vendor": "Kimoby", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Payment reconciliation", "summary": "Post successful payments to the matching CDK repair order while staff retain final closure. Value hypothesis: reduce cashier reconciliation errors and manual entry.", "url": "https://www.kimoby.com/products/payment-cdk-writeback", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "curbee-cdk", "name": "Curbee", "vendor": "Curbee", "platform": "Fortellis / CDK Drive (vendor source)", "category": "Mobile service", "summary": "Coordinate mobile-service bookings, routes, technician work and customer updates. Value hypothesis: improve route density and first-visit completion.", "url": "https://www.curbee.com/platform", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "numa-tekion", "name": "AI Appointment Agent / service operations", "vendor": "Numa", "platform": "Tekion (vendor source)", "category": "Service scheduling", "summary": "Identify callers, consult customer/service context and book appointments. Value hypothesis: fewer abandoned requests without overbooking.", "url": "https://numa.com/blog/numa-dealership-integrations-dms-schedulers-crm-guide", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "goto-tekion", "name": "GoTo Connect", "vendor": "GoTo", "platform": "Tekion (vendor source)", "category": "Telephony and SMS", "summary": "Call or text from customer and lead context in ARC. Value hypothesis: less manual dialing and fewer disconnected communication histories.", "url": "https://www.goto.com/integrations/tekion", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "callrevu-tekion", "name": "CallRevu CRM integration", "vendor": "CallRevu", "platform": "Tekion (vendor source)", "category": "Conversation intelligence", "summary": "Use call outcomes and appointment activity in dealership tools. Value hypothesis: fewer missed follow-ups and better management visibility.", "url": "https://www.callrevu.com/partnerships/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "uveye-tekion", "name": "UVeye inspection integration", "vendor": "UVeye", "platform": "Tekion (vendor source)", "category": "Vehicle inspection", "summary": "Bring scan evidence into advisor and customer workflows. Value hypothesis: clearer findings with less manual report handling.", "url": "https://uveye.com/integration/tekion/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "sharebox-tekion", "name": "Key Lounge / self-service kiosks", "vendor": "Sharebox", "platform": "Tekion (vendor source)", "category": "Key handover", "summary": "After-hours key drop-off and collection. Value hypothesis: convenient handover without weakening custody or identity checks.", "url": "https://sharebox.global/int/key-lounge/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "lyft-tekion", "name": "Lyft Concierge service transportation", "vendor": "Lyft Business", "platform": "Tekion (vendor source)", "category": "Customer transportation", "summary": "Request service-customer rides from a dealership workflow or customer link. Value hypothesis: reduce advisor coordination burden while controlling transportation spend.", "url": "https://www.lyft.com/business/customer-stories/walser-buick", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "stella-tekion", "name": "STELLA service agents", "vendor": "STELLA Automotive AI", "platform": "Tekion (vendor source)", "category": "Service voice AI", "summary": "Answer calls and support service booking. Value hypothesis: recover qualified requests while preserving staff escalation.", "url": "https://stellaautomotive.com/integrations/", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "toma-tekion", "name": "Toma AI phone assistant", "vendor": "Toma", "platform": "Tekion (vendor source)", "category": "Service voice AI", "summary": "Phone-driven appointment booking. Value hypothesis: reduce missed service requests without losing intent or overpromising.", "url": "https://kb.toma.com/how-to-integrate-toma-with-tekion", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "mykaarma-tekion", "name": "myKaarma order-data interoperability", "vendor": "myKaarma", "platform": "Tekion (vendor source)", "category": "Service order data", "summary": "Retrieve normalized service-order data through myKaarma APIs. Value hypothesis: a consistent read interface for approved operational tools.", "url": "https://docs.mykaarma.com/API_references/integration/order/API_reference/get-standard-order-for-uuid", "source_label": "Vendor evidence", "checked_at": "2026-10-16" }, { "id": "sunbit-tekion", "name": "Sunbit service financing", "vendor": "Sunbit", "platform": "Tekion (vendor source)", "category": "Service financing", "summary": "Offer pay-over-time financing for service purchases. Value hypothesis: a clear customer option within an approved service purchase flow.", "url": "https://sunbit.com/wp-content/uploads/2025/06/Sunbit-Media-Fact-Sheet.pdf", "source_label": "Vendor evidence", "checked_at": "2026-10-16" } ], "next_batch": "First deepen the weakest evidence: AutoText denied-work module scope, myKaarma Tekion field coverage, STELLA platform-specific permissions and Dealerlogix CDK writeback. Then investigate parts-readiness, warranty-evidence and service payment/reconciliation products through permissible vendor publications. Track pricing, activation, failure recovery and independent adoption evidence as separate unresolved questions; do not expand from a copied directory." }