Contact Support
Get help with a request, integration, account, or billing issue. A small reproducible example and the relevant identifiers help the team investigate.
Choose a contact channel
| Your request | Contact |
|---|---|
| Product, account, or billing assistance while signed in | Open dashboard chat |
| Technical troubleshooting or an integration issue | Email support@scrapeless.com |
| Custom plans, enterprise requirements, or a sales conversation | Email riley@scrapeless.com |
If you cannot access the dashboard, use email and describe the sign-in problem. If you already have a support conversation, reply there with new details so the investigation stays together.
Before reporting a technical issue
Check Service Status for a relevant incident and choose the relevant question category under FAQ in the navigation for common answers. A status page without a matching incident does not rule out an issue affecting your request.
Reduce the problem to the smallest reproducible case. Include the product and operation, the time and timezone, and the request, task, or session identifier if available. Explain the expected result and what happened instead.
Use this template:
Subject: [Product] Short description of the issue
Product and operation:
Issue started at (date, time, timezone):
Frequency and impact:
Request / task / session ID, if available:
Runtime, SDK version, framework, or MCP client:
Steps to reproduce:
Expected result:
Actual result:
HTTP status and redacted error message:
Minimal redacted request or code:
Recent configuration changes:
Checks already performed:For browser issues, add the session settings and failing navigation or action. For collection tasks, add the input and the task status. For proxy issues, add the proxy type, location, and channel identifier without credentials.
Account and billing requests
Provide your account email and explain the change or discrepancy. For payments, include the transaction reference, date, amount, currency, and affected service or billing period. See Subscription & Billing for common questions before submitting a request.
Custom plans and capacity
Describe the products you need, target sources, expected monthly usage, peak concurrency, geographic requirements, and any service-level requirements. Include your company and preferred contact details so the team can discuss the workload with you.
Protect sensitive information
Remove API keys, authorization headers, proxy passwords, browser cookies, and tokens embedded in URLs. Redact personal data and payment details from screenshots, logs, and response samples. Provide only the information needed to reproduce or identify the issue.
If a credential may be exposed, prioritize invalidating it and replacing it in your application. See Get and protect your API key. Contact support through a private channel for help with containment.