Support and Diagnostics
Create in-app support tickets with request types, optional screenshots, and previewable redacted diagnostics.
Create support requests from the app
TriggerDeck includes a Support screen in the More menu for product questions, bug reports, contact requests, and feature requests. The form keeps the request type explicit so users can send the right amount of context:
- Bug Report and Contact Support can include a redacted support file and optional screenshots.
- Feature Request focuses on the idea and does not require diagnostic files.
- Optional screenshots use the system photo picker and stay under the support attachment limit.
Flow shown on screenshot
Support ticket creation
Open More, choose Support, select a request type, enter an email address, subject, and message, then review the Files section. Use this view to explain how users can include screenshots and preview the redacted support file before submitting.
Preview redacted diagnostics before sending
For bug and support requests, the app can attach a generated support file. The file is meant to help troubleshoot app state without sending Zabbix API tokens or customer credentials.
The preview step matters: users can inspect the generated support file before submitting the ticket, then decide whether to include it.
The redacted support file can include app and device diagnostics such as app version, build number, iOS version, locale, time zone, local server identifiers, Zabbix API version and support status, push status, app settings, and recent redacted errors.
Use shake-to-report for quick bug reports
When something goes wrong during use, shake-to-report can open the same support flow as a bug report entry point. The user still controls the message, optional screenshots, and whether the redacted support file is included before anything is submitted.
Privacy boundaries
Support tickets are user-initiated. TriggerDeck does not send customer Zabbix API tokens, Authorization headers, server passwords, or raw JSON-RPC credentials in support submissions. Users should still avoid typing secrets into the message body or attaching files that contain private monitoring data.