Report a problem
template.
The Report a problem template is a ready-made Dazza workflow for bug reports your engineers can act on. Dazza collects email and what happened, plus steps to reproduce and browser or device if the customer gives them, asks the customer to confirm, then sends the request to your team’s inbox. Every detail, check and message can be changed.
The questions
it answers.
Dazza uses it when the customer reports a bug, an error, or something not working as expected. You can change that sentence, and Dazza follows the new one.
“The export button doesn’t work.”
“I get an error when I log in.”
“The page won’t load on my phone.”
“Something’s broken.”
What it asks for.
Nothing more.
Dazza asks only for what’s missing, never for what it’s already been told, and checks emails, numbers and dates as it goes. Add, remove or reorder details, up to 10.
| DETAIL | TYPE | REQUIRED | CHOICES OR HELP |
|---|---|---|---|
| Required | — | ||
| What happened | Long text | Required | — |
| Steps to reproduce | Long text | Optional | — |
| Browser or device | Short text | Optional | — |
Where the job
goes next.
This template uses Send to your team. Switch to another way to finish, or add decisions that choose between them.
Send to your team
The request lands in the Team queue of your inbox with every detail, and your team gets an email.
AS IT COMESShare a link
Dazza shows a button to a page, such as your booking page or a form, with details filled into the address.
SWITCH TO IT ANY TIMECall your system
Dazza sends a signed request to your system and answers from the reply. Scale and above.
SWITCH TO IT ANY TIMEThanks, I’ve logged this for the team. They’ll email you if they need more detail.
The checks,
out of the box.
Every check runs in code before the workflow does, so none of them rely on the AI behaving. Change any of them per workflow.
| Check | As it comes |
|---|---|
| Customer confirms first | On. Dazza shows the details and waits for the customer to press Confirm. |
| Customer verifies their email first | Off. Turn it on for anything about a customer’s own account (Growth and above). |
| Team approves before it goes ahead | Off. Turn it on to have your team approve or decline each one in the inbox (Growth and above). |
| Starts in | Test, so it only runs in your preview until you set it to Live. |
| Email and messaging apps | Web chat and apps only while Confirm is on. Turn Confirm off to use it on email and messaging apps. |
| Plan | Every plan. Starter includes 3 workflows. |
Who it suits.
How to adapt it.
The groups are a guide, not a rule. Any business can use any template, renamed to fit.
Who it suits
- SaaS and app teams
- Online services and e-learning platforms
- IT support providers
Tips for adapting it
- Let Dazza try first: with your docs in Knowledge, it answers how-to questions before anything is logged as a bug.
- Make Steps to reproduce required for the parts of your product that are hardest to debug.
- Send reports to your tracker: switch it to Call your system (Scale and above) with a webhook to your API, Zapier, Make or n8n.
- Add a Severity choice and a decision that hands “I can’t work at all” to a person.
Can it create Jira or Linear issues?
Through a workflow that calls your system (Scale and above), directly or with Zapier, Make or n8n. By default, reports land in your Dazza inbox.
Can users attach screenshots?
Yes. Customers attach photos and PDFs in the chat, or send them by email and on messaging apps. Dazza looks at them before it answers, and your team sees them in the conversation. See Photos and PDFs from customers.
Does it know which user it is?
If your app signs users’ logins, yes: they’re verified, and their email is filled in for them. See Verify your customers.