Support is support@argorant.com, and a real person reads it. What you put in the first message decides whether the answer comes back in one round or four.
- Write from the address on your account. It proves ownership and saves an entire exchange, and it is required for anything touching billing, deletion or an address change.
- Say what you were doing. The page or the command, not just the outcome. "Creating an export from a saved list" is worth more than "it broke".
- Quote the exact message. Error text, status codes such as 401 or 402, or CLI exit codes. Never paste the API key itself, only its name.
- Include the filter set if the question is about counts or coverage. Industry, roles, size and country tell us in seconds what a description cannot.
- Say what you already tried, so we do not send you back through it.
Before writing, two checks solve a large share of cases: are you signed into the account you think you are, and is the email address confirmed. Both are covered in the articles linked below.
For product documentation, argorant.com/docs covers the API, CLI and MCP surface in detail, and argorant.com/ai is a machine-readable reference you can hand directly to an AI agent.