> 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/core-features/aliases-and-signatures.md). # Aliases & signatures Control which email address and signature appear when you reply. Set up aliases for different contexts (support@, sales@) and create signatures that match. ### What are aliases? An alias is an email address attached to an email account. Every email account inherently comes with at least one alias, known as the default email address. However, it is entirely possible for an email account to have multiple aliases. {% hint style="info" %} Consider the email account . In addition to its default alias, , it could have multiple aliases such as , , , etc. {% endhint %} ### What are email signatures? Email signatures in Missive are customizable blocks of text automatically added at the end of your outgoing emails. They help ensure consistency in how you and your colleagues present your contact details, branding, and company information. {% hint style="info" %} Signatures can be personal, created by each user, or managed at the organization level, where shared templates ensure everyone uses the same layout and formatting. {% endhint %} --- # 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://missiveapp.com/docs/core-features/aliases-and-signatures.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.