FelicitiGet in touch
Case studies

Field notes from six teams shipping voice agents.

Recruiter screening, freight tracking, dealership service, insurance brokerage, consumer lending, property management — each built from the same composable sub-agents. What we shipped, what we learned, and how the same fabric handles six very different calls.

  • Recruiter screening

    We hired our backend engineer through this agent.

    An orchestrator composes 11 sub-agents per candidate — verify, probe seniority, qualify intent, kind wrap. Skips what doesn’t apply.

    11
    sub-agents composed
    20+
    candidates screened
    2
    hired into production
    Read the case study →
  • Freight brokerage

    One agent runs check calls and carrier sales.

    Two workflows, one agent fabric — carrier check-calls and inbound carrier sales. The orchestrator picks per call.

    2
    workflows, one agent
    9
    sub-agents composed
    TMS
    system of record
    Read the case study →
  • Auto dealership service

    Confirm appointments and answer "where's my car?"

    The orchestrator composes per workflow — outbound appointment confirmations and inbound service-status calls share the skeleton.

    2
    workflows, one agent
    8
    sub-agents composed
    DMS
    system of record
    Read the case study →
  • Insurance brokerage

    Walk a renewal and issue a COI from the same fabric.

    Outbound renewal check-ins and inbound certificate requests share the skeleton — verify the insured, read the policy from the AMS, log the outcome. The orchestrator picks per call.

    2
    workflows, one agent
    8
    sub-agents composed
    AMS
    system of record
    Read the case study →
  • Consumer lending

    Chase stips outbound. Answer "where's my app?" inbound.

    Outbound stipulation chases and inbound application status calls share the skeleton — verify the applicant, read the file from the LOS, log the outcome. ECOA, TCPA, and FDCPA-aware by composition.

    2
    workflows, one agent
    9
    sub-agents composed
    LOS
    system of record
    Read the case study →
  • Property management

    Take the maintenance call. Send the vendor update.

    Inbound maintenance intake and outbound work-order status calls share the skeleton — verify the resident, read the unit and open WOs from the PMS, log the outcome. Emergency triage runs before anything else.

    2
    workflows, one agent
    9
    sub-agents composed
    PMS
    system of record
    Read the case study →
FAQ

Frequently asked questions

Everything teams ask before they pick up the phone — and a few things they should.

How is this different from ElevenLabs Agents?
ElevenLabs Agents builds the voice layer — we use it for synthesis. What we add is the orchestration above it. ElevenLabs starts from one capable agent you steer with a prompt; we start from composable sub-agents that you build, test, and version like code. Test suites per sub-agent are the unit, not a feature.
What telephony providers do you support?
Twilio and Amazon Connect today. SIP-compatible providers via custom integration. More on roadmap based on customer demand.
What about compliance — TCPA, HIPAA?
TCPA-aware (rate limits, opt-out detection, recording disclosures). HIPAA-eligible architecture; BAA available on enterprise plans. SOC 2 in progress.
Can we self-host?
Yes, on enterprise plans. Most teams start on our managed cloud and migrate later if needed.
What languages do you support?
English is production-ready. Other languages depend on the speech providers you bring — we’re provider-agnostic, so the coverage scales with your stack.
Send us your use case

Want this for your calls?

Tell us the call you want to automate — recruiting or otherwise. We'll send back a working prototype within 48 hours, wired to your actual use case. Same composition pattern you just read about.

A founder reads every one. No sales calls unless you ask.