Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in

How to contact QuanticData support, and what to put in your first message

Contacting QuanticData support in three steps: open the chat in the dashboard, describe the problem with the order id of the plan, ask for a person; the card lists what the first message should carry: the order id, the exact error, the time with its time zone.
Contacting QuanticData support in three steps: open the chat in the dashboard, describe the problem with the order id of the plan, ask for a person; the card lists what the first message should carry: the order id, the exact error, the time with its time zone.

To contact QuanticData support, open the chat in your dashboard, which is signed in as you, or write to hello@quanticdata.io with the order id of the plan. In the chat you can ask for a person; when someone from support picks the conversation up, they reply in the same window. Below: each channel, what to send, and how to follow a request.

Everything here was checked on 21 November 2026 against the pages of this site and the sign-in page of the dashboard. Where a page of ours states something, we quote it.

The channels at a glance

ChannelWhere it isUse it for
Dashboard chatInside the dashboard, after you sign inAnything about your account: a plan, a payment, proxy lines, the API
Site chatOn the pages of this site and on the sign-in and sign-up pagesQuestions before you have an account, and help with signing up
E-mailhello@quanticdata.ioAnything, written from the address of your account
Abuse deskabuse@quanticdata.ioReports about traffic that came from one of our IPs
Enterprise formThe enterprise contact pageVolume requests and documents for procurement

If you have an account, start from the dashboard chat: it is the only channel that already knows who you are.

The dashboard chat: the direct line for account questions

The dashboard has a chat with our assistant on its pages. Our index for AI tools describes the channel as "the dashboard chat signed in as the person", and that is the point of it: the request is tied to your account, so support can look at the plan straight away.

The assistant answers first. When you want a person, ask to talk to one. The conversation then goes to support. When a person picks it up, the chat states that a human is replying, and from that moment what you type goes to the support agent. Their answers appear in the same window, so the whole exchange stays in one place.

The site chat: before you have an account

The same chat window is on the pages of this site and on the sign-in and sign-up pages of the dashboard, so you can ask a question while you are filling in a form. It needs no account. Its labels follow the language of your browser in eight languages: English, Italian, Spanish, German, French, Portuguese, Dutch and Polish.

Here too you can ask for a person. When someone from support joins, the header reads "Live support · a human is replying", and you can send a picture with the "Send a photo" button: JPEG, PNG or WebP, under 2 MB. That covers a screenshot of an error or of a tool's proxy settings, with passwords and card numbers covered.

The site chat does not see account data. For a question about a specific plan, payment or invoice, sign in and use the dashboard chat, or send the order id by e-mail.

E-mail: one address for everything

The About page gives one address "for anything: support, sourcing questions, partnerships, press": hello@quanticdata.io. It is also the contact address in our Terms and in our Privacy Policy.

Two habits make an e-mail quick to handle:

  • Write from the address of your account. Support can then match the message to your account.
  • Put the order id in the message. Our index for AI tools gives the same instruction to software agents: write to the address "with the order id".

If an AI agent works on your account, the same index tells it what to do before writing: check GET /public/orders and GET /public/balance first. Both endpoints are in the API reference, and they answer the two most common questions, whether the order went through and whether the balance covers the next one.

What to put in the first message

A request moves fastest when the person reading it can reproduce what you saw. These are the details that make that possible, in order of usefulness.

  1. The order id of the plan. It names the exact plan among the ones on your account. The API lists it for every plan: GET /public/proxies returns an orderId for each.
  2. The product. Residential Basic, Residential Premium, Mobile, ISP, Datacenter, IPv6, or the name of the Data API endpoint.
  3. What you ran. The tool and its version, or the command, with the password and the API key removed. Host, port and the username options (country, session) are what matters.
  4. The exact answer. The status code and the error text, copied, not retold. "407 Proxy Authentication Required" and "connection timed out" lead to different places; "it does not work" leads to a question back. With curl, the output of -v has everything; delete the Proxy-Authorization and Authorization lines before you send it, because they carry your password or key.
  5. When it happened. Date, time and time zone, for example 2026-11-21 14:05 UTC.
  6. The target. The site or URL you were opening and the country you asked for.
  7. For a Web Unlocker call, the request id. The API reference lists the response header that holds it as the id "to quote to support", and its error table gives the same instruction: "Retry; if it persists contact support with the request_id."
  8. A screenshot, when the problem is on a screen: the proxy form of your tool, a message in the dashboard. Crop or cover any password, key or card number first.

Never send your proxy password, your API key, your account password or card details (number, expiry, CVC), in chat or by e-mail. Support does not need them: the order id is enough to find the plan. The page for AI agents has the same rule, "Never the key in chat", and says where a key is replaced: you can rotate or revoke it from the API keys page. How to use an API key shows how to keep it in an environment variable instead of in a command.

A message with these parts looks like this:

Order id: ORDER_ID
Product: Residential Basic
Tool: curl 8.x on Windows 11
What I ran: one HTTPS request through the gateway, username with country us
Result: 407 Proxy Authentication Required (-v output attached, Proxy-Authorization line removed)
When: 2026-11-21 14:05 UTC, repeated three times
Target: https://example.com/, country us
What I already checked: balance, plan active, credentials copied again from the dashboard

The last line saves the most time. Many problems have a known cause that you can rule out yourself in a minute: the proxy not working checklist goes through them in order, proxy error codes explains each status code, and 407 Proxy Authentication Required covers credentials. If the problem is still there after that, saying what you ruled out lets support start from the next step.

How to follow a request and add information

The conversation where you asked for a person is the request: you follow it where you opened it. On the site chat, come back in the same browser; for anything about an account, use the dashboard chat.

  • Open. While support is on the conversation the chat says that a human is replying, and the message box writes to the support agent. Replies from the team appear there.
  • Adding information. Write it in the same conversation. A new detail, a second screenshot or the result of a test you were asked to run all belong under the original question, where the agent already has the context. Opening a second conversation for the same problem splits the facts in two.
  • Closed. When the matter is settled the conversation is closed, and the chat shows that the conversation is closed. For a new question, or a follow-up later, start a new chat and name the plan again with its order id.

By e-mail the rule is the same: reply on the same thread instead of sending a new message, so the earlier messages travel with your answer.

Abuse reports, enterprise requests and privacy requests

Three kinds of request have their own address or form, and a published statement of what happens next.

  • Abuse reports. If traffic from one of our IPs harmed your site, the Acceptable Use Policy says: write to abuse@quanticdata.io "with the IP, the timestamp with timezone, and a log excerpt. We answer abuse reports within one business day".
  • Enterprise requests. The enterprise contact page has a form for volume requests. The page asks you to "name the layer, the markets, the expected monthly volume and how the output will be used", and states: "The enterprise team answers by email with a scope".
  • Privacy requests. To access, correct, delete or export your data, the Privacy Policy says to e-mail hello@quanticdata.io.

Which channel for which question

Your questionBest channelSend with it
A plan, proxy lines or a connection errorDashboard chatOrder id, command, exact error, time
A payment or an invoiceDashboard chat or e-mailOrder id or invoice number, date, payment method
An API answer you did not expectDashboard chat or e-mailThe endpoint, the parameters and the request id when the answer has one
You cannot sign in or sign upSite chat on the sign-in pageThe e-mail of the account and the message on screen
Which product fits a job, before buyingSite chatThe target sites, the countries and the volume
A large or custom volumeEnterprise formLayer, markets, monthly volume

Sources & further reading

FAQ

Quick answers on contact QuanticData support.

Something else? Ask us

How do I contact QuanticData support?

Open the chat in your dashboard and ask your question; it is signed in as you. You can also use the chat on the site, or write to hello@quanticdata.io with the order id of the plan.

Can I talk to a person?

Yes. In the chat, ask to talk to a person. The conversation goes to support, and when someone picks it up the chat shows that a human is replying and their answers arrive in the same window.

What is the QuanticData support e-mail?

It is hello@quanticdata.io, the address the About page gives "for anything: support, sourcing questions, partnerships, press". abuse@quanticdata.io is the address for abuse reports.

What should I include in a support request?

The order id of the plan, the product, what you ran with the password removed, the exact status code or error text, the time with its time zone and the target site. For a Web Unlocker call, add the request id.

How do I check the status of my request?

Open the conversation where you asked for a person. While it is open the chat says that a human is replying and you can write to the agent; when it is settled the chat shows that the conversation is closed.

How do I add information to an open request?

Write it in the same conversation, or reply on the same e-mail thread. The agent then reads the new detail under the original question, with the context already there.

Should I send my proxy password or API key to support?

No, and no account password or card details either. The order id is enough to find the plan. Remove the password and the key from any command or screenshot you send, and rotate a key that was exposed from the API keys page.

An account with the chat built in

Sign up without a card, get $2 of credit every month, and ask your first question from the dashboard chat.

Related reading