Calyx runs your phone, WhatsApp, storefront and meeting agents on your own data. Every contact is consent-checked first, every call ends in a typed outcome, and what the agent learns stays in your workspace.
Most agent platforms optimise for how natural the voice sounds. Calyx optimises for what happens around the voice: who it is allowed to call, what it is allowed to say, and what it writes down afterwards.
A consent record per contact and per channel: AI voice, SMS, email, WhatsApp. The outbound path refuses to dial or message without one, and STOP on WhatsApp writes the opt-out back. The gate lives in code, not in a policy document.
refuse unless consent.voice_ai == written
Every call and conversation ends in a typed outcome from your goal template, with the next step and the fields the agent collected. Reports and campaign metrics are built on those outcomes, not on a transcript someone has to read.
outcome: callback_booked · 2026-11-12 18:30
Recall learns from finished calls and meetings and serves that memory back to the next session: preferences, open issues, what was promised. It is scoped to your workspace and your cloud. Nothing is pooled across customers.
recall.serve(contact) → 3 facts, 2 open items
Design the agent once in the console. Give it knowledge bases, a goal template and a voice. Then put it on the channels your customers already use.
Upload a contact list or feed one from an integration. Set the goal, the calling window and the retry rules. Watch outcomes land as calls finish.
Attach an agent to a number. It answers, resolves what it can from the knowledge base, and hands off with a summary when it should.
Follow up a call with a link or a confirmation, or run the whole conversation in chat. Consent and opt-out are shared with voice.
Send the agent into Meet, Zoom or Teams. It transcribes, answers when addressed, and files a structured summary with the session.
Products, policies, pages and documents, synced on a schedule. The agent cites what it used, so you can see why it said what it said.
Every session with its outcome, recording, transcript and the fields collected. Filter by campaign, agent or outcome type.
An abandoned checkout, a campaign row, or an inbound ring.
The contact's consent for this channel is checked. No record, no call.
Recall serves prior facts and open items for this contact.
Grounded in the knowledge base, within the goal template.
The session closes with an outcome, next step and collected fields.
New facts are written back. The report is ready in the console.
Install from the console, approve the read scopes, and sync your products, policies and pages into the store knowledge base. The store agent answers on your storefront in chat or voice. When a checkout is abandoned, it can call, with WhatsApp and email as backup, and attribute the recovered order back to the call.
Enable the Calyx store agent in the theme editor and paste the public key. One snippet, no theme surgery.
Abandon events arrive with the cart, so the agent knows what was left behind and why shipping looked slow.
A holdout group that is never called, so the lift you report is lift you earned.
Calyx ships as Helm charts and a Compose stack. Run it in your own cloud project, with your own provider keys, behind your own network.
Thirty minutes. We set up one agent against a sample of your knowledge base, run a live call, and show you the outcome and the memory it leaves behind.