<script type="application/ld+json">{"@context":"https://schema.org","@type":"TechArticle","headline":"Contacting support","description":"How to reach HarperFlow directly, in-app or before you've even signed up.","dateModified":"2026-07-12","inLanguage":"en","author":{"@type":"Organization","name":"HarperFlow"},"publisher":{"@type":"Organization","name":"HarperFlow","url":"https://www.harperflow.io","logo":{"@type":"ImageObject","url":"https://www.harperflow.io/favicon.png"}},"mainEntityOfPage":"https://www.harperflow.io/docs/contacting-support"}</script>
Troubleshooting
How to reach HarperFlow directly, in-app or before you've even signed up.
There's no ticket queue or chatbot standing between you and the team. A real person reads every message.
Look for Contact us inside the app. It shows up on your Profile page, on billing and plan screens, and a few other spots where you might get stuck. Write what's going on, and it goes straight to the HarperFlow team with your account attached, so a reply lands in your inbox rather than a support portal. You'll also get an automatic confirmation email the moment it sends.
The same kind of form is available on the register and sign-in screens, for problems that happen before you have an account to attach a message to. You'll be asked for your email so a reply has somewhere to go, and you won't get the automatic confirmation copy this way, just the reply itself once someone reads it.
A faster reply usually comes down to a bit of context: which workspace or site you mean, what you were trying to do, and the exact wording of any error message you saw. If it's about a specific article or run, mention its title or the date. The team can look it up much faster with something concrete to search for.
For some things, extending a trial, setting up Agency billing, an Enterprise conversation, the app offers a short call with HarperFlow's founder instead of a written form. It's the same team either way; a call just makes more sense when there's back-and-forth to work through.
Note: Messages are rate-limited to a handful in a short window, so give the team a moment to reply before sending a follow-up. It hasn't been lost.