Lorikeet handles 60%+ of KeyMe's inbound calls, captures the details your team needs, and lands a clean ticket in Zendesk — with a light engineering lift on KeyMe's side.
From our conversation: 8–10K calls a month, handled today by 13 phone agents. Roughly 70% of that volume is two repeating patterns — kiosk help and bad-key refunds — both of which can be triaged before anything reaches a human.
No direct API needed into your main ordering system on day one. Lorikeet works as an intelligent front line — it answers, qualifies, captures the right details, and creates a Zendesk ticket your team picks up. Your agents work tickets instead of taking calls, which is roughly an 8–10× efficiency gain on agent time.
Lorikeet answers every call with a brand-aligned voice agent, runs the right intake script for each issue type, and pushes a tagged, prioritised ticket into Zendesk for your team to resolve over email or text.
Once we can integrate with your ordering system, Lorikeet moves from "intake + ticket" to "resolve on the call" — the agent looks up the order, processes the refund to card on file, and ships a replacement key. Your team built the muscle to absorb the volume; Lorikeet absorbs even more of it.
Twilio and Zendesk are our two most-deployed integrations. The build sits primarily on Lorikeet's side — KeyMe's input is a couple of scoping calls with your director of business ops (Twilio) and Zendesk admin, plus light eng review on access and rollout.
Lorikeet picks up the existing Twilio number. We use Twilio internally for our own voice infrastructure, so the integration is battle-tested and primarily driven by your business ops contact, with light eng involvement.
Tickets land with proper tags, priority, channel, and structured fields so your agents pick up a familiar queue with full context — not a transcript blob. Most of our subscribers run Zendesk.
Lorikeet is priced as a fixed annual platform fee — no per-call or per-message charges to manage as volume scales. The math is straightforward when you compare it against the agents you'd otherwise hire to absorb that volume.
| Headcount offset | Loaded cost ($45K/agent) | Net vs. Lorikeet |
|---|---|---|
| 4 agents (expected) | $180K | +$45K saved |
| 5 agents (upside) | $225K | +$90K saved |
As KeyMe shifts more volume to email and text in 2026, the same $135K covers materially more of your support load — a written contact takes a fraction of the agent time of a call. The price stays flat; the offset grows.
Try the live agent before tomorrow's 1:1 — same workflows, same brand voice, running right now on a real Twilio number.