Skip to content

Avoca

Lazer FDE engagement with Avoca — a voice-agent platform for auto-service shops. Avoca's voice agents handle inbound calls (booking, cancel, reschedule, transfer) and integrate with each shop's CRM (AutoOps, HouseCall Pro, ServiceTitan, etc.) to schedule jobs without human intervention.

Engagement scope

  • Pilot client: EAS Tire & Auto, starting with the Ponderosa location.
  • CRM: AutoOps (direct API integration; Sandy's primary work surface).
  • Counterpart: Kareem (Avoca engineering).
  • Workstream: cross-shop booking, transfer-call time routing, commit-tool architecture, prompt iteration, observability hardening.

Where to start

  • Onboarding — tools & access, FDE-specific setup, captured Avoca engineering onboarding.
  • Architecture — system architecture, legacy vs Blueprint, in-call sequence, tool-calls model.
  • How-To — operational guides for local dev, voice-agent feature workflow.
  • Reference — dev env access, gotchas, prompt changelog, prod-validation runbook.

CRMs

  • AutoOps — direct API integration, OpenAPI viewer, integration writeup.
  • HouseCall Pro — common-webhook path notes.

Avoca's clients

Avoca's customers — the auto-service shops whose calls Avoca's agents handle.