---
title: "Getting support"
category: "Support"
source: "https://getbloggable.com/help/getting-support"
updated: 2026-10-22T10:34:36.217Z
---

# Getting support

## Start with Joe

Joe is on every signed-in page and searches these same help articles — but with your account in front of him. He'll usually answer faster than we will, and he can often just do the thing you were about to ask how to do.

Talking to Joe is free.

## Getting a human

If Joe can't help, **ask him to escalate**. He opens a support form and hands over the conversation as context, so you don't have to re-explain what you were trying to do.

Joe doesn't create tickets on his own — the form is always yours to submit. That's deliberate: a ticket you didn't knowingly raise is a ticket you'll never see the answer to.

**If you can't sign in**, email support directly using the "Email support" button at the bottom of any help article. Mail to that address becomes a ticket the same way the in-app form does, so either route reaches the same place.

## If your account is locked

A lapsed trial or a failed payment locks the app. Escalation to a human deliberately stays available on a locked account — that's the situation most likely to need one. Joe also stays available, read-only.

See *Plans, upgrades and top-ups*.

## What to include

The more of this you can give us, the faster this goes:

- **What you expected to happen**, and what happened instead
- **Which blog and which post**, by name or URL
- **When** it happened, roughly
- Anything the interface told you — an error message, a code, a screenshot

For a billing question, say what you were charged and what you expected. For a generation that went wrong, tell us which action you ran and, if you still have it, leave the draft in place rather than deleting it.

## Things that are usually us, not you

Report these rather than working around them:

- Credits that didn't reset at the start of a cycle
- A plan showing the wrong state after a successful payment
- An action that failed but wasn't refunded — failures are supposed to refund automatically
- A published post that isn't reachable at its public URL
- A custom domain that verified and then stopped serving