1. Saved first
Every signed-in request is written to Supabase support history with the account id and RF reference.
Support
Get help with your workflow.
Send account-linked details for saved projects, billing, exports, or resume runs so the issue can be traced without posting private files publicly.
Signed-in requests are saved to your accountRequests appear in Support and Settings historyOperator review uses the account-safe request packetNever paste full payment card details or private credentials
Ticket routingWhere a support request goes after submit.
The account history is the durable record. Operator alerts are available once the production webhook URL is configured.
2. Optional alert
Set a webhook or Resend email env vars in production to send the same request packet to an operator channel.
3. Tracked status
Requests move through open, reviewing, and closed while the reference stays visible to the account.
Workflow or export problem
Include the file type, selected export format, and any request id shown in the Studio.
Prefill requestBilling or Premium issueMention whether checkout, billing management, or Premium access sync is the part that looks wrong.
Prefill requestSaved project issueShare the project name and whether restore, rename, stage, delete, or exports look wrong.
Prefill requestPrivacy or data requestUse this for account exports, communication preferences, deletion questions, or privacy policy follow-up.
Prefill requestSign-in or profile accessUse this when login, email changes, security details, or account deletion controls need attention.
Prefill requestBefore sendingSend the details that make the issue traceable.
Workflow
Upload, Tailor, generated assets, or export creation stopped before finishing.
Include the request id when shown, file type, selected template, and the last workflow step you tried.Exports
A ready PDF, DOCX, or TXT download is missing, expired, locked, or attached to the wrong run.
Include export format, saved project name, and whether the issue happens from Studio, History, or Settings.Billing
Checkout, billing management, cancellation, or Premium access does not match the account state.
Include whether the issue is checkout, portal, subscription status, or Premium entitlement sync.Privacy
Account exports, communication preferences, deletion controls, or privacy policy details need review.
Include the settings section, requested data action, and whether you already downloaded your account record.Account
Sign-in, email changes, profile details, security metadata, or account deletion controls need attention.
Include sign-in method, account email, and the settings section where the issue appears.Saved projects
Restore, rename, stage, delete, or saved document history behaves unexpectedly.
Include project name, application stage, export format, and whether the run is local or account-saved.Request helpSign in to send a support request
Sign in first so the request can be tied to your account, plan state, and saved project history.
Support details were prefilled from the page where you asked for help.
Request packetWhat gets attached
RoleForge saves only account-safe context with your request.
Account sessionSign in required
Sign in so requests attach to plan and saved-project state.
Request historyNo recent request
New requests will appear here and in Settings.
Page contextIncluded
Prefilled from the page that sent you here.
Private dataKeep out
Do not paste card numbers, passwords, or secret keys.
After submitTrack the request from your account.
Support requests keep a visible account history first. When notification routing is configured, the same request is also sent for operator review.
- The request is saved to your signed-in account with an RF reference.
- Support history appears on this page and in Settings.
- If the support channel is configured, RoleForge sends the request details for operator review.
Use your account session
Support requests are saved with the signed-in account so billing, export access, and saved project context can be checked safely.
Sign in for support