| Information |
Why it matters |
| Account email |
Identifies the account |
| Plan |
Supports billing review |
| Billing date |
Supports charge review |
| Invoice or receipt |
Supports refund or invoice request |
| Charge date and amount |
Supports payment investigation |
| Pause/cancel screenshot |
Supports charged-after-cancel complaints |
| Team/workspace name |
Supports team issues |
| Project name |
Supports export or recovery issues |
| Prototype link |
Supports access complaints |
| Collaborator emails |
Supports team access review |
| Export error |
Supports product troubleshooting |
| Support ticket number |
Keeps escalation focused |
For billing complaints, lead with account email, plan, charge date, invoice, and pause/cancel status.
Cancellation and Paused Billing Complaints
Fluid UI's billing help says users can pause an account from the Billing tab and will not be charged in the future after pausing. It also warns that team members may not be able to access team projects while the account is paused.
Use this table:
| Billing issue |
Complaint focus |
| Need to pause or cancel |
Billing tab screenshot |
| Charged after pause |
Pause screenshot and charge date |
| Team lost access after pause |
Team name and member emails |
| Invoice missing |
Billing email and charge date |
| Payment failed |
Error screenshot and invoice |
| Plan confusion |
Plan screen and account email |
Ask Fluid UI to confirm future billing status and whether team access is expected to stop.
Refund and Invoice Complaints
Fluid UI's help center has a dedicated billing, payments, and refunds category. Since public refund terms can depend on the account and transaction, a refund complaint should include the account, invoice, charge date, amount, billing status, and the reason for review.
Use this table:
| Refund issue |
Evidence |
| Refund request |
Invoice, charge date, reason |
| Charged after cancellation |
Cancellation/pause screenshot |
| Duplicate charge |
Receipts and card statement |
| Missing invoice |
Account email and charge |
| Wrong plan charged |
Plan screen and invoice |
| Team billing dispute |
Team name, plan, members |
Ask support to state the refund policy basis in writing.
Team, Collaboration, and Project Complaints
Fluid UI team and collaboration complaints should focus on who owns the project, who has access, and whether account pausing changed access for team members.
Use this table:
| Project issue |
What to include |
| Team members cannot access |
Team name, member emails, billing status |
| Prototype link not working |
Prototype URL and permissions |
| Export failed |
Project name, export type, error |
| Deleted project |
Project name and deletion date |
| Owner unavailable |
Team owner email and account context |
| Collaboration issue |
Project name, collaborators, role |
Ask support to confirm ownership, access rights, and recovery or export options.
Privacy and Data Deletion Complaints
Fluid UI privacy complaints should identify the account email, request type, project context, and whether the customer also needs project exports before deletion.
Use this table:
| Privacy issue |
What to include |
| Data access request |
Account email and request type |
| Data deletion |
Account email and deletion scope |
| Project data question |
Project name and ownership |
| Team data question |
Team name and role |
| Unresolved privacy complaint |
Prior request and response |
| Export before deletion |
Project list and export format |
Save invoices, project links, and export files before requesting deletion.
When to Escalate Beyond Fluid UI
| Situation |
Escalation path |
Notes |
| Billing not stopped after pause |
Fluid UI support |
Include pause screenshot |
| Team access unresolved |
Team owner and Fluid UI support |
Include team and member list |
| Project export issue |
Fluid UI support |
Include project and error |
| Privacy request unresolved |
Fluid UI privacy route or applicable authority |
Include request date |
| Payment dispute considered |
Payment issuer |
Preserve Fluid UI support history first |
Escalation is strongest when the account email, plan, billing status, and project identifiers are clear.
What to Say in a Fluid UI Complaint
Use this script:
"I need Fluid UI to review a complaint for account [email]. The issue is [subscription cancellation, paused billing, refund review, invoice request, payment problem, team access, project export, prototype access, deleted project, account login, privacy request, or support delay]. The relevant details are [plan, charge date, amount, invoice, pause/cancel screenshot, team name, project name, prototype URL, export error, collaborator emails, support ticket, deletion date, or privacy request]. I am requesting [pause confirmation, cancellation confirmation, refund review, invoice copy, payment correction, team access explanation, project restore, export help, account access help, data deletion confirmation, privacy response, or written policy explanation]. Please confirm the next step and decision in writing."
Let Pine AI Help File the Complaint
