Accounts, guilds, halls, parties, voice, chat, billing, safety, and privacy.
- Your Shout account email
- Guild and hall names, when relevant
- What you expected and what occurred
Product & service support
Choose the product or service involved. Each option opens an email to our team with the topic filled in. You can also contact us directly.
Product & website support
Each button starts an email with the relevant topic already in the subject. Include the account email you use for that product and a concise description of what happened.
Accounts, guilds, halls, parties, voice, chat, billing, safety, and privacy.
Mailbox connections, message verdicts, sender or link analysis, accounts, and billing.
Domain scans, SPF, DKIM, DMARC, TLS, monitoring, accounts, and billing.
Scans, exposure findings, guided fixes, monitoring, accounts, and billing.
Workspace access, device enrollment, monitoring, patching, remote tools, and job results.
Content changes, website issues, hosting, and ongoing care for LabCMD website projects.
Managed technology
Name your organization, the affected person or device, and what is preventing work. Call for an active issue or start an email when the details can be sent safely.
Email managed supportOther requests
Before you send
Include the affected product or service, your account email, the approximate time and time zone, steps to reproduce, and a redacted screenshot when it helps.
Quick answers
Copy support@labcmd.com into your preferred email app. Add the product or service name to the subject and describe the issue.
Call the support line for an active issue, or email managed support when the request can be described without passwords, keys, codes, or other secrets.
Email support@labcmd.com from the account address when possible. Name the product, but never include your password, MFA code, or recovery material.
Use the privacy and data request path above. Identify the product and account, then describe the request. LabCMD may need to verify that you control the account before acting.
Begin with the security-report email path and a concise impact summary. Do not include live credentials, private keys, unnecessary personal data, or destructive proof of concept in the first message.