> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/revenue/quotes/format-descriptions-and-terms-with-rich-text.md). # Format descriptions and terms with rich text The Description field on quotes, invoices, and subscriptions — and the content of your quote Terms & Conditions sets — supports rich text formatting. Whatever you format shows up the same way in the document preview, the PDF your customer receives, and the quote signing page. ## Available formatting The toolbar above the field offers: * **Bold**, *italic*, and underline * Three heading sizes (H1, H2, H3) for section titles * Bulleted and numbered lists * Horizontal divider lines * Tables — the table button inserts a 3×3 table with a header row Use the numbered-list toolbar button to start a numbered list. Typing `1.` at the beginning of a line also starts one automatically. When typing or pasting plain text, other starting numbers remain ordinary text. While your cursor is inside a table, extra controls appear in the toolbar to add or remove rows and columns or delete the whole table. ## Where you can use it * **Quote, invoice, and subscription Description** — the Description field on the document form. * **Terms & Conditions sets** — the content editor on Settings → Quotes → Terms & Conditions. Formatting saved there appears at the bottom of every quote that uses that set. Text you wrote before this feature existed keeps rendering exactly as it did, and it converts to editable paragraphs the first time you open it in the editor. ## In the mobile app Technicians can format quote and invoice descriptions in the mobile app too. The **Description** field there has the same toolbar buttons as the web app, including the table controls (tap **Aa** next to **Suggest** to show or hide them), and works without an internet connection. A description formatted on the web shows the same way in the app, and formatting added in the app shows the same way on the web, in the PDF, and on the signing page. Opening and saving a quote or invoice in the app without changing its description leaves the description exactly as it was. See [Create and send quotes and invoices on mobile](/field-operations/mobile/create-and-send-quotes-and-invoices.md#description-formatting). ## Formatting and the AI * **AI quote/invoice drafting** writes formatted descriptions when something calls for it: ask for it in your instructions ("format the description with a heading and a bulleted list"), or give your quote prompt template a formatted Description — the template Description editor on Settings supports the same formatting, and generated documents carry it through exactly, including when the template's instructions direct edits to it. * **Suggest** keeps your formatting: when the description you're improving has headings, lists, or tables, the suggestion preserves that structure, and the review dialog shows both versions formatted. ## Tips * Paste formatted content from another document and the editor keeps the formatting it supports (headings, lists, divider lines, tables, bold/italic/underline); anything else is cleaned up automatically. * If your business uses a customized document template, tables and headings render with standard styling inside the description area of your existing layout. > **Where to find it:** The Description field on an open quote or invoice, and Settings → Quotes → Terms & Conditions ## Related guides * [Create a quote](/revenue/quotes/create-a-quote.md) * [Set terms and conditions on a quote](/revenue/quotes/set-terms-and-conditions-on-a-quote.md) * [Create Terms & Conditions sets for quotes](/administration/settings/create-terms-and-conditions-sets-for-quotes.md) * [Create an invoice](/revenue/invoices/create-an-invoice.md) --- # 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://learn.withessential.com/revenue/quotes/format-descriptions-and-terms-with-rich-text.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.