Account Support
Account support for ChainReachAI customers needing help with billing, subscriptions, access, permissions, and workspace administration.
Quick summary
- -Account support handles billing, plan changes, seat management, and access-related issues.
- -Requests move faster when customers include the affected workspace, billing context, and what change is required.
- -This page is for account administration rather than technical troubleshooting.
- -Teams can use this route for subscription clarity, permission questions, and operational account changes.
Account support exists so customers can resolve billing, subscription, and access issues without getting routed through technical troubleshooting first. These requests usually need account context, commercial history, and admin-level details rather than bug reproduction steps.
Use this page when the issue relates to who can access the workspace, what plan is active, how billing should change, or how account-level controls should be updated.
Billing and subscription questions
Use account support for plan changes, billing clarification, renewal questions, subscription status, or administrative requests tied to a customer workspace. The more specific the change request, the faster it can be handled.
Useful context includes the current plan, the intended change, the billing cycle involved, and whether the request is urgent due to renewal or customer operations.
Access and permission management
Account support also covers login issues, seat changes, workspace access, and permission questions. These are administrative workflows and should be handled separately from technical product defects.
If the issue affects who can enter the platform or what they can control inside it, this is the correct support path.
- -Login and authentication concerns.
- -Workspace access questions.
- -Seat or user administration changes.
- -Permission or account-control clarification.
What to include in your request
Account support requests should identify the workspace, the user or role affected, and the exact change needed. For billing questions, include the plan or payment context so the team does not need to reconstruct it from scratch.
If the request is time-sensitive because it affects production access or renewal timing, say that explicitly in the first message.
When to use a different path
If the issue is a product bug or broken workflow, use technical support instead. If the request is commercial or partnership-related, use the main contact page.
Clear routing helps the team resolve issues faster because the right people start with the right context.
FAQ
What does ChainReachAI account support handle?
Account support handles billing, plan changes, subscription questions, seat updates, login issues, and workspace administration requests.
Should I use account support for product bugs?
No. Product bugs and broken workflows should go through technical support so they can be investigated as engineering issues.
What helps account support respond faster?
Include the workspace context, affected user or role, billing details if relevant, and the exact account or subscription change you need.
Account changes move faster when the request is specific
Explain the workspace, the billing context, and the exact access or subscription change required.