/aws-sms-voice

name: aws-sms-voice
description: >
  Onboards RCS Business Messaging and Notify OTP via the pinpoint-sms-voice-v2
  AWS CLI. Covers creating a branded RCS test agent (logo, banner, rich cards,
  suggested replies), adding verified testers, and sending/receiving the first RCS
  message; and configuring AWS End User Messaging Notify to send one-time-passcode
  (OTP) verification codes through AWS-managed phone numbers without buying a
  number or completing carrier registration. Also discovers which registration type a
  country requires from live API definitions and runs the universal registration
  lifecycle (create, derive fields, fill, submit, recover from denial, resubmit) shared
  by 10DLC, toll-free, short code, sender ID, RCS country launch, and Notify tier
  upgrade. Applicable to RCS agent setup, RCS message send/receive, Notify OTP
  configuration, verification-code delivery, registration requirements by country, and
  registration submission. Does not cover WhatsApp (see aws-social-messaging).
version: 1

AWS End User Messaging — SMS, Voice, RCS & Notify

Overview

AWS End User Messaging SMS and Voice (the `pinpoint-sms-voice-v2` API) is the control and data plane for SMS, Voice, RCS Business Messaging, and Notify (OTP). This skill covers the two fastest onboarding paths — each reaches a real message on a real phone in about five minutes, with no phone-number purchase and no carrier registration:

1. **Create an RCS test agent and send your first branded message** — a branded RCS Business Messaging agent, a verified test device, and a rich outbound + inbound message. See [references/hello-rcs-test-agent.md](references/hello-rcs-test-agent.md). 2. **Send an OTP with Notify** — a one-time-passcode text through AWS-managed sending identities and pre-approved templates. See [references/hello-notify-otp.md](references/hello-notify-otp.md).

Beyond onboarding, this skill takes an identity to production registration in three steps:

1. **Find which registration a country requires** — discover the registration type and its live field set for a target country and identity type, reconciled with the official docs. See [references/registration-requirements-by-country.md](references/registration-requirements-by-country.md). 2. **Run the registration lifecycle** — the universal engine (create, derive fields, fill, submit, poll, recover from denial, resubmit) shared by every registration type, including RCS country launch. See [references/registration-core-engine.md](references/registration-core-engine.md). 3. **Take an identity to production** — exit the SMS sandbox, launch RCS in a country with carrier monitoring and SMS fallback, upgrade Notify to Advanced, and apply production hygiene (keywords, configuration sets, protect configurations). See [references/customer-go-to-production-guide.md](references/customer-go-to-production-guide.md).

Guardrail — where this skill's files live (MCP vs local install)

This skill can be loaded two ways, and the `references/` files resolve differently:

• **Loaded through the AWS MCP `retrieve_skill` tool.** Reference files do not

exist on the local filesystem. Fetch them via `retrieve_skill` with the `file` parameter (e.g., `file="references/hello-rcs-test-agent.md"`). Do NOT `file_read` these paths locally — they are not there.

• **Installed locally** (e.g., `.kiro/skills/aws-sms-voice/`). Read references

from the local skill directory using the relative paths shown in this file.

This applies only to the skill's own packaged files. User-created artifacts (brand-assets/, temp files) are always in the user's working directory.

Execute commands using available tools from the AWS MCP server when connected — it provides sandboxed execution, audit logging, and observability. When the MCP server is not available, fall back to the AWS CLI or shell as needed.

Choosing a path

| You want to… | Go to | |---|---| | Send rich, branded messages (cards, logo, two-way) to your own test phone | [hello-rcs-test-agent.md](references/hello-rcs-test-agent.md) | | Send a verification code / OTP to any supported phone, fastest possible path | [hello-notify-otp.md](references/hello-notify-otp.md) | | Find out which registration a country needs and what fields it requires | [registration-requirements-by-country.md](references/registration-requirements-by-country.md) | | Create and submit a registration of any type (10DLC, toll-free, sender ID, RCS launch, Notify tier) | [registration-core-engine.md](references/registration-core-engine.md) | | Take an identity to production (sandbox exit, RCS carrier launch + fallback, Notify Advanced, hygiene) | [customer-go-to-production-guide.md](references/customer-go-to-production-guide.md) |

RCS test agents deliver **only to verified test devices** and require a short brand registration (auto-reviewed in minutes). Notify sends to any recipient in its supported countries immediately, but is limited to AWS-managed OTP templates. Pick RCS to explore rich messaging; pick Notify for the shortest path to a production-grade verification text.

Before you start (both paths)

The **AWS MCP server is recommended** for the best experience here — it runs the many `pinpoint-sms-voice-v2` and `sts` calls with sandboxed execution, audit logging, and observability. It is not a hard requirement: every step also works with the plain AWS CLI or the AWS Agent Toolkit when the MCP server is not available.

1. **Credentials.** Run `aws sts get-caller-identity --region <REGION>` (pass `--region` to use the regional STS endpoint; the global `sts.amazonaws.com` endpoint is legacy). If it fails, configure the user's auth (named profile / SSO / access keys — `--profile <PROFILE>` on every command if a profile is in play) and prefer an assumed IAM role with ephemeral credentials. Each reference file's Prerequisites carry the full auth, CloudTrail-audit, and CLI-freshness steps. 2. **Least-