Coggleby Glossary

31 terms — operational, integration, and compliance vocabulary used throughout Coggleby documentation and blog posts.

A

After-hours coverage
Inbound call answering outside posted shop hours. Independent shops often miss tow and emergency-symptom calls overnight; an AI front desk captures the request, triages drivable-vs-tow, and queues the casefile for the morning.
AI front desk
Automated voice agent that answers inbound calls, captures vehicle and symptom data, and writes a structured estimate request into the shop management system. Replaces voicemail and reduces interruptions to the service advisor.
AutoLeap
A cloud-based shop management system widely used by independent auto-repair shops. Coggleby writes estimate requests directly into AutoLeap as customer + vehicle + repair-order records.

B

Bay utilization
The proportion of available service-bay hours occupied by paying repair orders. Low utilization is usually a scheduling and intake problem, not a marketing problem.
Bilingual coverage
The ability to intake a call in the caller's preferred language without manual routing. Spanish-speaking customers are a meaningful share of inbound calls in many US metros; an AI front desk that auto-detects language preserves the call.

C

CARFAX
Vehicle-history report service. Not directly integrated with intake, but VIN capture during intake makes downstream CARFAX lookups trivial for the service advisor.

D

Drivable vs tow
Triage decision made during intake: can the vehicle safely reach the shop under its own power, or does it need a tow? This single bit of information drives whether the caller needs an estimate slot or an immediate dispatch.
DTC code
Diagnostic Trouble Code — a standardized identifier (e.g. P0420) emitted by the vehicle's OBD-II system when a fault is detected. Capturing the code during intake speeds shop-side diagnosis.

E

Estimate request
A structured record containing year/make/model, mileage, symptom description, urgency, drivable status, and contact info — everything the service advisor needs to scope an estimate without a callback.

F

First-call resolution
Closing the loop on a customer request within a single phone interaction. Hard to achieve in auto repair (diagnostic is rarely instant), but capturing complete intake data on the first call is the realistic version of the goal.
Front desk
The role responsible for answering inbound calls, greeting walk-ins, and routing requests to the service advisor or technician. In small shops this is often the owner or a service advisor doing it as a side duty.

H

Heavy line work
Repairs that occupy a bay for an extended period — engine, transmission, head-gasket. Heavy line work has different scheduling implications than maintenance and should be flagged at intake.

I

Intake script
The ordered sequence of questions used to capture an estimate request: greet, language preference, vehicle, mileage, symptoms, urgency, drivable status, contact info, consent.

L

Language detection
Automatic identification of the caller's spoken language within the first few seconds of audio, used to switch the intake script to the correct language without asking.

M

Mileage
Odometer reading at the time of intake. Used by the service advisor to scope wear-item repairs and recommend interval-based maintenance.

N

No-show appointment
A scheduled estimate or repair slot where the customer does not arrive. Reminders, deposit collection, and clearer expectations at intake all reduce no-show frequency.

O

OBD-II
On-Board Diagnostics version 2 — the standard interface in passenger vehicles since 1996. Source of DTC codes that can be captured at intake if the customer has read them off a scan tool.

R

Repair order
The work-order record in the shop management system once a customer commits to a repair. Often referred to as an RO.

S

Service advisor
The shop staffer responsible for greeting customers, writing estimates, communicating diagnoses, and selling repair work. In small shops often the owner.
Shop management system
Software-of-record for an auto-repair shop — customer database, vehicle history, RO scheduling, parts ordering, invoicing. Coggleby integrates with AutoLeap and is adding Tekmetric and Shopmonkey.
Shopmonkey
A cloud shop management system used by independent and multi-bay shops. On the Coggleby integration roadmap.
SMS reminder
Text message sent to a customer ahead of an appointment to reduce no-shows. Requires explicit consent at intake under TCPA.
Symptom checklist
Structured set of common complaint categories (noise, vibration, warning light, leak, performance, electrical, body) used at intake to standardize what the customer is reporting.

T

TCPA
Telephone Consumer Protection Act — US federal statute governing automated calls and SMS to consumers. Requires prior express consent for marketing texts; intake confirmations are treated more leniently but consent is still best practice.
Tekmetric
A cloud shop management system focused on multi-bay independents. On the Coggleby integration roadmap.
Tow triage
Sequence of intake questions that determine whether a vehicle is drivable or needs a tow, and if a tow, what the destination, vehicle weight class, and urgency are. Coggleby sends a triggered SMS to the shop's dispatch contact when a tow is required.
Twilio
Telephony API provider used to receive inbound calls and send outbound SMS. The carrier-layer plumbing under the Coggleby front desk.

V

Vapi
Voice AI platform that handles real-time speech-to-text, LLM reasoning, and text-to-speech for the Coggleby agent. Calls hit Twilio first, then Vapi, then Coggleby webhooks for intake persistence.
Vehicle history
Record of previous repairs, recalls, and ownership for a specific VIN. Sources include CARFAX, AutoCheck, and the shop's own RO history.
Related: CARFAX, VIN
VIN
Vehicle Identification Number — 17-character unique identifier. Captured at intake when available; enables exact year/make/model/trim decoding and recall lookups.
Voicemail-only fallback
The legacy alternative to a live or AI front desk. Voicemail loses callers who hang up, callers who never leave a message, and the structured-data advantage of an intake script.