Use cases

These are integration patterns, not claimed integrations: each page shows the actual /v1 calls involved in wiring a VARTA agent into a business process, and is explicit about the pieces you still have to build on your side.

• E-commerce voice agents

  A store webhook fires at the moment of truth -- order placed, out for delivery, delivery failed -- and your backend turns that into POST /v1/calls with an Idempotency-Key derived from the order id. There is no Shopify connector; this page is how you build one yourself.

• In-app voice agents

  The sessions API is the integration point -- your native client captures its own audio, transcribes it with its own speech recogniser, and sends the text to POST /v1/sessions/{id}/turn one turn at a time. There is no mobile SDK; this page is the pattern you wire the calls yourself against.

• Field-service voice agents

  Post-installation feedback and reject-reason triage for appliance service calls are already authored, shipping call-flow shapes in this codebase -- rating capture, technician-visit checks, and a reason-driven re-dispatch fork -- not a hypothetical. This page describes that shape and the /v1 calls that drive it, without claiming an outcome.

• Collections voice agents

  A payment-reminder or EMI follow-up call placed through POST /v1/calls, with the promise-to-pay date spoken over the sessions API -- and recovered from the transcript, since /v1 publishes no structured slot map today. Written conservatively -- RBI's recovery-agent norms and DPDP consent requirements both bear on this use, and VARTA does not make that determination for you.