> 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/docs/docs_se/referens/references/what-happens-when-i-reach-my-contact-limit.md).

# Vad händer när jag når min kontaktgräns?

eMarketeers betalplaner storleksbestäms efter antalet kontakter du kommunicerar med, så din plan sätter storleken på din kontaktdatabas.

### Vad händer vid kontaktgränsen

När du når gränsen för kontaktdatabasen kan du inte skapa nya kontakter i kontot. Nya formulärinskick avvisas, filimporter listar kontakter som avvisade, och publicerade formulär stängs och visar ett felmeddelande.

### Så vet du att du närmar dig gränsen

För att undvika att kontot pausas skickar vi varningar när du närmar dig gränsen. Den första varningen går ut vid 90 % av kapaciteten. Varningarna når användarna på ditt konto via e-post och som chattmeddelanden inuti eMarketeer.

### Så skapar du nya kontakter igen

Få kontot tillbaka under gränsen genom att ta bort kontakter eller uppgradera planen. Kontakta oss via chatten i eMarketeer eller [via e-post](mailto:customerservice@emarketeer.com) om du vill uppgradera.

När du är under gränsen igen börjar formulär och filimporter fungera inom några minuter.


---

# 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/docs/docs_se/referens/references/what-happens-when-i-reach-my-contact-limit.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.