{ "slug": "voice-agent-launch-checklist", "title": "Voice Agent Launch Checklist: The Go/No-Go Gates Before Real Callers", "description": "A voice agent launch checklist as yes/no gates: scope, offline replay, per-stage latency, barge-in, tools, transport, handoff, cost, guardrails, monitoring and rollback, each with a pass signal and the article that owns the method.", "kind": "sub", "order": 11, "target_query": "voice agent launch checklist", "secondary_queries": [ "voice agent go live checklist", "voice ai agent pre launch checklist" ], "tags": [ "voice", "launch", "checklist", "go-live", "readiness", "agents", "production" ], "published": "2026-10-14", "updated": "2026-10-15", "words": 1429, "estimated_tokens": 1901, "premium": false, "rights": { "access": "free", "note": "Editorial guides are always free and never part of the licensed corpus.", "license": "https://changegamer.ai/license.xml", "pricing": "https://changegamer.ai/api/pricing.json", "payment": "https://changegamer.ai/api/payment.json" }, "license": "https://changegamer.ai/license.xml", "citation": "ChangeGamer (2026-10-14). Voice Agent Launch Checklist: The Go/No-Go Gates Before Real Callers. ChangeGamer. https://changegamer.ai/articles/voice-agent-launch-checklist (updated 2026-10-15).", "bibtex": "@misc{changegamer_voice_agent_launch_checklist, title = {Voice Agent Launch Checklist: The Go/No-Go Gates Before Real Callers}, publisher = {ChangeGamer}, year = {2026}, url = {https://changegamer.ai/articles/voice-agent-launch-checklist}, note = {Updated 2026-10-15}}", "canonical": "https://changegamer.ai/articles/voice-agent-launch-checklist", "markdown": "https://changegamer.ai/articles/voice-agent-launch-checklist.md", "takeaways": [ "A voice agent launch checklist is a set of yes/no gates, each with a pass signal you can show someone, and as the author's inference a single unresolved \"no\" means the launch waits.", "The evaluating-voice-agents reference says offline evaluation should gate a release by replaying fixed recorded or synthetic calls, including deliberately hard ones such as accents, background noise and crosstalk.", "The voice-realtime-agents reference sets a sub-600 ms glass-to-glass latency target and advises keeping mid-conversation tool calls under 200 ms, so a launch gate should compare measured percentiles against those figures.", "The customer-support-agents reference advises launching on a narrow set of well-understood request types, such as order status and password reset, before expanding into judgment-heavy categories.", "The corpus gives no numeric pass thresholds for barge-in accuracy, false-interruption rate or alert levels, so each launch gate threshold must be set from your own pilot traffic and written down before the go decision." ], "outline": [ { "depth": 2, "text": "What decides whether a voice agent is ready to launch?", "anchor": "what-decides-whether-a-voice-agent-is-ready-to-launch", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#what-decides-whether-a-voice-agent-is-ready-to-launch" }, { "depth": 2, "text": "Which gates cover the conversation itself?", "anchor": "which-gates-cover-the-conversation-itself", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#which-gates-cover-the-conversation-itself" }, { "depth": 2, "text": "Which gates cover the path to the caller?", "anchor": "which-gates-cover-the-path-to-the-caller", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#which-gates-cover-the-path-to-the-caller" }, { "depth": 2, "text": "Which gates cover risk, cost and visibility?", "anchor": "which-gates-cover-risk-cost-and-visibility", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#which-gates-cover-risk-cost-and-visibility" }, { "depth": 2, "text": "How should the first real traffic be sequenced?", "anchor": "how-should-the-first-real-traffic-be-sequenced", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#how-should-the-first-real-traffic-be-sequenced" }, { "depth": 2, "text": "What does the corpus not say about launching a voice agent?", "anchor": "what-does-the-corpus-not-say-about-launching-a-voice-agent", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#what-does-the-corpus-not-say-about-launching-a-voice-agent" }, { "depth": 2, "text": "Has ChangeGamer run a go/no-go gate itself?", "anchor": "has-changegamer-run-a-go-no-go-gate-itself", "url": "https://changegamer.ai/articles/voice-agent-launch-checklist#has-changegamer-run-a-go-no-go-gate-itself" } ], "faq": [ { "question": "What should be on a voice agent launch checklist?", "answer": "A voice agent launch checklist should cover scope, an offline replay, per-stage latency, barge-in, tools, transport, human handoff, cost, spoken-output guardrails, live monitoring and a rollback path. Each item should be a yes/no gate with a pass signal, an inference of this article, not a corpus standard." }, { "question": "How do you decide a voice agent is ready for real callers?", "answer": "A voice agent is ready when every gate on your checklist has a recorded pass signal, including an offline replay that gates the release per the evaluating-voice-agents reference. The thresholds are yours to set from pilot traffic, because the corpus supplies almost none." }, { "question": "Should a voice agent launch to all callers at once?", "answer": "No, as the author's inference. The customer-support-agents reference advises starting on a narrow set of well-understood request types, and the pillar sequences launch from internal callers to a small share of real traffic with a human fallback always reachable." }, { "question": "Does a voice agent launch checklist replace the general agent checklist?", "answer": "No. This checklist adds the voice-only gates, such as barge-in, spoken guardrails and handoff audio, while the shipping-agents-to-production reference holds the general readiness list for evaluation gates, observability, cost controls and rollback that any customer-facing agent needs." } ], "body": "A voice agent is ready for real callers when every gate below has a yes and a pass signal you can show someone else; a single \"no\" means wait. This article is the pre-launch list for the [voice AI agent in production](/articles/voice-ai-agent-in-production) cluster, and each gate points to the article that owns the method instead of repeating it.\n\nLabels: \"corpus\" means a named reference says it; \"inference\" means it is the author's own reasoning. The gate list and pass signals are inference, and the only numbers are two corpus targets; every other threshold is \"set from your own traffic\". Vendor facts in the voice reference carry a 2026-07-09 check date that the later 2026-09-28 pass did not renew.\n\n## What decides whether a voice agent is ready to launch?\n\nReadiness is decided by evidence, not confidence: each gate is a yes/no condition plus a pass signal such as a replay report, a percentile table or a recorded test call. That shape is inference, but the evaluating-voice-agents reference supports its core, saying offline evaluation should gate a release while online monitoring catches what the fixed set misses afterward (corpus).\n\nThree rules keep the list honest (inference):\n\n- Write each threshold down before you look at the result, so the gate cannot move to fit the number.\n- Run the gates on the production path: the real transport, the real tools and a real phone or browser, not a developer shortcut.\n- Name one person who can say no. A checklist nobody can veto is a status report.\n\nFor anything that is not specific to voice, the [shipping agents to production](/resources/shipping-agents-to-production) reference holds the general readiness list. Nothing below stands in for it.\n\n## Which gates cover the conversation itself?\n\nFive gates cover the conversation: scope, offline replay, per-stage latency, barge-in and tools. Each is stated as a question that must be answered yes.\n\n1. **Scope: is the first release limited to request types you understand well?** The customer-support-agents reference advises launching on well-understood types including order status, resets and documented policy lookups (corpus). Pass signal: a written list of in-scope intents and a spoken answer for everything else.\n2. **Replay: did a fixed set of calls, including hard ones, pass on the exact build you will ship?** The evaluating-voice-agents reference lists accents, background noise and crosstalk as deliberately hard cases (corpus). Pass signal: a report on the release candidate, not an earlier build. Metric definitions are in [evaluating voice agents](/resources/evaluating-voice-agents).\n3. **Latency: are percentiles measured per stage and end to end, against the 600 ms target?** The voice-realtime-agents reference targets sub-600 ms glass to glass (corpus). Pass signal: P50 and P95 per stage from calls over the real path. The split and measurement method are in the [voice agent latency budget](/articles/voice-agent-latency-budget).\n4. **Barge-in: does the agent stop for real interruptions and ignore backchannels?** Pass signal: barge-in accuracy and false-interruption rate, both counted from a labelled clip set against thresholds you wrote beforehand, as in [testing turn detection and barge-in](/articles/voice-turn-detection-and-barge-in-testing).\n5. **Tools: does every tool have a time budget, a class and a spoken failure path?** The reference advises keeping mid-conversation tool calls under 200 ms (corpus). Pass signal: a table of tools with measured durations; the admission rules are in [tool admission rules for voice](/articles/tools-in-a-voice-agent-loop).\n\n## Which gates cover the path to the caller?\n\nTwo gates cover the path: the transport works from the caller's real network, and a handoff works when the agent lets go. Both fail in ways a quiet office test never shows.\n\n6. **Transport: has the chosen transport been exercised from the client types you will serve?** The corpus pairs WebRTC with browser and mobile clients, WebSocket with server-to-server and a SIP path with telephony for some vendors, and says nothing about carriers or the phone network. Pass signal: dropped-connection and real-network tests passed; details in [WebRTC vs WebSocket vs SIP](/articles/voice-agent-transport-webrtc-vs-websocket-vs-sip). For phone calls, place real calls, because no corpus entry substitutes for that.\n7. **Handoff: can a caller reach a person, and does the context arrive?** The customer-support-agents reference says to instrument escalation triggers together with deflection from day one (corpus). Pass signal: a recorded transfer that succeeded, one that failed audibly and one with no answer; mechanics in [handoff mechanics on the call](/articles/voice-agent-human-handoff).\n\n## Which gates cover risk, cost and visibility?\n\nFour gates cover what can hurt you after the first hour: cost, spoken output, monitoring and the vendor. They are the ones teams skip because nothing fails during a demo.\n\n8. **Cost: do you have a per-minute figure computed from pilot usage?** Pass signal: a number built from recorded usage and a dated vendor rate card, with the method in [voice agent cost per minute](/articles/voice-agent-cost-per-minute) and a spend limit you will notice reaching.\n9. **Guardrails: has spoken output been tested adversarially, with a fail-closed behavior defined?** The voice-realtime-agents reference warns that cascaded pipelines inherit transcription errors (corpus). Pass signal: a recorded adversarial script run; see [guardrails for spoken output](/articles/guardrails-for-spoken-output-in-voice-agents).\n10. **Monitoring: do dashboards and alerts exist, and has an alert been fired deliberately?** The evaluating-voice-agents reference names transcription confidence, per-stage and end-to-end latency and containment as online signals (corpus). Pass signal: a fault injected on purpose reached a human. The plan is in [the live dashboard plan](/articles/voice-agent-online-monitoring). Traces should also let you find one call: the agent-observability reference describes the trace and span model for that.\n11. **Vendor and rollback: do you know which model serves calls, and can you return to the previous configuration in one step?** Pass signal: the model identifier appears on a sample trace and a rollback was rehearsed once; the routine is in [handling a vendor model change](/articles/voice-agent-vendor-change-management). Generic canary mechanics sit in [agent rollout and rollback](/articles/agent-rollout-and-rollback).\n\nThe architecture decision behind gates 3 and 9 is already made by launch day; if you doubt it, the seams are laid out in [what to log and filter by architecture](/articles/voice-agent-architecture-cascaded-vs-speech-to-speech).\n\n## How should the first real traffic be sequenced?\n\nSend real callers in widening steps with a human reachable throughout, and widen only when the gates still hold on the new traffic. This is the pillar's launch order, restated as a decision rule rather than copied: internal callers first, then a small share of real traffic, then more scope as handoff and resolution logs say it is safe (corpus advice for scope, inference for the steps).\n\n| Step | Who calls | Hold until |\n|---|---|---|\n| 1 | Your own team, on the production path | Gates 1 to 11 each have a recorded pass |\n| 2 | A small share of real traffic on in-scope intents | Live panels match the replay and pilot baselines |\n| 3 | More traffic or more intents, one change at a time | Handoff reasons and resolution still look healthy |\n\nThe share and the hold time are yours to set from your own traffic; the corpus gives neither.\n\n## What does the corpus not say about launching a voice agent?\n\nThe corpus does not give pass thresholds, compliance requirements or telephony procedures, so a checklist built on it can structure the decision but cannot make it. Specifically, as of October 2026:\n\n- no numeric threshold for barge-in accuracy, false-interruption rate, transcription confidence or alert levels;\n- nothing on call recording consent, disclosure that the caller is speaking to an AI, or regional telephony rules, so take legal advice for the places your callers are;\n- nothing on trunking, touch-tone input or codecs beyond the existence of vendor SIP paths;\n- vendor facts dated 2026-07-09, so re-read current vendor documentation before relying on a model name, transport or price.\n\n## Has ChangeGamer run a go/no-go gate itself?\n\nNot on voice, since it has no voice agent and no call data, but it does run a publishing gate shaped like the checklist above. Its CI workflow, `.github/workflows/ci.yml`, runs `node ../scripts/aeo-audit.mjs --since 2026-08-14 --min 85` and fails the build for an article scoring below the floor. A comment in that file records the floor being raised from 80 to 85 on 2026-08-14 and says never to lower it to make a red build pass. That is the discipline worth borrowing: a fixed threshold, written before the result, enforced by a machine rather than by goodwill. For the metric definitions behind your own thresholds, see [evaluating voice agents](/resources/evaluating-voice-agents) and [voice and realtime agents](/resources/voice-realtime-agents); launch scope for customer-facing agents is in [AI customer support agents](/resources/customer-support-agents). If callers will use more than one language, add a per-language replay and an unsupported-language handoff as described in [how a voice agent handles callers who speak another language](/articles/voice-agent-multilingual-callers).", "cluster": { "id": "voice-agents-in-production", "title": "Voice agents in production", "description": "How to build and run a live voice AI agent — architecture choice, turn detection and barge-in, latency budget, tool calls in a voice loop, transport, cost, human handoff, guardrails, monitoring and launch — covering live caller conversations only, not offline dubbing/localization (ai-dubbing-localization-and-subtitling) and not the WER/MOS/VoiceBench scoring methodology owned by the evaluating-voice-agents resource.", "status": "complete", "pillar": { "slug": "voice-ai-agent-in-production", "title": "Voice AI Agent in Production: Architecture, Latency, Handoff and Launch", "description": "How to build and run a voice AI agent in production: cascaded vs speech-to-speech architecture, turn detection and barge-in, the latency budget, tool calls in a voice loop, transport, cost, human handoff and launch sequencing.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/voice-ai-agent-in-production", "markdown": "https://changegamer.ai/articles/voice-ai-agent-in-production.md", "json": "https://changegamer.ai/api/articles/voice-ai-agent-in-production.json" }, "articles": [ { "slug": "voice-agent-latency-budget", "title": "Voice Agent Latency Budget: Where the 600 ms Goes and How to Hold It", "description": "How to split a 600 ms voice agent latency budget across speech-to-text, the language model, speech synthesis and tool calls, how to measure each stage, and which levers hold the budget.", "kind": "sub", "order": 1, "html": "https://changegamer.ai/articles/voice-agent-latency-budget", "markdown": "https://changegamer.ai/articles/voice-agent-latency-budget.md", "json": "https://changegamer.ai/api/articles/voice-agent-latency-budget.json" }, { "slug": "voice-turn-detection-and-barge-in-testing", "title": "How to Test Voice Agent Turn Detection and Barge-In", "description": "How to test voice agent turn detection and barge-in: build a labelled clip set, count barge-in accuracy and false-interruption rate, separate cut-off from talk-over failures, and split offline gates from online monitors.", "kind": "sub", "order": 2, "html": "https://changegamer.ai/articles/voice-turn-detection-and-barge-in-testing", "markdown": "https://changegamer.ai/articles/voice-turn-detection-and-barge-in-testing.md", "json": "https://changegamer.ai/api/articles/voice-turn-detection-and-barge-in-testing.json" }, { "slug": "voice-agent-architecture-cascaded-vs-speech-to-speech", "title": "What to Log and Filter in a Voice Agent, by Architecture", "description": "What to log and filter in a voice agent depending on architecture: where a cascaded pipeline gives you text seams for logging, redaction and output filters, what a native speech-to-speech model leaves you to do from outside, and what a model swap forces you to re-test.", "kind": "sub", "order": 3, "html": "https://changegamer.ai/articles/voice-agent-architecture-cascaded-vs-speech-to-speech", "markdown": "https://changegamer.ai/articles/voice-agent-architecture-cascaded-vs-speech-to-speech.md", "json": "https://changegamer.ai/api/articles/voice-agent-architecture-cascaded-vs-speech-to-speech.json" }, { "slug": "tools-in-a-voice-agent-loop", "title": "Function Calling in a Voice Agent: What a Tool May Be in a Spoken Loop", "description": "Function calling in a voice agent: which vendors and frameworks support tools as of the corpus's 2026-07-09 verification, how to classify tools as lookup, action or handoff, what barge-in does to a side effect, and a checklist for admitting a tool.", "kind": "sub", "order": 4, "html": "https://changegamer.ai/articles/tools-in-a-voice-agent-loop", "markdown": "https://changegamer.ai/articles/tools-in-a-voice-agent-loop.md", "json": "https://changegamer.ai/api/articles/tools-in-a-voice-agent-loop.json" }, { "slug": "voice-agent-transport-webrtc-vs-websocket-vs-sip", "title": "Voice Agent Transport: WebRTC vs WebSocket, and Where SIP Fits", "description": "WebRTC vs WebSocket for voice AI agents: which transport each vendor documents as of the corpus's 2026-07-09 verification, how cascaded stacks use WebSocket components, a decision tree by client type, and a per-transport test checklist.", "kind": "sub", "order": 5, "html": "https://changegamer.ai/articles/voice-agent-transport-webrtc-vs-websocket-vs-sip", "markdown": "https://changegamer.ai/articles/voice-agent-transport-webrtc-vs-websocket-vs-sip.md", "json": "https://changegamer.ai/api/articles/voice-agent-transport-webrtc-vs-websocket-vs-sip.json" }, { "slug": "voice-agent-human-handoff", "title": "Voice Agent Human Handoff: What Happens on the Call When the Agent Lets Go", "description": "Voice agent human handoff mechanics: the handoff as a tool that ends the agent's session, barge-in during the transfer announcement, what the caller hears on hold and on failure, a context payload schema, and a real-call test checklist.", "kind": "sub", "order": 6, "html": "https://changegamer.ai/articles/voice-agent-human-handoff", "markdown": "https://changegamer.ai/articles/voice-agent-human-handoff.md", "json": "https://changegamer.ai/api/articles/voice-agent-human-handoff.json" }, { "slug": "voice-agent-cost-per-minute", "title": "How to Compute Your Voice Agent Cost per Minute", "description": "How to compute a voice agent cost per minute from your own pilot: symbolic formulas for native speech-to-speech and cascaded STT, LLM and TTS, the variables that move the result, idle audio, retries, tool-call turns, and a sensitivity check.", "kind": "sub", "order": 7, "html": "https://changegamer.ai/articles/voice-agent-cost-per-minute", "markdown": "https://changegamer.ai/articles/voice-agent-cost-per-minute.md", "json": "https://changegamer.ai/api/articles/voice-agent-cost-per-minute.json" }, { "slug": "guardrails-for-spoken-output-in-voice-agents", "title": "Voice Agent Guardrails: Checking What the Agent Says Before the Caller Hears It", "description": "Voice agent guardrails for spoken output: sentence-level gating before TTS, fail-closed judges, spoken numbers a text PII filter misses, readback before state changes, transcription-driven injection, refusal phrasing for the ear, and an adversarial test list.", "kind": "sub", "order": 8, "html": "https://changegamer.ai/articles/guardrails-for-spoken-output-in-voice-agents", "markdown": "https://changegamer.ai/articles/guardrails-for-spoken-output-in-voice-agents.md", "json": "https://changegamer.ai/api/articles/guardrails-for-spoken-output-in-voice-agents.json" }, { "slug": "voice-agent-online-monitoring", "title": "How to Monitor a Voice Agent in Production: Dashboard, Alerts and Runbook", "description": "How to monitor a voice agent in production: per-stage latency percentiles, transcription confidence, containment paired with a resolution signal, live false-interruption rate, a handoff trigger review, and call-audio retention, each with what to chart, alert on and do.", "kind": "sub", "order": 9, "html": "https://changegamer.ai/articles/voice-agent-online-monitoring", "markdown": "https://changegamer.ai/articles/voice-agent-online-monitoring.md", "json": "https://changegamer.ai/api/articles/voice-agent-online-monitoring.json" }, { "slug": "voice-agent-vendor-change-management", "title": "How to Handle Voice AI Vendor Model Changes Without Regressing Callers", "description": "How to handle voice AI vendor model changes: classify the change, record the model id on every trace, replay an offline set with hard calls on old and new, canary before cutover, keep a rollback, and run a deprecation-readiness routine.", "kind": "sub", "order": 10, "html": "https://changegamer.ai/articles/voice-agent-vendor-change-management", "markdown": "https://changegamer.ai/articles/voice-agent-vendor-change-management.md", "json": "https://changegamer.ai/api/articles/voice-agent-vendor-change-management.json" }, { "slug": "voice-agent-launch-checklist", "title": "Voice Agent Launch Checklist: The Go/No-Go Gates Before Real Callers", "description": "A voice agent launch checklist as yes/no gates: scope, offline replay, per-stage latency, barge-in, tools, transport, handoff, cost, guardrails, monitoring and rollback, each with a pass signal and the article that owns the method.", "kind": "sub", "order": 11, "html": "https://changegamer.ai/articles/voice-agent-launch-checklist", "markdown": "https://changegamer.ai/articles/voice-agent-launch-checklist.md", "json": "https://changegamer.ai/api/articles/voice-agent-launch-checklist.json" }, { "slug": "voice-agent-multilingual-callers", "title": "How Does a Voice Agent Handle Callers Who Speak Another Language?", "description": "How a live voice agent handles callers who speak another language: detecting the language, choosing speech components per language, slicing evaluation by language and handing off when the language is unsupported, with the thin corpus evidence stated plainly.", "kind": "sub", "order": 12, "html": "https://changegamer.ai/articles/voice-agent-multilingual-callers", "markdown": "https://changegamer.ai/articles/voice-agent-multilingual-callers.md", "json": "https://changegamer.ai/api/articles/voice-agent-multilingual-callers.json" } ] }, "navigation": { "pillar": { "slug": "voice-ai-agent-in-production", "title": "Voice AI Agent in Production: Architecture, Latency, Handoff and Launch", "description": "How to build and run a voice AI agent in production: cascaded vs speech-to-speech architecture, turn detection and barge-in, the latency budget, tool calls in a voice loop, transport, cost, human handoff and launch sequencing.", "kind": "pillar", "order": 0, "html": "https://changegamer.ai/articles/voice-ai-agent-in-production", "markdown": "https://changegamer.ai/articles/voice-ai-agent-in-production.md", "json": "https://changegamer.ai/api/articles/voice-ai-agent-in-production.json" }, "previous": { "slug": "voice-agent-vendor-change-management", "title": "How to Handle Voice AI Vendor Model Changes Without Regressing Callers", "description": "How to handle voice AI vendor model changes: classify the change, record the model id on every trace, replay an offline set with hard calls on old and new, canary before cutover, keep a rollback, and run a deprecation-readiness routine.", "kind": "sub", "order": 10, "html": "https://changegamer.ai/articles/voice-agent-vendor-change-management", "markdown": "https://changegamer.ai/articles/voice-agent-vendor-change-management.md", "json": "https://changegamer.ai/api/articles/voice-agent-vendor-change-management.json" }, "next": { "slug": "voice-agent-multilingual-callers", "title": "How Does a Voice Agent Handle Callers Who Speak Another Language?", "description": "How a live voice agent handles callers who speak another language: detecting the language, choosing speech components per language, slicing evaluation by language and handing off when the language is unsupported, with the thin corpus evidence stated plainly.", "kind": "sub", "order": 12, "html": "https://changegamer.ai/articles/voice-agent-multilingual-callers", "markdown": "https://changegamer.ai/articles/voice-agent-multilingual-callers.md", "json": "https://changegamer.ai/api/articles/voice-agent-multilingual-callers.json" } }, "resources": [ { "slug": "voice-realtime-agents", "html": "https://changegamer.ai/resources/voice-realtime-agents", "markdown": "https://changegamer.ai/resources/voice-realtime-agents.md", "json": "https://changegamer.ai/api/resources/voice-realtime-agents.json" }, { "slug": "evaluating-voice-agents", "html": "https://changegamer.ai/resources/evaluating-voice-agents", "markdown": "https://changegamer.ai/resources/evaluating-voice-agents.md", "json": "https://changegamer.ai/api/resources/evaluating-voice-agents.json" }, { "slug": "customer-support-agents", "html": "https://changegamer.ai/resources/customer-support-agents", "markdown": "https://changegamer.ai/resources/customer-support-agents.md", "json": "https://changegamer.ai/api/resources/customer-support-agents.json" }, { "slug": "agent-observability", "html": "https://changegamer.ai/resources/agent-observability", "markdown": "https://changegamer.ai/resources/agent-observability.md", "json": "https://changegamer.ai/api/resources/agent-observability.json" } ] }