> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmailr.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Mailr is a direct-mail marketing platform for US home-services contractors. Each postcard is personalized with an AI-enhanced image of the recipient's own home and a unique QR code that leads to a personalized landing page. Campaigns can target a neighborhood the customer draws on a map, the homes around past jobs they upload or import, or fire automatically from their CRM. Mailr does not mail an uploaded recipient list. When answering questions, prefer the exact steps and UI labels from these docs, and direct users to app.getmailr.com to sign in. For anything involving account-specific data, billing disputes, or mail that appears lost, direct the user to support@getmailr.com.
# Edit a design with AI
> Refine a Mailr postcard by describing the change: one side at a time, up to two reference images, every edit saved as a new version you can return to.
Editing a design in Mailr is **instruction-based**: you describe the change in words, optionally attach a reference image or two, and Mailr renders a new version of that side. It isn't a drag-and-drop canvas and there are no layers to move — you direct the design, you don't push boxes around.
Open the editor from your design library, or with **Open in editor →** right after a design generates.
## What's on the editor screen
* **Editor bar** (top) — **← Designs**, the design name, a **Saved** (or **Approved**) chip, **Print preview**, **Edit from this version**, and **Approve for use · Front v2 · Back v1 →**.
* **Left rail** — the Front/Back switcher with live thumbnails (each labeled "· v3" or "Rendering v4…"), then **VERSIONS · FRONT/BACK**: every version as a thumbnail, the live one badged **Current**, and a **Use this version** action on any other.
* **Middle** — the artboard, with **Fit**, **◉ Print guides**, an **↗ Expand** control (or double-click) for full size, and the caption **"6 × 9 in · Front · v2 · sample home shown — each recipient sees their own house."** On the front of a Home Render design there's also a **⌂ Sample home / ▦ Transparent** toggle.
* **Right** — the **ACTIVITY** thread: your instructions as chat bubbles and each render's result as a version card ("v3 of the front is ready", with **View** and **Use this version**), with the composer at the bottom.
The house in the editor is always a stand-in. The toggle's tooltip says it: **"The house is a stand-in — every recipient's card features their own home."** Switch to **▦ Transparent** to see your artwork with the photo area knocked out, so you can tell exactly which part of the card each recipient's home fills.
## Run an edit
Use the Front/Back switcher in the left rail. The composer header changes to **EDIT THE FRONT** or **EDIT THE BACK**.
Type it in the composer — the placeholder reads **"Describe the change to the front…"**. Send it empty and you'll get *"Describe the change first."*
**＋ Add reference** opens your brand-kit photos and logos with an upload option, and you can paste an image from your clipboard anywhere in the panel. The cap is **2 reference images per edit** — the counter reads "1 / 2", and going over shows *"Up to 2 reference images per edit."* References have to come from your brand gallery or your own uploads.
Press **Edit front** or **Edit back**. The fine print spells out exactly what will happen: **"This creates v4 for the front. The back will not change. · N credits."**
The thread shows **"Rendering v4 of the front…"**, with your queue position if it's waiting. A toast reads **"New version ready"** when it lands.
## One side at a time
An edit only ever changes the side you ran it on. Editing the front never touches the back, and each side runs one edit at a time — start a second front run and you'll see *"A front run is already in progress for this design."*
You **can** work on both sides at once. The app tells you so: *"The front is still rendering — you can edit the back at the same time."*
Two other limits worth knowing:
* **Nothing to edit before generating** — *"No front version to edit yet — generate first."* Generate the design before you try to refine it.
* **Approved designs are locked.** The composer and every action are disabled. Use **New design from this** in the library's **•••** menu to get an editable copy.
## Versions: nothing is overwritten
Every edit creates a **new version**. Earlier versions are never replaced, so you can always go back.
The **VERSIONS · FRONT** and **VERSIONS · BACK** rails list every version as a thumbnail. Click one to look at it, and press **Use this version** to make it live again. Version cards in the **ACTIVITY** thread carry the same **View** and **Use this version** actions.
Your next edit — and your approval — always start from the version marked **Current**. To change which one that is, select the version you want and use **Use this version**, or **Edit from this version** in the editor bar (tooltip: *"Make this the version your next edit (and approval) starts from."*). If the version is already live the tooltip reads *"Edits already start from this version."*
## Credits and failed runs
The **AI credits** chip in the section rail shows your balance, and every action shows its own cost before you commit — **· N credits** under **Edit front**. If you're short, you'll see *"Not enough AI credits — this run needs N and you have M."*
**Failed or timed-out runs refund automatically.** You are not charged for an edit that didn't produce a version.
Failures are shown per side, in place, and each message says what to do:
| Message | What to do |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| *"This request couldn't be processed. Try rewording your direction."* | Rephrase the instruction in plainer, more concrete terms and run it again. |
| *"The design service is busy right now. Your credits were refunded — try again in a minute."* | Wait a minute and retry. |
| *"The design run took too long and was cancelled. Your credits were refunded."* | Retry, ideally with a simpler instruction. |
| *"Something went wrong on our side. Your credits were refunded."* | Retry. If it keeps happening, [contact support](/resources/contact-support). |
## Writing an edit instruction that works
* **Change one thing per run.** Each edit produces one new version, so a single, clear change is easy to judge and easy to undo. Stack several small edits rather than writing one long list.
* **Be concrete and visual.** The kind of language the design brief asks for is the kind that works here: *"Confident and architectural. One main image, short headline, generous negative space."* Describe the result you want, not the steps to get there.
* **Say which side you mean — and pick it.** Instructions only apply to the side selected in the left rail. "Move the phone number up" run on the front will not touch the back.
* **Use a reference image instead of a paragraph.** When you want a particular look, attaching one of your own photos (up to two) says more than a long description.
* **If a run comes back wrong, reword rather than repeat.** The app's own advice for a rejected instruction is *"Try rewording your direction."*
* **Big changes belong in a regenerate.** If you don't like anything about the result, go back to your brief and use **↺ Generate again** rather than fighting it one edit at a time.
Your phone number, website, logo, and colors come from your [brand kit](/designs/brand-kit) and are applied automatically. If a contact detail is wrong on the card, fix it in the brand kit and regenerate — asking for it in an edit instruction is the long way round.
## Next steps
The full flow, including the approval checklist.
Which parts of a card change household to household.