Support center
Use this page to choose the right channel. Product and account issues go to support@fbrights.com. Intellectual property packets go to ip@fbrights.com. WhatsApp +1 209 659 8799 is for messaging coordination only.
What to include
Your account email, asset identifiers, and a short description. Attach only relevant files. Never send passwords.
Dashboard tickets
Signed-in clients can open support tickets so replies stay linked to the account.
Technical issues
Describe browser, time, and what you expected. Screenshots help. Do not include session cookies.
Billing
Include invoice identifiers. Review the Refund Policy before disputing a charge.
Security reporting
Email support@fbrights.com with a factual description. Do not test exploits against other customers.
Hours
We do not publish invented office hours or guaranteed response times.
Example
A client cannot upload a large video. They email the filename, size, and error text. Support investigates storage limits without needing the Facebook password.
Escalation
If a ticket already exists, include the reference. Do not open duplicates across every channel at once.
FAQ
Is WhatsApp a voice line? No. Messaging only.
Get started
Continue in the dashboard after login or registration. If you are not signed in, use the free trial registration flow and return to the related module. Email support@fbrights.com, ip@fbrights.com for intellectual property packets, or WhatsApp +1 209 659 8799.
Channel selection
Product and account issues go to support@fbrights.com. Intellectual property packets go to ip@fbrights.com. WhatsApp +1 209 659 8799 is messaging only.
Ticket hygiene
Include account email, asset identifiers, and a short description. Avoid duplicate messages across every channel at once.
Security reports
Email support@fbrights.com with subject Security Report. Do not test exploits against other customers.
Support expectations
Provide context, identifiers, and relevant attachments. Avoid passwords. Use the correct mailbox. Dashboard tickets keep history when the application backend is live. WhatsApp is for coordination, not formal evidence storage. We do not publish invented SLAs.
Examples of good tickets
Good tickets name the Page or work, attach the error screenshot, and state the expected result. Poor tickets paste credentials or demand guaranteed recovery. Clear tickets receive clearer answers.
Support expectations
Provide context, identifiers, and relevant attachments. Avoid passwords. Use the correct mailbox. Dashboard tickets keep history when the application backend is live. WhatsApp is for coordination, not formal evidence storage. We do not publish invented SLAs.
Examples of good tickets
Good tickets name the Page or work, attach the error screenshot, and state the expected result. Poor tickets paste credentials or demand guaranteed recovery. Clear tickets receive clearer answers.
Support expectations
Provide context, identifiers, and relevant attachments. Avoid passwords. Use the correct mailbox. Dashboard tickets keep history when the application backend is live. WhatsApp is for coordination, not formal evidence storage. We do not publish invented SLAs.
Examples of good tickets
Good tickets name the Page or work, attach the error screenshot, and state the expected result. Poor tickets paste credentials or demand guaranteed recovery. Clear tickets receive clearer answers.
Support expectations
Provide context, identifiers, and relevant attachments. Avoid passwords. Use the correct mailbox. Dashboard tickets keep history when the application backend is live. WhatsApp is for coordination, not formal evidence storage. We do not publish invented SLAs.
Examples of good tickets
Good tickets name the Page or work, attach the error screenshot, and state the expected result. Poor tickets paste credentials or demand guaranteed recovery. Clear tickets receive clearer answers.
Clients should keep local copies of critical notices, avoid sharing passwords, and use the dashboard modules after Sign In so email threads and workspace records stay aligned. International clients are welcome. English is the primary language for formal correspondence. WhatsApp +1 209 659 8799 is messaging only.

