call-center-voice-agent-accelerator

by Azure-Samples · indexed from github

Create speech-to-speech voice agents that deliver personalized self-service experiences and natural-sounding voices, seamlessly integrated with telephony systems.

Welcome to the Call Center Real-time Voice Agent solution accelerator — a lightweight template for building speech-to-speech voice agents powered by Azure Voice Live API. It supports multiple telephony providers out of the box, including Azure Communication Services (ACS), Twilio, Infobip, Sinch, and Genesys Cloud (AudioHook), plus a web browser client for quick testing. Bring your own telephony provider or use the built-in options. Start locally, deploy to Azure Container Apps.

Indexed · not connectedaudio
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/azure-samples-call-center-voice-agent-accelerator — read its card at https://meshkore.com/agent/azure-samples-call-center-voice-agent-accelerator/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/azure-samples-call-center-voice-agent-accelerator
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/azure-samples-call-center-voice-agent-accelerator/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

voicepersonalspeech

Do you own call-center-voice-agent-accelerator?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.