> ## Documentation Index
> Fetch the complete documentation index at: https://docs.make-pretty.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Support
> How to reach us, and what to include so a problem can be reproduced on the first try.
Email [support@make-pretty.com](mailto:support@make-pretty.com). Before that, check
[Troubleshooting](/help/troubleshooting). Most of what people write in about has a fix on that
page.
## What to include
A report with these six things can usually be reproduced without a back-and-forth.
| Include | Where to get it | Why it helps |
| ----------------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| What you asked | Copy the message you sent, verbatim | The exact wording is often the difference between a good result and a bad one |
| The message ID | Message actions → **Copy Message ID** | Points us at the precise turn, with its steps and model |
| Roughly when | Date and time, with your timezone | Narrows the logs when a message ID is not to hand |
| Which deck and template | Deck name, and whether it uses your firm's master or a [slide pool](/slide-pools/overview) | Most slide problems are template problems |
| Expected versus actual | One line each | Tells us what "wrong" means to you |
| The failure text | Expand the failed step → **Copy error** | The literal error, not a description of it |
**Copy Message ID** is the single most useful item. With it we can pull the whole turn (every
step row, the model that ran, and what came back) without asking you to reproduce anything.
If a slide came out wrong rather than erroring, attach the `.pptx` too, or a screenshot of the
slide next to what you expected.
## The fastest way to flag a bad result
Rate the answer in the chat. Every reply ends with *"How good was this answer?"* (1 to 10, from
**Useless** to **Perfect**), and picking a rating offers a reason: **Wrong content**,
**Design is off**, **Missed my ask**, **Too slow**, or **Something else**, plus an optional note.
The rating is attached to that conversation, so it arrives with the context already in it. It
takes a second and needs no email. Use support instead when you need an answer back.
## Reporting a security issue
Email [support@make-pretty.com](mailto:support@make-pretty.com) with the details and how to
reproduce it. Please do not post it publicly first.
Security reviewers asking for documentation (certificates, hosting detail, data-processing
terms) should use the same address. [Security and privacy](/help/security) is a summary, not a
compliance pack.
## Account and billing
Start with your workspace owner or an admin. Most of what people ask about is theirs to change,
not ours:
| Question | Who handles it |
| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Add or remove a teammate, change a role | Workspace owner or admin. See [Members and roles](/admin/members) |
| Raise the monthly AI allowance | Ask your workspace owner or admin, who arranges it with us. See [Usage and limits](/admin/usage-limits) |
| Change the model provider or API key | Workspace admin. See [Model providers](/admin/model-providers) |
| Ownership transfer, or anything the UI will not let an admin do | Support |
For your own account, **Settings → Account** has **Export your data** and account deletion
without going through us. See [Preferences](/help/preferences).
## Related
Symptom-by-symptom fixes, including every error the chat can show.
Every step row Pretty shows while it works, and what to expect from each.