> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/sms/sms-campaigns/analytics-audiences-and-reports/archiving-recipients-removing-recipients-with-error-status.md). # Archiving recipients, removing recipients with ERROR status To manually add a contact to the archive, first go to the contact list, select the contact, and then check the checkbox. After selecting the contact, simply click the **Archive** button to move the selected address or number to the archive. This ensures that these addresses will not be considered for future campaigns. Additionally, after every sent SMS campaign, the report provides an option to archive undelivered messages. This functionality allows for the automatic transfer of addresses that received the **ERROR** status (for SMS) to the archive. Addresses that have been moved to the archive due to **ERROR** are automatically excluded from future sends and will not be accepted when importing new data. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.messageflow.com/sms/sms-campaigns/analytics-audiences-and-reports/archiving-recipients-removing-recipients-with-error-status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.