> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmillwork.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact support

> Send the context needed to investigate without sending secrets.

Email [support@getmillwork.dev](mailto:support@getmillwork.dev) after completing
the relevant checks.

## Ask your coding assistant to prepare the report

Copy the prompt below into the coding assistant that can see your project or
current terminal. The assistant should collect the safe details and produce the
draft. You should not have to complete a support form.

```text theme={null}
Prepare a Millwork support email for me. Do not send it.

Use only information already visible in this project, the current terminal,
and the most recent relevant error. Infer what I tried, what happened, and what
I expected from that context. Do not open or print environment files,
secret stores, browser storage, cookies, credentials, one-time setup links,
prompts, model output, or customer data. Do not include full request or
response bodies.

Collect these safe fields when available:
- what I tried and what I expected;
- dashboard, API, or provider surface;
- endpoint and HTTP method;
- UTC time;
- organization ID;
- run or connection ID;
- HTTP status;
- problem type, title, and instance;
- whether it happens every time; and
- checks already completed.

Redact any secret-like value that appears in nearby console text. Use a short,
relevant error excerpt only. If a field is unavailable, write "not available"
instead of guessing. Do not ask me to fill in these fields. Ask one short
question only if the problem itself cannot be identified from the current context.

Return only a plain-text email draft with this subject:
[Millwork support] <surface>: <short problem>
```

Review the draft before sending it. A coding assistant should prepare the
report, not email support or change your account on its own.

<Warning>
  Do not paste an entire console, log file, request body, or response body into
  an assistant. First remove credentials, authorization headers, cookies,
  secure setup links, prompts, model output, and customer data.
</Warning>

Send the reviewed draft to
[support@getmillwork.dev](mailto:support@getmillwork.dev). A redacted screenshot
is useful for a dashboard problem. For billing, include only the amount, UTC
time, and safe receipt reference. Never include card or bank details.

<Warning>
  Never send a password, API key, token, browser cookie, provider credential,
  secure setup link, invitation link, prompt, model output, or customer data.
</Warning>

Millwork cannot recover a secret that is no longer available. Create or rotate
the credential through the dashboard or secure provider setup.