> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Meta Business Agent

> The AI that Meta runs natively inside WhatsApp, connected to your Jelou workflows and tools to resolve real cases.

**Meta Business Agent (MBA)** is the AI that **Meta** runs natively inside WhatsApp. It serves your customer directly in the chat, without Jelou mediating the conversation.

What Jelou adds is the ability to **execute real actions**: by connecting your workflows and tools, the agent stops merely replying and starts resolving — checking an order status, verifying someone's identity, generating a payment request.

## When to use it

Meta Business Agent is a good fit when:

* You want a first line of support inside WhatsApp that answers immediately, without building a full conversational flow.
* You already have workflows and tools in Jelou that resolve specific cases and you want to expose them to that automated support.
* You need the conversation to be able to pass to a human operator with full context when the customer asks for it.

## It does not replace Jelou's AI Agent

These are two different products and they can coexist.

|                              | Meta Business Agent                  | Jelou AI Agent                    |
| :--------------------------- | :----------------------------------- | :-------------------------------- |
| Who runs it                  | Meta, inside WhatsApp                | Jelou, inside your flows          |
| Where the conversation lives | In the WhatsApp chat                 | In the Brain Studio workflow      |
| How it is configured         | Per channel, in the project settings | As an AI Agent node in a workflow |
| Flow control                 | Defined by Meta's agent              | Defined by you in the flow design |

You can have one, the other, or both on different channels. The choice is not mutually exclusive.

<Note>
  If you need fine-grained control over the conversation path (step-by-step validations, branching, specific templates), the **AI Agent** node inside a workflow is still the right tool. See the [AI Agents guide](/en/guides/agentes-ia/index).
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Requirements and activation" icon="circle-check" href="/en/guides/meta-business-agent/requisitos-y-activacion">
    What you need before activating and how to get it running.
  </Card>

  <Card title="Configuration" icon="gear" href="/en/guides/meta-business-agent/configuracion">
    Instructions, audience, tools and operator handoff.
  </Card>

  <Card title="Costs" icon="credit-card" href="/en/guides/meta-business-agent/costos">
    How the agent's usage is billed.
  </Card>

  <Card title="Limits and verticals" icon="ban" href="/en/guides/meta-business-agent/limites-y-verticales">
    Meta's limits and the enabled verticals.
  </Card>
</CardGroup>