# Amazon — Build WhatsApp AI agents with Amazon Bedrock AgentCore

- Company: Amazon (amazon.com)
- Announced: 2026-11-17T18:48:50+00:00
- Category: developer-tool-release
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/build-whatsapp-ai-agents-with-amazon-bedrock-agentcore/
- Record: https://forck.live/items/37444-build-whatsapp-ai-agents-with-amazon-bedrock-agentcore
- Subject: Bedrock / Nova

Amazon's AWS blog presents SMART, an open source Python SDK and Terraform stack that supplies the WhatsApp channel layer for AI agents already running on Amazon Bedrock AgentCore. The post argues the agent is rarely the hard part: inbound messages arrive as deeply nested, type-dependent payloads that must be authenticated and normalized, and media such as voice notes, images and documents each need their own processing pipeline. Wiring the channel up otherwise means configuring more than 10 AWS services, and anything sent more than 24 hours after the user's last message must use a pre-approved Meta message template. SMART deploys the whole infrastructure to a customer's AWS account with one command, and the contract with the agent is deliberately small: the agent receives the inbound message and returns text, optionally with rich message attachments. AgentCore runtime hosts and scales the agent, while AgentCore memory persists conversation history scoped to each phone number, with a 7-day default retention period. Because AgentCore is framework-agnostic, Strands Agents gets memory wired automatically and LangGraph or Pydantic-AI can integrate too. Webmotors, originally scoped as a two-month engagement, compressed delivery to six weeks and moved its internal team into controlled production ahead of a full launch.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/build-whatsapp-ai-agents-with-amazon-bedrock-agentcore/:

> Across Latin America, India, and Southeast Asia, WhatsApp is one of the most widely used messaging applications. That makes it an obvious place to build an AI agent. For many end users, it is how they expect to interact with businesses. However, it is also a genuinely difficult surface to build for, even when your agent already runs on Amazon Bedrock AgentCore .
> 
> The agent is rarely the hard part. The integration is. Inbound messages arrive as deeply nested, type-dependent payloads that must be authenticated and normalized before your agent can read them. Media such as voice notes, images, and documents each require their own processing pipeline. Beyond message handling, you need conversation memory that survives sessions, durable schedules for reminders, and an authenticated path for external systems to trigger outbound messages. And anything you send more than 24 hours after the end user’s last message must use a pre-approved Meta message template.
> 
> Wiring that up means configuring more than 10 AWS services and learning a set of WhatsApp system behaviors that most teams discover only by hitting them. None of it is visible to a customer, but all of it has to work.

---

Record: https://forck.live/items/37444-build-whatsapp-ai-agents-with-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
