Contact

Talk to the OpenClawAi.run team.

We aim to reply within one to two business days. Before you send a message, check the Status page for incidents and the Docs or FAQ for common issues.

Best first steps

If your instance is stuck, check Status first. For setup or lifecycle questions, visit Docs and FAQ. When you contact us, include your instance ID and timestamp so we can help quickly.

Contact paths

We route all requests through a single support address to keep response times fast. Use the categories below to tell us how to prioritize your message.

Support and onboarding

Questions about instances, BYOK setup, or console issues.

Email: support@openclawai.run

Incidents and outages

Service availability issues or unexpected behavior not covered by the status page.

Email: support@openclawai.run (subject: Incident)

Security concerns

Report vulnerabilities or suspicious activity. Please avoid public disclosure.

Email: support@openclawai.run (subject: Security)

Business inquiries

Questions about higher limits, private deployments, or enterprise needs.

Email: support@openclawai.run (subject: Business)

Before you contact us

A little preparation helps us resolve issues faster. The checklist below highlights the information that shortens back-and-forth and makes your request easier to triage.

Include the essentials

Instance ID, timestamp with timezone, your browser and version, and a short summary of the issue.

Document the steps

Tell us what you clicked and what you expected to happen. Screenshots are helpful but optional.

Never send keys

Do not paste API keys or secrets into support messages. We will never ask for them.

Check the status first

If there is an active incident, we will post updates on the Status page with estimated recovery.

Submit a support request

Use the form below to provide the details we need. This form is a placeholder while we finalize ticketing.

What to include

Provide your instance ID, the time the issue occurred (include timezone), your browser and version, and a short description of what you were doing. If you are using BYOK, do not send your key. We will never ask for it.

If you are reporting a security issue, add "Security" to the subject line and include reproduction steps if possible.

Response times and priorities

We aim to respond to most requests within one to two business days. Incident reports are prioritized above general questions, and security reports receive the fastest triage.

Incident reports

If your instance is inaccessible and the Status page shows no active incidents, mark your email as an incident so we can respond quickly. Include the exact time and your instance ID.

Security reports

Use "Security" in the subject line. Please provide clear reproduction steps so we can validate and patch the issue. We will coordinate a responsible disclosure timeline with you.

General questions

If you are unsure whether a behavior is expected, we may redirect you to the Docs or FAQ. This keeps support cycles short and helps us improve the documentation.

Business inquiries

Requests for higher limits, private deployments, or training should include your target timeline and usage volume. We will reply with next steps or a brief discovery checklist.

We do not provide live chat during the beta. Email support is the fastest and most reliable way to reach the team.

Our support hours follow standard business days. If you contact us on weekends or holidays, expect a reply on the next business day unless there is a critical incident.

We may ask a few follow-up questions to reproduce the issue. Answering those quickly helps us resolve the request faster.

Feedback and product suggestions

We welcome short, focused feedback. If you have ideas for new features, send the smallest concrete example of a workflow you want to run. This helps us evaluate impact quickly.

Helpful feedback format

Describe the outcome, the data sources involved, and how often you would run the workflow. Clear use cases help us prioritize roadmap items without guesswork.

Share limitations too

If a limit blocks your work, tell us. Beta limits are designed to be transparent and adjustable based on real needs.

For feedback, use support@openclawai.run with "Feedback" in the subject line.

We are here to help

OpenClawAi.run is evolving quickly. Your feedback helps us shape a safer, clearer online OpenClaw experience. Reach out any time.