Report a Problem / Contact Support

How to contact QuoteFinder.ca support and report account, billing, verification, technical, safety, or security issues

Quick summary: Use this page to contact QuoteFinder.ca support and report problems with your account, quote requests, billing/credits, verification, team access, or platform bugs. For faster help, include a short issue label in the first line (for example, Billing / credits issue or Security Report) and share the key details listed below.

How to contact support

If you need help with a problem on QuoteFinder.ca, please contact us through our support/contact page:

Contact / Support

To help us route your request quickly, put a short label in the first line of your message (examples are listed below).

Fastest way to get routed correctly

Start your message with a clear label + one-sentence summary. Example: Billing / credits issue — I was charged, but my credit balance did not update.

What support can help with

QuoteFinder.ca support can help review platform-related issues, including:

account access problems (login issues, restricted access, unexpected errors);
quote request workflow problems (missing requests, broken pages, blocked actions);
provider/brokerage/team access and permissions issues;
billing and credits issues (declines, balance questions, blocked billing actions);
verification and document submission questions;
technical bugs, display issues, and broken links/pages;
spam, impersonation, abuse, or suspicious behavior reports;
security concerns or suspected account compromise.

Before you contact support (quick self-check)

A quick self-check can save time and help you describe the issue more clearly:

Refresh the page and try again.
Check if the issue happens in another browser/device.
Log out and back in (for account/session issues).
Check your dashboard notices (billing, verification, restrictions, etc.).
Confirm you are using the correct account/email.
If you are on a team account, confirm your role/permissions with your team admin.

Common confusion

Some problems that look like “bugs” are actually caused by permissions, eligibility, verification status, or billing/credits rules. Include any notices or error messages you see so support can identify the cause faster.

Choose the right issue label (copy one into your message)

Use one of these labels in the first line of your message to speed up routing:

Issue type	Label to use	Example
Account access	Account access issue	Account access issue — I can log in but cannot open my dashboard.
Client quote workflow	Client quote question	Client quote question — I submitted a request but cannot view updates.
Agent/provider eligibility	Agent eligibility question	Agent eligibility question — A request in my category is not available to me.
Team setup / permissions	Team setup help	Team setup help — One staff member cannot access assigned requests.
Billing / credits	Billing / credits issue	Billing / credits issue — Payment went through but credits did not appear.
Verification / documents	Verification help	Verification help — My document was rejected and I’m not sure why.
Bug / broken page	Technical bug report	Technical bug report — The market page shows a blank section on mobile.
Spam / abuse / impersonation	Abuse report	Abuse report — I received repeated unrelated messages from a provider.
Security concern	Security Report	Security Report — I think my account may have been accessed without permission.
Privacy question	Privacy request	Privacy request — I need help understanding how my data is handled.
Policy / terms question	Policy question	Policy question — I need clarification on provider messaging rules.

What to include in your support message (important)

The more specific your report is, the faster support can review it.

Include these basics

your account email (and team/brokerage name, if applicable);
a short summary of what went wrong;
the exact page URL where the issue happened (if relevant);
what you were trying to do;
what happened instead (including any error message text);
when it happened (date/time and your time zone if possible);
whether the problem is still happening right now.

For technical bugs, also include

device type (desktop/mobile/tablet);
browser and version (if known);
screenshots or screen recording (if helpful);
steps to reproduce the issue (1, 2, 3…);
whether it happens on another browser/device.

For billing / credits issues, also include

transaction date/time;
amount charged (if any);
what action you were trying to complete;
any billing/credits notice shown in your dashboard;
team account name and billing owner/admin (if applicable).

For verification/document issues, also include

the verification request type (if known);
whether this is first-time verification or re-verification;
the status shown (pending / needs action / restricted, etc.);
what step or upload failed.

For abuse, impersonation, or spam reports, also include

who was involved (profile/account name if visible);
what happened and why it seems abusive/suspicious;
screenshots/messages/links (if available);
whether there is an immediate safety or fraud concern.

Tip: copy exact error text

Exact error messages are much more useful than paraphrases. If possible, paste the full message shown on screen.

What not to send

To protect your security and privacy, please do not send:

passwords or one-time codes;
full payment card numbers;
unnecessary personal documents (unless specifically requested through a verification workflow);
sensitive information unrelated to your support issue.

Security reminder

QuoteFinder.ca support should not need your password. If someone asks for your password, treat it as suspicious and report it as a Security Report.

Reporting urgent security or fraud concerns

If you believe there is a security issue, account compromise, impersonation, or suspicious activity with potential harm, contact support right away and use:

Security Report (first line label)

Include what happened, when you noticed it, affected account/page URLs (if known), and screenshots/messages where possible.

For responsible disclosure and security reporting guidance, see:

Incident Response / Security Reporting (Responsible Disclosure)

After you contact support (what happens next)

After you submit your message, QuoteFinder.ca may:

review and route the issue to the appropriate function (support, billing, verification, trust & safety, etc.);
ask follow-up questions if more detail is needed;
request screenshots or steps to reproduce for bug reports;
request transaction details for billing reviews;
request clarification for verification or policy questions.

Some issues can be resolved quickly, while others (for example, billing disputes, verification reviews, or security investigations) may require additional review.

How to make support requests easier to resolve

Send one clear issue per message when possible.
Use a clear label in the first line.
Include the exact page URL and error text.
Attach relevant screenshots only (not large unrelated files).
If the issue is solved, reply with a short update so the case can be closed cleanly.

Respectful use of support channels

Please use support channels in good faith. Abusive, spammy, deceptive, or extortionate messages may be restricted or escalated under platform policies.

For platform conduct rules, see the Acceptable Use Policy (AUP) and Trust & Safety Enforcement / Policy Violations.

Quick links to self-help pages

Last updated: February 23, 2026