How to Ask for Help

Where to go when something isn't working. We answer faster when you include the right context.

Open a support ticket

Email: support@whisper.security

Include:

1. What you ran. The full Cypher query (or curl command), or the Splunk SPL.
2. What you expected. Briefly.
3. What you got. The full response — headers and body. For Splunk, the search command output and any internal log entries.
4. The request ID. WhisperGraph error responses include a request_id field; copy it.
5. The time. Approximate UTC time of the failed request.
6. 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

• FAQ — common questions
• Glossary — definitions for terms you'll see in error messages
• Error Codes & Rate Limits — every documented HTTP status with recovery steps
• Known Limitations — what WhisperGraph doesn't know
• Splunk Troubleshooting — Splunk-specific issues
• Changelog — recent changes that may affect you

Status and incidents

Live status: status.whisper.security

For active incidents we post updates within 15 minutes of detection.

Security disclosure

Found a security issue? Don't open a ticket — email security@whisper.security. PGP key on the console.