Update content to change language to client-facing, update quickstart

content/docs/agents/get-started/what-is-aci.mdx

@@ -6,26 +6,35 @@
 ---
 
 import { BookText, HomeIcon } from 'lucide-react';
+
+Agent Communication Infrastructure (ACI) is the communication layer that connects agents to the messaging platforms where people already work, collaborate, and talk to businesses.
 
-Agent Communication Infrastructure (ACI) is a protocol-driven infrastructure layer for enabling structured, stateful communication between autonomous agents and your users across messaging platforms.
+ACI sits between communication channels and your agent logic. Instead of building separate integrations for each platform, ACI gives your agent one communication interface for inbound messages, outbound replies, conversation state, user identity, and delivery across:
 
-ACI sits between messaging platforms and your agent logic. Instead of building separate integrations for each channel, ACI provides a unified interface for webhooks, message delivery, conversation state, and subscriber identity.
+* Slack
+* Microsoft Teams
+* WhatsApp
+* Email
+* Telegram
+* Other supported platforms
 
-The agent itself can be powered by an LLM, custom code, a rules engine, a human-in-the-loop workflow, or a combination of systems or Platform managed agents like [Claude Managed Agent](https://platform.claude.com/docs/en/managed-agents/overview), [ AWS Bedrock AgentCore](https://aws.amazon.com/bedrock/agentcore/) and many more. ACI doesn't define the agent’s intelligence. It defines the communication infrastructure around it.
+The agent brain can be powered by an LLM, custom code, a rules engine, a human-in-the-loop workflow, a managed agent platform, or a combination of systems. ACI does not define the agent’s intelligence. It defines the communication infrastructure around it.
+
+That means you can build an agent that your team uses internally, expose an agent to your product users, or create a customer-facing agent that lives in the channels your customers already use.
 
 ## What does ACI solve?
 
-Software is becoming more conversational. Users no longer only click through interfaces or receive one-way notifications. They ask questions, reply to messages, clarify requests, approve actions, send files, react with emojis, and expect software to continue the conversation in channels where they already are.
+Software is becoming more conversational. People no longer only click through interfaces or receive one-way notifications. They ask questions, reply to messages, clarify requests, approve actions, send files, react with emojis, and expect software to continue the conversation in the channels where they already are.
 
-At the same time, agents are becoming more capable. And most teams already have agents that answers users questions, analyze information, trigger workflows, escalate issues, and coordinate with other systems.
+At the same time, agents are becoming more capable. Teams are building agents that answer questions, analyze information, trigger workflows, escalate issues, and coordinate with other systems.
 
-In most cases, these agents only work inside one platform, getting these agents into a different platform requires rebuilding the communication layer from scratch.
+The problem is that most agents are still trapped inside one interface. Moving the same agent into Slack, Microsoft Teams, WhatsApp, email, Telegram, or another channel usually means rebuilding the communication layer for each platform.
 
-This creates an infrastructure problem where each channel has its own webhook format, identity model, threading behavior, permissions, message formatting, interaction patterns, and delivery constraints. Teams that want to expose an agent across Slack, Microsoft Teams, WhatsApp, email, or other channels often end up rebuilding the same communication plumbing for every channel.
+Each channel has its own webhook format, identity model, threading behavior, permissions, message formatting, interaction patterns, and delivery constraints. Without a shared communication layer, teams end up rebuilding the same infrastructure every time they want an agent to reach a new audience.
 
-ACI exists to standardize that layer. It separates the communication layer from the agent logic, so teams can connect agents to different messaging platforms without hand-building every channel integration from scratch.
+ACI standardizes that layer. It separates communication infrastructure from agent intelligence, so you can connect an agent to multiple messaging platforms without hand-building every channel integration from scratch.
 
-You create your agent once. ACI handles delivery everywhere. The goal isn't only to send messages but to let agents hold useful conversations across channels while preserving context, control, and visibility.
+You create the agent once. ACI handles communication across connected channels. The goal is not only to send messages, but to let agents hold useful conversations while preserving context, control, and visibility.
 
 ## How ACI works
 
@@ -35,31 +44,48 @@
 
 ### Communication channels
 
-Communication channels are the places where users interact with the agent, such as Slack, Microsoft Teams, WhatsApp, Telegram, and more. When a user sends a message on any of these platforms, it enters the ACI layer.
+Communication channels are the places where people interact with the agent:
+
+* Slack
+* Microsoft Teams
+* WhatsApp
+* Telegram
+* Email
+* Other supported platforms
+
+When a user sends a message in one of these channels, the message enters the ACI layer.
 
 ### Bridge
 
-The bridge is the infrastructure layer in the middle. It receives the platform webhook, normalizes the message into a standard format, and resolves the user's identity. 
+The bridge is the infrastructure layer between the communication channel and the agent's brain.
 
-It creates or loads the conversation with its full history, and forwards everything to your server as a single context object.
+It receives the platform webhook, normalizes the message into a standard format, and resolves the user's identity. It then creates or loads the conversation, attaches the relevant conversation history, and forwards the message to your configured agent brain as context.
 
-When your agent replies, the bridge delivers the response back to the correct platform thread, persists it in the conversation history, and records the activity. 
+When the agent replies, the bridge delivers the response back to the correct platform, thread, or conversation. It also persists the response in the conversation history and records the activity for observability.
 
-### Agent brain
+### Agent
 
-The agent brain is either Custom code agent or Managed agent.
+The agent's brain is the system that decides how to respond. ACI supports different kinds of agents, including custom code agents and managed agents.
 
-In case of Custom code agent, you can build agent brain with your custom code using agent sdk, lanchain etc. Your server receives the context object and processes it however you decide. Call an LLM, run business logic, route to a human, or combine all three.
+For a custom code agent, your server receives the context object and processes it however you decide. You can call an LLM, run business logic, use external APIs, route the conversation to a human, or combine multiple systems. You can build the agent brain with the Novu agent SDK, AI SDK, LangChain, OpenAI SDK, or any custom code of your choosing.
 
-In case of Managed agent, platfrom like Claude manages the agent intelligence, it provides, system tools like grep, web search, connection to external tools like linear, notion using MCP.
+For a managed agent, you configure the agent's behavior, system prompt, tools, skills, and external connections. The managed platform runs the agent harness and executes the agent loop, while ACI handles the communication layer between the managed agent and your connected channels.
 
-The channel-agnostic nature of this architecture means that when you connect a new provider, your agent implementation doesn't change. Not a single line of code. The same brain that responds on Slack will respond on Microsoft Teams, WhatsApp, or email without modification.
+Because the agent brain is separate from the channel layer, your agent does not need channel-specific logic for each connected provider. The same agent can respond through the ACI bridge across:
 
-## What ACI handles vs. what you control
+* Slack
+* Microsoft Teams
+* WhatsApp
+* Email
+* Telegram
+* Other supported channels
 
-ACI draws a clear boundary between infrastructure and intelligence.
 
-### The infrastructure handles
+## What ACI handles and what you control
+
+ACI draws a clear boundary between communication infrastructure and agent intelligence.
+
+### ACI handles
 
 * Webhook ingestion and message normalization across all connected platforms.
 * Message delivery to the correct platform thread.
@@ -70,21 +96,23 @@
 
 ### You control
 
-In case of _Custom code agent_, you control:
+For a custom code agent, you control:
 
 * Your LLM, prompts, and model configuration.
 * Your tools and function calls.
 * Your business logic and decision-making.
 * Your API keys and credentials.
 * Your choice of runtime, which can be managed agents, Vercel AI SDK, LangChain, OpenAI SDK, or any custom code of your choosing.
 
-In case of _Managed agent_, platform like Claude controls:
+For a managed agent, you configure:
 
+- The agent's instructions and behavior.
 - MCP servers and their configuration.
-- The agent's tools and their configuration.
-- The agent's business logic and decision-making.
+- The agent's tools, skills and their configuration.
+- The external systems the agent can access.
+- The guardrails or constraints supported by the managed platform.
 
-ACI is opinionated about infrastructure and unopinionated about intelligence. It handles the delivery problem so you can focus on the capability problem.
+ACI is opinionated about communication infrastructure and unopinionated about intelligence. It handles the communication problem so you can focus on what your agent should do.
 
 ## Common use cases
 
@@ -102,6 +130,8 @@
 
 ## Start building
 
+Follow the quickstart to create your first agent, connect a Slack provider, and send your first message in under five minutes.
+
 <Cards>
   <Card
     href="/agents/custom-code-agent/concepts"

content/docs/agents/index.mdx

@@ -0,0 +1,84 @@
+---
+title: "Overview"
+pageTitle: "Agents"
+description: "Connect your AI agents to chat platforms and communication channels with Novu's Agent Communication Infrastructure (ACI)."
+icon: Plug
+---
+
+import { Code2, Sparkles, BrainCircuit, Blocks, MessagesSquare, CircleHelp, Zap } from 'lucide-react';
+
+Novu Connect is built on the [Agent Communication Infrastructure (ACI)](/agents/get-started/what-is-aci), the infrastructure layer that handles how agents communicate, so your agents can hold real conversations across messaging platforms with users, on the channels they already use.
+
+ACI draws a hard boundary between two concerns:
+
+* **Communication infrastructure**: Webhook ingestion, message normalization, conversation state, identity resolution, and delivery across channels. ACI owns this layer.
+
+* **Agent intelligence**: Your LLM, prompts, tools, managed agent configuration, business logic, or custom runtime. You own this layer.
+
+The result is that you can create an agent once and make it available across connected channels. ACI routes messages in, sends replies out, preserves conversation context, and removes the need to rebuild communication plumbing for every platform.
+
+<Card href="/agents/get-started/what-is-aci" title="What is ACI?" icon={<CircleHelp />}>
+  Learn how ACI works, what it solves, and where it draws the line between infrastructure and intelligence.
+</Card>
+
+## Connect the agent
+
+Novu Connect accepts two kinds of [agent brains](/platform/additional-resources/glossary#agent-brain). You choose how you want to bring it.
+
+### External connectors
+
+Delegate the agent logic entirely to a managed platform such as Claude Managed Agents. You configure the agent's behavior, system prompt, tools, skills, and MCP servers and the platform runs the intelligence.
+
+<Card href="/agents/managed-agent/overview" title="Managed agent" icon={<Sparkles />}>
+  Set up a fully managed agent powered by Claude. No custom server code required.
+</Card>
+
+### Custom code
+
+Write your own agent logic. Handle events, call any LLM or API, and reply using the Novu agent SDK. Compatible with AI SDK, LangChain, OpenAI SDK, and any custom code of your choosing.
+
+<Card href="/agents/custom-code-agent/quickstart" title="Custom code agent" icon={<Code2 />}>
+  Build an agent with full control over logic, tools, and event handling.
+</Card>
+
+## How a conversation flows
+
+ACI turns channel-specific messages into a standard communication flow between the user and your agent brain.
+
+1. A user sends a message on Slack, Teams, WhatsApp, or another supported channel.
+2. Novu ingests the webhook, normalizes the event, and resolves the user's identity.
+3. Novu sends the event to your agent brain with full conversation context.
+4. Your agent processes the message and responds. 
+5. Novu delivers the reply back to the correct platform thread.
+6. Novu persists the conversation and makes it visible in the Connect dashboard.
+
+## Start building
+
+<Card href="/agents/managed-agent/quickstart" title="Quickstart" icon={<Zap />}>
+  Follow the quickstart to create your first agent, connect a Slack provider, and send your first message in under 5 minutes.
+</Card>
+
+## Learn more
+
+Explore the full documentation to go deeper on any part of Novu Connect.
+
+<Cards>
+  <Card href="/agents/get-started/what-is-aci" title="What is ACI?" icon={<CircleHelp />}>
+    Understand the infrastructure layer and the problem it solves.
+  </Card>
+  <Card href="/agents/get-started/mental-model" title="Mental model" icon={<BrainCircuit />}>
+    How inbound messages flow from a channel through to your agent and back.
+  </Card>
+  <Card href="/agents/get-started/agents-and-providers" title="Agents and providers" icon={<Blocks />}>
+    How agents and provider connections work, and which channels are supported.
+  </Card>
+  <Card href="/agents/managed-agent/overview" title="Managed agent" icon={<Sparkles />}>
+    Configure a fully-managed agent powered by Claude.
+  </Card>
+  <Card href="/agents/custom-code-agent/quickstart" title="Custom code quickstart" icon={<Zap />}>
+    Connect a Slack provider and send your first message in under five minutes.
+  </Card>
+  <Card href="/agents/conversations" title="Conversation observability" icon={<MessagesSquare />}>
+    Monitor, inspect, and manage live agent conversations.
+  </Card>
+</Cards>