ZolvaPlaybooks
End-to-end recipes you can run in a demo, then ship.
Each playbook is a complete, working path from install to a gated production rollout for one concrete use case. The rule for every playbook: real code with real error handling, and every third-party call verified against the provider's official documentation before it is published. Nothing illustrative, nothing invented.
Channels
Put a guardrailed agent on the channel your customers already use. Your gateway owns the provider specifics; Zolva owns the guardrails and the audit trail.
Voice CX with ElevenLabs
Take call volume off your CX team with a voice agent: ElevenLabs handles speech, Zolva is the brain, every turn guardrailed and audited, escalation to your human team built in. Covers the agents-platform path and the raw TTS path.
channels · guardrails · handover · scorecard
WhatsApp collections via your gateway
Repayment assistance on Meta's WhatsApp Cloud API through your own gateway: RBI contact-window guardrails, payment-link tools, third-party disclosure hard blocks, and every message on the audit chain.
channels · guardrails · audit
SMS collections with Twilio & Razorpay
Repayment assistance over plain SMS: Twilio Messaging as the channel, Razorpay payment links as a guarded tool, and per-customer contact caps plus RBI contact windows enforced as config, not prompt suggestions.
channels · tools · guardrails
Telegram support with Zendesk escalation
A support agent on the Telegram Bot API whose escalations become real Zendesk tickets; when the team solves one, a signed Zendesk webhook resumes the session and tells the customer on the channel where they asked.
channels · handover · resume
Fraud-alert support on RCS
A verified-sender agent on Google's RCS Business Messaging via your own gateway: Pub/Sub inbound, the agentMessages API for replies, third-party disclosure hard-blocked, every turn audited.
channels · guardrails · audit
Testing & quality
Gate every release on its worst cohort, attack your own agent before an adversary does, and turn each production failure into a permanent test.
CI-gated agent releases
zolva validate and zolva eval --gate in GitHub Actions
so no prompt or policy change ships without passing its worst cohort, plus a weekly
drift run and the failure-to-regression loop.
evals · feedback · scorecard
Red-team your agent with synthetics
Attacker personas converse with your real staging agent nightly: prompt injection, social engineering, and data-exfiltration attempts become gated tests, and every attempt lands on the audit chain.
synthetics · guardrails · audit
Every failure becomes a permanent test
Escalations and thumbs-down flow into a failure queue, get triaged into regression cohorts, and gate every future release; the same bug can never silently return, and accepted failures export as a fine-tuning dataset.
feedback · evals · export
Compliance & privacy
The evidence regulators ask for and the data handling they require: a tamper-evident trail, contact limits that count across channels, and PII that never leaves your perimeter.
An audit trail regulators can trust
A tamper-evident hash-chained record of every decision, continuous chain verification, the SARR scorecard, and a self-hosted read-only dashboard, assembled as the evidence EU AI Act and SR 11-7 ask for.
audit · scorecard · dashboard
Cap contacts across every channel
One shared ledger keyed on a customer reference enforces a rolling contact limit over WhatsApp, SMS, and RCS together, with RBI contact windows, as config not prompt suggestions.
guardrails · customer_ref · audit
Mask PII before the model sees it
Card numbers, emails, phones, and your own identifiers are redacted before any text reaches the model, while sessions, audit, and human handover keep the true transcript. Exports are masked too.
redaction · sessions · handover
Operations & infrastructure
Run the platform on your terms: one handover desk for every escalation, and every model call routed through a gateway inside your own network.
The handover desk lives in Slack
Every escalation from every agent lands as a threaded message in one Slack channel; a teammate's thread reply becomes the resolution, recorded back into the session and the audit chain through the resume endpoint.
handover · resume · audit
Run against your own LLM gateway
Point Zolva at an in-VPC, OpenAI-compatible gateway (LiteLLM, vLLM, or a Bedrock or Azure proxy) so no prompt or customer data leaves your network, with bounded retries and per-gateway timeouts.
bridge · base_url · resilience