Support
Open a support ticket with the right context, plus pointers to the docs sections, error reference, and status page.
Updated July 2026
Support Documentation
Where to go when something isn't working. We answer faster when you include the right context.
Open a support ticket
Two ways to reach us:
- Support portal — open a ticket at console.whisper.security/support. Best for tracked, async requests.
- Email — support@whisper.security.
Include:
- What you ran. The full Cypher query (or curl command), or the Splunk SPL.
- What you expected. Briefly.
- What you got. The full response — headers and body. For Splunk, the search command output and any
internallog entries. - The request ID. WhisperGraph error responses include a
request_idfield; copy it. - The time. Approximate UTC time of the failed request.
- Your plan tier. Run
CALL whisper.quota()and paste the output.
For Splunk-specific issues, attach the diag bundle: /opt/splunk/bin/splunk diag --collect TA-whisper-graph. See Splunk Troubleshooting.
Ticket template
Subject: [WhisperGraph] <one-line summary>
Plan tier: <Anonymous | Free | Professional | Enterprise>
Region: <if Splunk Cloud>
Time (UTC): <YYYY-MM-DDTHH:MM:SSZ>
What I ran:
<Cypher / SPL / curl command>
What I expected:
<one or two sentences>
What I got:
<full response or error>
request_id: <if present>
Where else to look
- Errors & Rate Limits — every documented HTTP status with recovery steps
- Cypher Best Practices — query rules and known limitations
- Cypher Reference — the read-only dialect: syntax, clauses, functions, cheat sheet
- Whisper Graph — schema, threat feeds, and procedures
- Use Cases — runnable workflows and copy-paste recipes
- AI & Agents — MCP setup and reference
- Splunk Troubleshooting — Splunk-specific issues
- Glossary — definitions for terms you'll see in error messages
Status and incidents
Live status: status.whisper.security
For active incidents we post updates within 15 minutes of detection.