# Amazon — How MoEngage built agentic customer engagement on Amazon Bedrock AgentCore

- Company: Amazon (amazon.com)
- Announced: 2026-11-16T18:16:07+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/how-moengage-built-agentic-customer-engagement-on-amazon-bedrock-agentcore/
- Record: https://forck.live/items/36811-how-moengage-built-agentic-customer-engagement-on-amazon-bedrock-agentcore
- Subject: Bedrock / Nova
- Models affected: Claude Sonnet 4.6, Claude Sonnet 5, Claude Sonnet 5.5

MoEngage built Merlin AI, a set of agents that work on live platform data, on Amazon Bedrock and Amazon Bedrock AgentCore, and exposed its existing APIs as MCP tools so assistants such as Claude or ChatGPT can reach a brand's data. The company says more than 1,350 consumer brands use its platform across push, email, in-app, SMS, WhatsApp and RCS. The MoEngage MCP Connector gives an MCP-compatible assistant secure, tenant-scoped access to a brand's segments, campaign history and content library, which MoEngage treated as an architecture problem: how to grant that access without rebuilding hundreds of existing APIs. Merlin AI runs four agent modes, embedded agents in Merlin AI Studio, conversational agents, custom agents and decisioning agents, all sharing foundation models in Amazon Bedrock, AgentCore runtime for hosting and MCP for data access. Across all four modes it uses Anthropic Claude Sonnet 4.6, Claude Sonnet 5 and Claude Sonnet 5.5 on Amazon Bedrock for reasoning, tool-call planning and content generation. MoEngage says customer Glance saw a 38% uplift in push notification click-through rates as a result.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/how-moengage-built-agentic-customer-engagement-on-amazon-bedrock-agentcore/:

> This post was co-written with Ashwin Srinivasan, Nishan Das and Karthik Baile from MoEngage.
> 
> A marketing or product team member planning a weekend flash sale often opens three tools before writing a single line of copy. First they open the analytics dashboard to see what worked last time, then the content library to find the right tone, and then the campaign builder to build the campaign itself. Repeat that across email, push, SMS, and WhatsApp, and much of a marketing team’s week goes to navigating tools instead of making decisions.
> 
> The MoEngage Model Context Protocol (MCP) Connector gives an MCP-compatible assistant, such as Claude or ChatGPT, secure, tenant-scoped access to a brand’s segments, campaign history, and content library.
> 
> This capability points to a broader shift in software platforms. Beyond a user interface for business users and an API for engineering teams, a third layer is emerging, where a user describes an outcome in plain language and an agent carries out the steps across the platform.

---

Record: https://forck.live/items/36811-how-moengage-built-agentic-customer-engagement-on-amazon-bedrock-agentcore
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
