Support
Reach Cmdop support through the contact page for account, billing, or product problems. Before you write, run cmdop status if a machine is involved — it often names both the problem and the fix. Include the exact error text and the steps to reproduce it, and never send credentials of any kind.
For account, billing, or product help, use the contact page.
Before you write
Many issues resolve faster with one command. If it involves a machine, start
with Troubleshooting — cmdop status names both the
problem and the next step.
What to include
- What you were trying to do, and what happened instead.
- The exact visible error text.
- The steps to reproduce it.
- The output of
cmdop statuswhen a machine is involved.
Never send passwords, API keys, join keys, or connection PINs. No support request needs them.
Common questions
How do I contact Cmdop support?
Use the contact page for account, billing, or product help. Include the exact visible error and steps to reproduce it.
What should I send for a machine issue?
Include what you were trying to do, the exact error text, reproduction steps,
and the output of cmdop status.
Should I send credentials to support?
No. Never send passwords, API keys, join keys, or connection PINs. A support request should not require secrets.
Cmdop