Support

Start with the fastest recovery path, then escalate only when the issue needs manual review.

Use self-serve recovery first for password and sign-in issues. Use direct support for billing mismatches, failed paid runs, blocked access, and questions that still need human review.

Support overview

One support page, three clear paths, and a direct route to manual review.

The page is designed to keep support decisions simple. Start with self-serve recovery for password or sign-in blockers. Use pricing when the question is really about plans or lane limits. Use direct support when the issue involves billing, failed paid runs, blocked access, or anything that still needs a human review after the obvious recovery steps are done.

Direct contact
[email protected]

Best for login recovery, billing questions, workflow access issues, and refund review.

Response target
Within 1 business day

Priority goes to failed paid runs, billing mismatches, and blocked customer access.

Best use
Billing, failed runs, account review

Use direct support when the issue cannot be solved by login recovery or plan checking alone.

Manual review

When the issue needs a human, send the cleanest context possible.

The fastest support requests include the account email, the workflow or billing reference, the approximate time of the issue, and the exact error or missing output.

Recommended subject
Billing issue / Failed run / Access issue
Send emailLogin help
User manual

Read the workflow manual before sending a product question.

The manual explains the 8-step article workflow, which fields are optional, example answers for each field, and how inputs affect generated output. Use it when the question is about how to operate the editor rather than billing, login, or failed runs.

Open user manual
Fastest route first

Use the right path before opening a manual review.

Most support delays happen when a self-serve issue gets sent as a manual support request. These routes are meant to solve the obvious blockers first and keep human review for the cases that really need it.

Self-serve
Forgot password

Use this first when an email-sign-in account cannot access the current password.

Reset password
Self-serve
Login help

Use this for Google-account mismatch, verification loops, or routing confusion after sign-in.

Open login help
Self-serve
Pricing and limits

Check plans, lane balances, and premium usage rules before opening a billing or limit-related support request.

View pricing
Send support request

Best results come from specific details, not long explanations.

Include the account email, workflow or billing reference, what failed, and the approximate time. If the problem is visual, mention the page and attach a screenshot in your email client before sending.

Include these details
Account email used for sign-in
Workflow, job, or billing issue involved
Exact error, missing output, or unexpected charge
Support note

Good support requests include context

Include account email, workflow or billing reference, approximate time, and the exact error or missing output.

Support note

Refund review depends on failure type

System failures are refundable. Edited briefs, manual stops, or usage-limit blocks are not treated the same way.

Support note

Use self-serve where possible

Password reset, login help, and plan comparison are faster than waiting for manual review when the issue is already covered.

Common questions

The questions support gets most often.

These answers are tuned for the current account, billing, refund, and access flow so users can resolve obvious blockers before sending an email.

What is the fastest way to get support?+

Use the support email form on this page and include the account email, the workflow or job involved, what you expected to happen, and what actually happened. That gives support enough context to review the issue without extra back-and-forth.

What details should I include in a support request?+

Include the signed-in email, billing or workflow name, approximate time of the issue, any visible error message, and whether the problem affected drafts, premium text, standard visuals, premium visuals, or billing. Screenshots help when the issue is visual.

When are refunds automatic?+

If a paid run starts and then fails because of a provider outage, infrastructure interruption, or internal processing issue, credits are refunded automatically. The refund appears in usage history and the billing ledger after the failure is recorded.

What does not count as a system failure?+

Changed briefs, prompt rewrites, manual cancellations, usage limits, or stopping mid-session are not treated as system failures. Support reviews refunds based on whether the platform or model-delivery layer broke after the run began.

Why do drafts, premium text, and images show different remaining balances?+

blogworkflow.ai tracks usage by lane. Standard draft generation, premium text generation, visual research, standard visual generation, and premium visual generation each use their own allowance, so the dashboard shows separate remaining balances instead of one pooled counter.

Will other users see my workflows, outputs, or generation history?+

No. Workflows, saved outputs, and usage history are scoped to the signed-in account. Other users do not see your library unless they are using the same account credentials.

What should I do if email verification completed but access still looks blocked?+

Return to the login page and sign in again with the same email or Google account that created the workspace. If the dashboard still does not open, use Login help first. If it still fails, contact support and include the account email so the login method can be checked.

How long are generated sessions kept in Project Library?+

Project Library keeps the most recent 30 days of saved outputs. Download important HTML, Markdown, SEO pack, and image assets before older sessions roll out of the visible history window.