> For the complete documentation index, see [llms.txt](https://authentic.gitbook.io/authentic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://authentic.gitbook.io/authentic-docs/go-to-market/go-to-market-for-saas-partners/prequote-marketing-emails.md). # Prequote Marketing Emails Prequoting email campaigns have historically been successful for us in driving adoption. We can send out estimated quotes, or “prequotes”, using only a few fields of information that partners typically have readily available, namely: business type, annual revenue, and state (and in some cases, the amount the business wants to insure). Through customer.io, we can send out mass campaigns that are customized by tenant and have a specific prequote for each prospect. There are two ways we can execute prequote campaigns, and each has a few steps of setup before we can go live and automate this process. Either we can send the prequote emails ourselves or partners can send them directly. In either scenario, we are able to send from a custom email address and can work together with partners on email design. #### 1. Authentic sends emails * Partner sends us emails via CSV * Partner allows us to verify their domain in our customer.io * Work together to design emails / we design with tenant final approval * We set up automated biweekly collection of email data sheet #### 2. Tenant sends emails * Tenant sets up guardrails to take in necessary data in correct form * Create template and design / use our input and template * Access our API endpoint for prequote pricing --- # 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://authentic.gitbook.io/authentic-docs/go-to-market/go-to-market-for-saas-partners/prequote-marketing-emails.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.