Report an Issue With Flinque
Something not working right? Tell us about it. Every issue report goes directly to our engineering and support team, gets categorized by severity, and triggers a response within the SLA window for your plan. We triage critical platform issues within 2 hours, respond to account and billing issues within 24 hours, and fix verified bugs on a predictable release cadence.
Check these first, you might find a faster answer
Many issues have quick fixes or known workarounds already documented. A 60-second check here often beats waiting for support.
What Kind of Issue Are You Reporting?
We handle 10 categories of issues. Knowing which category your issue falls into helps us route it to the right team faster and gives you a better sense of the expected response time.
Account & Login
Cannot log in, password reset not working, account locked, 2FA problems, or unexpected logouts.
Billing & Payments
Failed payments, wrong charges, invoice issues, plan changes, refund requests, or subscription problems.
Data Accuracy
Wrong creator metrics, incorrect audience data, fake follower scores that look off, or stale profile information.
Integration Problems
Shopify, WooCommerce, Google Ads, Meta Ads, or other integrations not syncing, throwing errors, or returning incorrect data.
API & Developer
API errors, rate limit questions, webhook delivery failures, authentication issues, or endpoint behavior that does not match the developer docs.
Platform Bug
Filters not working, exports failing, search returning unexpected results, UI glitches, or any feature that is not behaving as documented.
Security Concern
Suspicious account activity, unauthorized access, vulnerability reports, or any security-related concern. These go to our security team immediately.
Privacy & Data Requests
GDPR, CCPA, or other privacy-related requests including data export, creator profile removal, or right to erasure.
Performance & Speed
Slow loading pages, search timeouts, exports taking too long, or dashboard responsiveness problems.
Something Else
Anything that does not fit the categories above. Describe it in the form below and our team will route it correctly.
Severity Levels and Response Time SLAs
Not every issue is urgent, and we take severity labels seriously so genuinely critical problems get immediate attention. Here is how we classify issues and what response times you can expect.
These are target SLAs based on median response time over the past 90 days. Response time for urgent issues outside business hours may be longer for Starter Plan customers. Enterprise customers get 24/7 priority monitoring regardless of category.
Submit Your Issue Report
Fill out the form below with as much detail as possible. You will get an automated confirmation immediately and a real response from our team within the SLA for your severity level and plan.
What Information Should You Include?
The difference between a 10-minute resolution and a 3-day back-and-forth is usually the quality of the initial report. Here is what our engineering team needs to triage and fix issues fast.
What happened vs what you expected
Describe the actual behavior and the behavior you expected. This is the single most valuable piece of information for us.
Steps to reproduce
Tell us exactly how to trigger the issue. “Click X, then Y, then see Z”. If we cannot reproduce it, we cannot fix it.
When it started happening
First noticed today? Last week? Right after a specific action? Timing helps us correlate issues with recent releases.
Screenshots or recordings
A 30-second Loom or an annotated screenshot is worth hundreds of words. Especially for UI bugs or visual issues.
Request and response details
The endpoint, request payload, response body, and request ID (from the error response). This cuts triage time by hours.
Specific creator handles
If creator data looks wrong, tell us which creator handles are affected. “Follower count for @username looks incorrect” beats “numbers look off”.
Known Issues and Status
If you are experiencing an issue, check here first. We log active platform issues publicly so you know what our team is already working on and when a fix is expected.
All systems operational
No active platform-wide issues reported. Last status check: checked continuously, updated every 5 minutes.
Is the platform down or is there a security emergency?
For P1 Critical issues like full platform outages, data loss, or active security concerns, submit the form above with severity set to P1 Critical. Our on-call engineering team monitors P1 reports 24/7. Enterprise customers can also reach their dedicated support contact directly.
For security vulnerabilities that should not be submitted through a public form, email our security team directly. We treat all security reports confidentially and welcome responsible disclosure from researchers.
Prefer a different contact method?
The form above is the fastest route to our engineering team for platform issues. For other requests, here are alternative contact paths.
In-app chat
Quickest for active customers. Click the chat icon in your dashboard.
Feature requests
Have an idea for a new feature or improvement?
Your report helps us build a better platform
Every bug fix, data correction, and platform improvement starts with a customer telling us something is not right. The more specific your report, the faster we can fix it for you and everyone else.
Report an Issue FAQs
How do I report a bug on Flinque?
Use the issue report form above. Select “Platform Bug” as the category, choose an appropriate severity level, and describe what happened versus what you expected. Include steps to reproduce the bug, screenshots if possible, and your browser or device info. Our team responds within the SLA window for your severity and plan.
How fast does Flinque respond to issue reports?
Response times depend on severity and plan. P1 Critical issues get responses within 2 hours (24/7) for standard plans, or within 1 hour for Enterprise plans. P2 High issues get responses within 24 hours on business days. P3 Medium within 48 hours. P4 Low within 72 hours. Enterprise plan customers get priority response across all severity levels.
Can I report an issue without being a paying customer?
Yes. Free Plan users can submit issue reports through the same form. Response times may be slightly longer for Free Plan users compared to paid plans, but we review 100% of reports regardless of plan.
What is the difference between reporting an issue and requesting a feature?
An issue report describes something that is not working as documented or expected. A feature request asks for new functionality that does not exist yet. For feature requests, use the “Something Else” category in the form above or submit via our contact page.
How do I report a security vulnerability in Flinque?
For security vulnerabilities, use the “Security Concern” category in the form above, or email our security team directly. We treat all security reports confidentially and welcome responsible disclosure from security researchers. Do not post vulnerabilities publicly before contacting us.
How do I request data removal or exercise GDPR rights?
Use the “Privacy & Data Requests” category in the form above. We handle GDPR, CCPA, and other privacy requests including data export, right to erasure, and creator profile removal. Standard response time for privacy requests is under 30 days per regulatory requirements, though we aim to resolve most within 7 days.
What happens after I submit an issue report?
You get an automated confirmation email with a ticket ID immediately. A member of our support team reviews the report, triages the severity, and responds within the SLA window. For verified bugs, your ticket stays open until the fix ships to production, and you receive an update when that happens.
Can I track the status of my issue report?
Yes. Every issue report gets a unique ticket ID in the confirmation email. You can reply to that email chain for updates, and our support team proactively notifies you when the issue is resolved or when additional information is needed. Enterprise customers also get in-dashboard ticket tracking.