Tekion (vendor source) · Service scheduling
AI Appointment Agent / service operations
Numa
Marketplace or vendor integration claims do not establish customer authorization, exact endpoint access, fees or deployed performance. Recommendations below are editorial hypotheses.
- Workflow and value hypothesis
- Identify callers, consult customer/service context and book appointments. Value hypothesis: fewer abandoned requests without overbooking.
- Buyer and operating owner
- Fixed-operations director and service BDC
- Platform compatibility evidence
- Vendor guide names Tekion and describes native scheduling/cloud DMS connectivity.
- Read/write and API depth
- Vendor describes customer/appointment reads and end-to-end booking; endpoint schemas and dealer permissions remain unverified.
- Public pricing
- Unknown: no platform-specific dealer or connector price verified.
- Competition, overlap and possible gaps
- Compare with STELLA, Toma and the native scheduler. A gap would be reliable handling of complex service constraints, not simply answering calls.
- Adoption evidence and limits
- No deployment test, price or permission scope verified. The source expands APC incorrectly; that expansion is not relied upon.
- Next research step
- With authorization, test unavailable slots, duplicate callers, parts prerequisites and staff handoff; measure completed eligible ROs and correction time.
Evidence and sources
- Numa product/integration evidence — Vendor guide names Tekion and describes native scheduling/cloud DMS connectivity.