> 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/references/references/what-happens-when-i-reach-my-contact-limit.md). # What happens when I reach my contact limit? eMarketeer pay plans are sized by the number of contacts you communicate with, so your plan sets the size of your contact database. ### What happens at the contact limit When you reach the contact database limit, you can't create new contacts in the account. New form submissions are rejected, file imports list contacts as rejected, and published forms close and show an error message. ### How you know you're approaching the limit To avoid pausing the account, we send warnings as you get close to the limit. The first warning goes out at 90% of capacity. Warnings reach the users on your account by email and as chat messages inside eMarketeer. ### How to create new contacts again Bring the account back under the limit by removing contacts or upgrading the plan. Contact us through the chat in eMarketeer or [by email](mailto:customerservice@emarketeer.com) if you want to upgrade. Once you're under the limit again, forms and file imports start working within minutes. --- # 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/references/references/what-happens-when-i-reach-my-contact-limit.md?ask=&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.