Automotive marketplace research
Checked: 2026-10-16
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.

Xtime Enhanced Repair Order Integration | Xtime | Fortellis / CDK Drive (vendor source) | Repair-order workflow
Service staff work on repair orders in Xtime with changes passed into CDK. Value hypothesis: less repeated entry and fewer conflicting versions.
Source: https://xtime.com/client-resource-center/product-news-updates/
Profile: https://jaycorp.us/automotive-marketplaces/xtime-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Xtime product evidence
URL: https://xtime.com/client-resource-center/product-news-updates/
Supports: Vendor updates describe enhanced CDK DMS integration and automatic flow of Xtime work into CDK; the integration directory lists CDK Global.
Evidence: Xtime supporting integration evidence
URL: https://xtime.com/integrations/
Supports: Supporting vendor description; not a functional or certification audit.

STELLA Service | STELLA Automotive AI | Fortellis / CDK Drive (vendor source) | Service voice AI
Handle inbound service calls and scheduler bookings. Value hypothesis: recover missed or after-hours requests with reliable staff handoff.
Source: https://stellaautomotive.com/stella-service/
Profile: https://jaycorp.us/automotive-marketplaces/stella-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: STELLA Automotive AI product evidence
URL: https://stellaautomotive.com/stella-service/
Supports: Product page describes scheduler booking; vendor FAQ names CDK Global. Exact CDK Drive versus CDK Service path needs confirmation.
Evidence: STELLA Automotive AI supporting integration evidence
URL: https://stellaautomotive.com/resources/frequently-asked-questions/
Supports: Supporting vendor description; not a functional or certification audit.

GoTo Connect - DMS | GoTo Connect | Fortellis / CDK Drive (vendor source) | Telephony and SMS
Combine dealership communications with customer/service context. Value hypothesis: reduce manual context lookup and communication fragmentation.
Source: https://community.goto.com/discussion/325726/whats-new-with-goto-connect-march
Profile: https://jaycorp.us/automotive-marketplaces/goto-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: GoTo Connect product evidence
URL: https://community.goto.com/discussion/325726/whats-new-with-goto-connect-march
Supports: Official vendor release-community announcement explicitly names CDK Drive among integrations.
Evidence: GoTo Connect supporting integration evidence
URL: https://www.goto.com/blog/goto-connect-for-automotive
Supports: Supporting vendor description; not a functional or certification audit.

AIVA for Fixed Operations Suite | CDK Global | Fortellis / CDK Drive (vendor source) | Service voice AI
Conversational service scheduling with capacity settings and staff transfers. Value hypothesis: use an existing suite capability before adding another assistant.
Source: https://www.cdkglobal.com/aiva-fixed-operations
Profile: https://jaycorp.us/automotive-marketplaces/aiva-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: CDK Global product evidence
URL: https://www.cdkglobal.com/aiva-fixed-operations
Supports: CDK product page describes native scheduler integration and inclusion in Fixed Operations Suite.
Evidence: CDK Global supporting integration evidence
URL: https://www2.cdkglobal.com/fixedops-updates
Supports: Supporting vendor description; not a functional or certification audit.

BMW Connected Vehicle | CDK Global | Fortellis / CDK Drive (vendor source) | OEM service information
Use connected-vehicle information during service preparation and write-up. Value hypothesis: reduce separate OEM lookups while preserving provenance.
Source: https://www.cdkglobal.com/oem-integrations/bmw
Profile: https://jaycorp.us/automotive-marketplaces/bmw-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: CDK Global product evidence
URL: https://www.cdkglobal.com/oem-integrations/bmw
Supports: CDK BMW page describes Connected Vehicle / Vehicle Query via BMW SPARQ for recalls, campaigns, coverage and history.

RevolutionParts CDK DMS Integration | RevolutionParts | Fortellis / CDK Drive (vendor source) | Parts commerce
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.
Source: https://www.revolutionparts.com/oem-plans/
Profile: https://jaycorp.us/automotive-marketplaces/revolutionparts-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: RevolutionParts OEM plans
URL: https://www.revolutionparts.com/oem-plans/
Supports: Vendor plan page lists a Fortellis DMS integration add-on; exact operation scope remains unknown.

Dealerlogix Create and Update RO — comparator | Dealerlogix | CDK comparator (vendor source) | Repair-order workflow
Coordinate service write-up, approvals and parts handling. Value hypothesis: consolidate operational handoffs and reduce duplicate edits.
Source: https://dealerlogix.com/pricing/
Profile: https://jaycorp.us/automotive-marketplaces/dealerlogix-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Dealerlogix product evidence
URL: https://dealerlogix.com/pricing/
Supports: Outside the requested filtered snapshot: included only as a vendor-sourced comparator. Vendor pages name CDK integration; exact listing-to-product mapping remains uncertain.
Evidence: Dealerlogix supporting integration evidence
URL: https://faq.dealerlogix.com/article/6-what-dms-providers-is-dealerlogix-integrated-with
Supports: Supporting vendor description; not a functional or certification audit.
Evidence: Dealerlogix parts-writeback FAQ
URL: https://faq.dealerlogix.com/article/415-parts-writeback-faq
Supports: General writeback description; CDK-specific support still requires confirmation.

AutoText - Denied Work Module — partial evidence | VenueVision | Fortellis / CDK Drive (vendor source) | Customer messaging
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.
Source: https://www3.venuevision.com/autotext/
Profile: https://jaycorp.us/automotive-marketplaces/autotext-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: VenueVision product evidence
URL: https://www3.venuevision.com/autotext/
Supports: Vendor sources support base autoTEXT and a CDK relationship; the specific denied-work module is only partially corroborated.
Evidence: VenueVision supporting integration evidence
URL: https://www3.venuevision.com/venuevision-vs-fleetlane/
Supports: Supporting vendor description; not a functional or certification audit.

Kimoby Pay CDK Integration | Kimoby | Fortellis / CDK Drive (vendor source) | Payment reconciliation
Post successful payments to the matching CDK repair order while staff retain final closure. Value hypothesis: reduce cashier reconciliation errors and manual entry.
Source: https://www.kimoby.com/products/payment-cdk-writeback
Profile: https://jaycorp.us/automotive-marketplaces/kimoby-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Kimoby product evidence
URL: https://www.kimoby.com/products/payment-cdk-writeback
Supports: Vendor documents CDK payment writeback, tender mapping and paid-status updates.
Evidence: Kimoby CDK integration explanation
URL: https://www.kimoby.com/blog/kimoby-cdk-integration
Supports: August 4, 2026 distinction between payment posting and repair-line writeback.
Evidence: Kimoby automatic payment settling documentation
URL: https://help.kimoby.com/fortellis-automatic-payment-settling
Supports: Vendor setup and settlement description; no activation performed.

Curbee | Curbee | Fortellis / CDK Drive (vendor source) | Mobile service
Coordinate mobile-service bookings, routes, technician work and customer updates. Value hypothesis: improve route density and first-visit completion.
Source: https://www.curbee.com/platform
Profile: https://jaycorp.us/automotive-marketplaces/curbee-cdk.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Curbee product evidence
URL: https://www.curbee.com/platform
Supports: Vendor M.A.R.S. platform page names native CDK integration.

AI Appointment Agent / service operations | Numa | Tekion (vendor source) | Service scheduling
Identify callers, consult customer/service context and book appointments. Value hypothesis: fewer abandoned requests without overbooking.
Source: https://numa.com/blog/numa-dealership-integrations-dms-schedulers-crm-guide
Profile: https://jaycorp.us/automotive-marketplaces/numa-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Numa product/integration evidence
URL: https://numa.com/blog/numa-dealership-integrations-dms-schedulers-crm-guide
Supports: Vendor guide names Tekion and describes native scheduling/cloud DMS connectivity.

GoTo Connect | GoTo | Tekion (vendor source) | Telephony and SMS
Call or text from customer and lead context in ARC. Value hypothesis: less manual dialing and fewer disconnected communication histories.
Source: https://www.goto.com/integrations/tekion
Profile: https://jaycorp.us/automotive-marketplaces/goto-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: GoTo product/integration evidence
URL: https://www.goto.com/integrations/tekion
Supports: Dedicated vendor integration page describes ARC calling/texting and configurable account modes.

CallRevu CRM integration | CallRevu | Tekion (vendor source) | Conversation intelligence
Use call outcomes and appointment activity in dealership tools. Value hypothesis: fewer missed follow-ups and better management visibility.
Source: https://www.callrevu.com/partnerships/
Profile: https://jaycorp.us/automotive-marketplaces/callrevu-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: CallRevu product/integration evidence
URL: https://www.callrevu.com/partnerships/
Supports: Vendor integration roster names Tekion. This is roster evidence, not a product-specific API specification.

UVeye inspection integration | UVeye | Tekion (vendor source) | Vehicle inspection
Bring scan evidence into advisor and customer workflows. Value hypothesis: clearer findings with less manual report handling.
Source: https://uveye.com/integration/tekion/
Profile: https://jaycorp.us/automotive-marketplaces/uveye-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: UVeye product/integration evidence
URL: https://uveye.com/integration/tekion/
Supports: Dedicated vendor page describes inspection reports within ARC repair orders.

Key Lounge / self-service kiosks | Sharebox | Tekion (vendor source) | Key handover
After-hours key drop-off and collection. Value hypothesis: convenient handover without weakening custody or identity checks.
Source: https://sharebox.global/int/key-lounge/
Profile: https://jaycorp.us/automotive-marketplaces/sharebox-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Sharebox product/integration evidence
URL: https://sharebox.global/int/key-lounge/
Supports: Vendor product landing page names Tekion integration.

Lyft Concierge service transportation | Lyft Business | Tekion (vendor source) | Customer transportation
Request service-customer rides from a dealership workflow or customer link. Value hypothesis: reduce advisor coordination burden while controlling transportation spend.
Source: https://www.lyft.com/business/customer-stories/walser-buick
Profile: https://jaycorp.us/automotive-marketplaces/lyft-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Lyft Business product/integration evidence
URL: https://www.lyft.com/business/customer-stories/walser-buick
Supports: Vendor customer case study describes an ARC/APC ride-request workflow introduced in 2022.

STELLA service agents | STELLA Automotive AI | Tekion (vendor source) | Service voice AI
Answer calls and support service booking. Value hypothesis: recover qualified requests while preserving staff escalation.
Source: https://stellaautomotive.com/integrations/
Profile: https://jaycorp.us/automotive-marketplaces/stella-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: STELLA Automotive AI product/integration evidence
URL: https://stellaautomotive.com/integrations/
Supports: Vendor identifies Tekion under certified integrations. Certification is a vendor claim; scope was not independently audited.

Toma AI phone assistant | Toma | Tekion (vendor source) | Service voice AI
Phone-driven appointment booking. Value hypothesis: reduce missed service requests without losing intent or overpromising.
Source: https://kb.toma.com/how-to-integrate-toma-with-tekion
Profile: https://jaycorp.us/automotive-marketplaces/toma-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Toma product/integration evidence
URL: https://kb.toma.com/how-to-integrate-toma-with-tekion
Supports: Vendor setup guide describes Toma in ARC Integration Hub and a dealer-requested connection. No dealer account was inspected.

myKaarma order-data interoperability | myKaarma | Tekion (vendor source) | Service order data
Retrieve normalized service-order data through myKaarma APIs. Value hypothesis: a consistent read interface for approved operational tools.
Source: https://docs.mykaarma.com/API_references/integration/order/API_reference/get-standard-order-for-uuid
Profile: https://jaycorp.us/automotive-marketplaces/mykaarma-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: myKaarma product/integration evidence
URL: https://docs.mykaarma.com/API_references/integration/order/API_reference/get-standard-order-for-uuid
Supports: Public schema includes Tekion as a possible DMS value. This is weak relationship evidence, not proof of current certified connectivity.

Sunbit service financing | Sunbit | Tekion (vendor source) | Service financing
Offer pay-over-time financing for service purchases. Value hypothesis: a clear customer option within an approved service purchase flow.
Source: https://sunbit.com/wp-content/uploads/2025/06/Sunbit-Media-Fact-Sheet.pdf
Profile: https://jaycorp.us/automotive-marketplaces/sunbit-tekion.html
checked_at: 2026-10-16
status: reviewed
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.
Evidence: Sunbit product/integration evidence
URL: https://sunbit.com/wp-content/uploads/2025/06/Sunbit-Media-Fact-Sheet.pdf
Supports: Vendor-authored June 2025 fact sheet names Tekion among SaaS integrations. Historical roster evidence only.