Getting help

Wren is a small operation, and a person reads what you send. This page is about making that exchange quick: where to write, and what to say so the first reply is a useful one rather than a request for more detail.

Which address

support@writewithwren.com — anything about the product. The extension isn't syncing, analytics look wrong or empty, a post didn't publish, a plan or charge doesn't look right, something is broken or behaving strangely.

legal@writewithwren.com — your data. Asking for a copy of what we hold, correcting it, exporting your content, or deleting your account and its data. What we cover and how it works is in Your data and privacy.

The contact form — everything else. Questions before you sign up, partnerships, press, feedback, or anything that isn't one of the above.

If you pick the wrong one, nothing bad happens — they all reach the same person.

What to include

Four things, and the first reply is usually the answer rather than a question:

1. The email address on your Wren account, if you're writing from a different one.
2. What you were doing — the page you were on and what you clicked.
3. What you expected, and what happened instead. "It didn't work" and "the button did nothing, I expected a draft" are very different starting points.
4. When it happened, roughly. Server logs are searchable by time, so "this morning" narrows things considerably.

A screenshot is worth a paragraph, especially for anything visual.

Things worth trying first

Some problems have a known answer, and the article will be faster than waiting for a reply:

• The extension isn't picking up your posts → The Wren browser extension
• Analytics are empty or look wrong → Tracking your performance
• A charge, a plan change, the monthly allowance, or a refund → Plans and billing
• Cancelling, or deleting your data → Managing your account

What support can't reach

Being straight about the edges, so you're not left waiting on something that isn't coming:

• LinkedIn itself. If LinkedIn has restricted, limited or locked your account, that's between you and them — Wren has no visibility into it and no way to appeal on your behalf.
• What LinkedIn reports. Wren shows the numbers LinkedIn gives; where those disagree with LinkedIn's own screens, theirs is the source.
• Writing the post for you. Wren drafts, critiques and revises inside the product — but a support email isn't a channel for having a post written.
• Your OpenRouter account. On Nest the key and the balance are yours. If it's out of credit or a charge there looks wrong, OpenRouter's support is the right door.

Anything else, write in. It's better to send it and be redirected than to sit with something broken.