Relayiq — DevOps skill for Claude Code

RelayIQ v1 — AWS-native voice agentic customer care

A production-pattern voice AI agent for telecom customer care (modeled on an AT&T / T-Mobile support line), built **entirely on AWS services**: Amazon Connect for the contact center, Chime SDK Voice Connector for the SIP trunk / session border control layer, Lex V2 for speech capture, Bedrock for the LLM, guardrails and knowledge base, Lambda for orchestration, OpenSearch Serverless for retrieval.

**Status: deployed and tested end-to-end on a live toll-free number, September 2026.** Guardrails, PII redaction, RAG over the policy corpus, tool calls, and escalation all verified from a real phone call. See "Lessons from the first real deployment" at the bottom of `docs/DEPLOYMENT.md` for what broke on the way and how each was fixed.

Architecture

PSTN caller
   |
   v
Amazon Connect (claims the number; AWS is the carrier)
   |   contact flow: greet -> Lex turn -> check action -> loop | escalate
   v
Amazon Lex V2 bot  <- ASR via Transcribe, replies played via Polly
   |   every utterance -> AMAZON.FallbackIntent fulfillment hook
   v
Lambda orchestrator
   |-- Bedrock Guardrails (input)  + Comprehend PII redaction
   |-- LangGraph ReAct agent on Bedrock Claude
   |     |-- lookup_account / lookup_billing / lookup_outage  -> API Gateway + Lambda mocks
   |     |-- search_policy_kb  -> Bedrock Knowledge Base on OpenSearch Serverless
   |     |-- escalate_to_human
   |-- Bedrock Guardrails (output)
   v
Spoken reply, or transfer to the live-agent queue

Chime SDK Voice Connector: optional (`enable_voice_connector`), provisioned
alongside to demonstrate the SIP/SBC layer (TLS/SRTP enforced, streaming to
EventBridge, termination allow-list). Off by default because many AWS
accounts need a support case to enable the service; the call path doesn't
depend on it.

Repo layout

infra/               Terraform: Connect, Lex V2, Voice Connector, Lambda (via S3),
                     Bedrock Guardrail + Knowl