> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/ai-assistants.md).

# AI assistants

Connect Claude or ChatGPT to your eMarketeer account and ask about your marketing in plain language.

Connect Claude or ChatGPT to your eMarketeer account and ask about your marketing in plain language.

The assistant works with your real data: reports, contacts, journeys, campaigns and forms. It reads from the accounts you belong to. Every user on an account can read this data through the connector, whatever their role in eMarketeer.

## What you can do

Ask about your results, look up contacts and check how your journeys are running. Marketing Users and Administrators can also ask the assistant to make changes, such as creating a campaign or closing a form.

## Examples

Write to the assistant the way you would ask a colleague.

### Reports

* How did our emails perform last month compared with the month before?
* Which pages on our website got the most visits this week?
* Export last quarter's email results as a spreadsheet.

### Contacts

* Give me a short brief on <anna@example.com> before my sales call.
* Why is <anna@example.com>'s lead score so high?
* Has <anna@example.com> agreed to receive emails?

### Journeys

* Are any of our journeys failing? What's going wrong?
* Who is waiting in the second step of the onboarding journey?

### Campaigns and forms

* Create a campaign called Spring webinar in the Events folder.
* Show how many people chose each answer in our customer survey form.
* Close the registration form for the June event.

### Planning

* Suggest our next campaign based on what has worked recently.
* Check our email deliverability and tell me what to fix.

## Who can do what

| What                                                                                                       | Who                                                |
| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Read reports, contacts, journeys, campaigns and forms                                                      | Every user                                         |
| Change things: tags, notes, segments, campaigns, starting or restarting journeys, opening or closing forms | Marketing Users and Administrators on that account |

If you don't have one of these roles on any of your accounts, the assistant doesn't offer these actions at all.

## Changes the assistant can make

These are the only changes the assistant can make. Everything else is read-only.

### Contacts

* Add an existing tag to a contact, or remove one. The assistant can't create new tags.
* Write a note on a contact's card, signed with your name.

### Segments

* Save a new segment from a set of filters. Saving a segment doesn't change any contacts.

### Journeys

* Add one contact to a journey that can be started manually. The journey then runs its own steps, which can include sending an email or a text message.
* Restart contacts who got stuck at a step: named contacts, everyone at one step, or everyone in the journey.
* Take one contact out of a journey, so they receive nothing more from it.

### Campaigns

* Create a new, empty campaign.
* Rename a campaign or change its description.
* Move a campaign to a folder.
* Add an email, form, page or text message to a campaign as a copy of a template. Nothing is sent, and you edit the content in eMarketeer afterwards.

### Forms

* Open or close a form, including the closed message, an automatic close date and a maximum number of responses.

### What the assistant can't do

* Send or schedule a campaign.
* Delete anything.
* Edit the content of emails, forms or pages.
* Change contact details or import contacts.

## Supported assistants

Claude works on claude.ai and in the Claude desktop app. See [Connect Claude to eMarketeer](/integrations/ai-assistants/connect-claude.md).

ChatGPT works on chatgpt.com. See [Connect ChatGPT to eMarketeer](/integrations/ai-assistants/connect-chatgpt.md).

## Next steps

{% columns %}
{% column %}
{% content-ref url="/pages/x57E6RoA3ftEdrlVdDwz" %}
[Connect Claude to eMarketeer](/integrations/ai-assistants/connect-claude.md)
{% endcontent-ref %}

{% content-ref url="/pages/80ztWvNh5BclgXBze0Jn" %}
[Connect ChatGPT to eMarketeer](/integrations/ai-assistants/connect-chatgpt.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
{% content-ref url="/pages/pqSm6LroBwnQDhKdSmzV" %}
[AI assistants: data and privacy](/integrations/ai-assistants/data-and-privacy.md)
{% endcontent-ref %}

{% content-ref url="/pages/xWMgOxNEVEJ1NJlqxPLb" %}
[AI assistants: troubleshooting](/integrations/ai-assistants/troubleshooting.md)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}


---

# 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://support.emarketeer.com/integrations/ai-assistants.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.
