> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/get-started/readme.md). # What is Missive? Missive is the collaborative email client built for teams. Manage email, SMS, WhatsApp, and more in one shared inbox. Missive is the collaborative email client built for teams. Work together on shared inboxes, discuss emails internally, and respond across email, SMS, WhatsApp, and more from one place. ## How teams use Missive * Share email accounts with your team without forwarding, CC'ing, or sharing passwords * Add comments and **@mentions** to any conversation (visible only to your team) * Co-write drafts in real-time with colleagues * Manage email, SMS, WhatsApp, Instagram, Messenger, and live chat in one inbox * Automate repetitive work with rules and AI {% embed url="" %} ## Who uses Missive Customer support teams, sales teams, and agencies. Any business where email is mission-critical and collaboration matters. ## Join a live session We run live 45-minute sessions twice a week covering team inboxes, collaboration features, and Q\&A with the Missive team. [Register here](https://missiveapp.com/webinar). ## Video library Tutorials, deep dives, customer stories, and workflow ideas. [Watch videos](https://www.youtube.com/@missiveapp/videos). --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://missiveapp.com/docs/get-started/readme.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 `build a script that syncs our docs to a CMS` 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.