> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform.md).

# What are the differences between Batch Customer Engagement Platform and Mobile Engagement Platform?

Learn about Batch's positioning and the features of our two commercialized platforms: CEP and MEP.

CEP and MEP are two different platforms that meet two distinct use cases.

* The **Customer Engagement Platform** (CEP): ideal for marketing teams managing the CRM of the company as a whole.
* The **Mobile Engagement Platform** (MEP): ideal for marketing teams managing the CRM of mobile applications.

## Customer Engagement Platform

The CEP has been designed to simplify the work of marketers by offering an all-in-one CRM platform that combines email, SMS, and mobile push within a single B2C marketing automation solution.

CEP features include:

* **Email & SMS** **channels** in addition to **Mobile Push, Web Push, and In-App Messaging**.
* **Projects:** Mobile apps and websites can be grouped and targeted in a single project to orchestrate omnichannel communications.
* **Profiles**: a unified CRM view that handles both anonymous users and logged-in users equally, giving a complete picture of all their associated data.
* **The Automation Builder:** a visual drag-and-drop interface to build sophisticated multi-step, multi-branch, and multichannel customer lifecycle flows.

***

## Mobile Engagement Platform

The MEP, marketed by Batch since 2015, is a mobile-focused engagement platform including these channels:

* **Mobile Push Notifications**
* **Web Push Notifications**
* **In-App Messaging**
* **Inbox**

***

## Am I using Batch CEP or MEP?

Here is the simplest way to know if you're using Batch CEP or MEP:

### CEP dashboard:

On the CEP, apps and websites are grouped into projects.\
Projects are listed on the top left corner of the dashboard:

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FyU8oJHbQYCExeLscIgLM%2FBatchCEP.png?alt=media&amp;token=179e6929-4a03-4fdc-bc7f-3a1ba99b0e7f" alt=""><figcaption><p>Batch Customer Engagement Platform dashboard</p></figcaption></figure>

### MEP dashboard:

On the MEP, apps and websites are listed on the left side of the dashboard:

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FNBTYhmDcYrYMtCOUTNWH%2FBatchMEP2.png?alt=media&amp;token=b0a00bbc-afbf-470d-9fc9-b014b35fdda0" alt=""><figcaption><p>Batch Mobile Engagement Platform dashboard</p></figcaption></figure>

***

## How to access the CEP from the MEP dashboard?

Once the CEP has been activated for your account, you can access it directly from the MEP dashboard:

1. Log in to the Batch dashboard.
2. Click the **Switch to CEP** button in the upper-right corner of the navigation bar:&#x20;

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FKtlaItiigkpBkCT4KHhk%2FCleanShot%202026-10-21%20at%2014.12.39%402x.png?alt=media&amp;token=32c0c8fe-13d0-4a58-b231-cc164c3db9ee" alt=""><figcaption></figcaption></figure>

You will then land on the CEP dashboard, where your apps and websites are grouped into projects. Use the project selector in the upper-left corner to choose the project you want to work on.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/getting-started/other/faq/what-are-the-differences-between-batch-customer-engagement-platform-and-mobile-engagement-platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.