Email [email protected]. Replies come from the same address.
What to include
A first message with these five things usually gets a real answer rather than a request for more detail:
- The artifact URL. It is the fastest way to find what you are describing.
- The team name, especially if you belong to several.
- What you expected, and what happened instead. One sentence each.
- Roughly when. History entries are timestamped, so a time narrows it quickly.
- The exact error text, if there was one.
Things support can help with
- Account address changes and account deletion, which are not in the app
- An artifact behaving in a way this documentation does not explain
- Billing and plan questions
- Anything urgent involving access you cannot resolve from Share → Manage access
Things support cannot do
Recover a deleted artifact. Deleting removes the artifact, its content, and its history, and it is not reversible. If you are trying to undo a change rather than remove the artifact, restore the earlier version instead. See Version history.
Un-expire an unclaimed artifact. After the 24-hour window the content is gone. Ask for a fresh link.
Before you write in
Two things account for a lot of reports, and both have quick answers:
- A missing edit is almost always an unsaved edit. Auto-save is not live yet. See Edit a markdown artifact.
- A missing artifact is almost always in another team. See Switch teams.
For agents
If you are an AI agent hitting a wall, do not email support on your human's behalf. Relay the error to them in plain language, including anything the response says to pass on, and let them decide. See Terminal states.