Support
Write to support@rampsight.com
Every message is read and answered by the person who builds Rampsight. There is no ticket system in front of it and no chatbot.
What to include
Three things make the first reply the last one.
- Your agency name and the site or report concerned — the URL of the site in the dashboard, or the link of the report or statement, so we look at the same thing you do.
- What you expected and what happened instead — a screenshot helps; the exact text of an error message helps more.
- When it happened — the scan time shown in the scan history is enough. Scans are logged, and the log is where most answers come from.
How long we take
Rampsight is operated by one person in Brazil (UTC−3). These are the times we hold ourselves to, not marketing.
| Plan | First reply |
|---|---|
| Scale (priority support) | Within one business day. |
| Starter, Agency, trial | Within two business days. |
| A site that cannot be scanned at all | Same business day — it is usually something we can see in the crawl log. |
Before you write
A few answers that come up often — each one links to where it is explained in full.
- A scan reports zero pages. The address must be the site as it opens in a browser; a site that redirects to another domain (not just to or from
www) is treated as a different site. Sites that block automated browsers cannot be scanned — tell us and we will look at the crawl log. - What a rule means and how to fix it is explained, in four languages, on the rules pages linked from every finding.
- Billing, invoices and cancellation happen on the Billing page of the dashboard; refunds follow the Refund Policy. For invoice questions write to billing@rampsight.com.
- The API is documented at /docs/api; keys are managed in Settings.
- Security reports go to security@rampsight.com — see the security page for what we ask of researchers.