Fewer tickets.
Better ones.
How-to questions answered from your docs. Bug reports that arrive with steps and a browser. Account questions answered from your system for signed-in users, and demo requests sent straight to your calendar.
For the questions your docs already answer.
Most tickets are a doc away. Dazza finds the page and walks users through it, and when it’s a real problem, collects what engineering will ask for.
See it in the demoReady on day one.
Yours to change.
Ready during setup. Point them at your own tools with a webhook.
Report a problem
Bug reports with steps and a browser, not just “it’s broken”.
Check an account
Plan, usage or status from your system, for verified users.
Book a demo
Send prospects to your demo calendar.
Check something in your system
Any lookup your API can answer.
Pass an enquiry to the team
Anything else, as a tidy request in your inbox.
Create issues in your tracker
Through a webhook to your API, Zapier, Make or n8n.
Your users are signed in.
Dazza knows it.
Sign each user’s email on your server and pass the token to the widget. Dazza treats them as verified, so account checks run without an email code, and your API is told who’s asking.
- HS256 tokens, signed on your server
- Works in single-page apps
- Verified identity sent with every request
Can it read our docs site?
Yes. Point Dazza at it and it reads every page in your sitemap: up to 1,000 on Growth and 5,000 on Scale.
Can it create issues in Jira or Linear?
Through a workflow that calls your system, directly or via Zapier, Make or n8n. By default, bug reports land in your Dazza inbox.
Can it see user accounts?
Only through your own API, and only for users who are verified by your app’s signed login or an email code.