Check an account
template.
The Check an account template is a ready-made Dazza workflow for plan, usage and billing questions from verified users. Dazza sends email to your own system, once the customer has proved who they are, and answers with what your system replies. Every detail, check and message can be changed.
The questions
it answers.
Dazza uses it when the customer asks about their plan, usage, billing status or account. You can change that sentence, and Dazza follows the new one.
“Which plan am I on?”
“When does my subscription renew?”
“How many seats have we used?”
“Is my account active?”
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 | — |
Where the job
goes next.
This template uses Call your system. 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.
SWITCH TO IT ANY TIMEShare 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.
AS IT COMESPOST https://your-system.example/dazza
content-type: application/json
x-dazza-event: action.run
x-dazza-timestamp: 1793097720
x-dazza-signature: sha256=9f2c…
{
"event": "action.run",
"action": {
"id": "act_…",
"name": "Check an account"
},
"run": {
"id": "run_…",
"test": false
},
"inputs": {
"email": "jamie@example.com"
},
"conversation": {
"id": "cnv_…",
"pageUrl": "https://yourbusiness.com/…"
},
"customer": {
"email": "jamie@example.com",
"name": "Jamie",
"verified": {
"email": "jamie@example.com",
"via": "code",
"userId": null
}
},
"sentAt": "2026-10-27T10:42:00.000Z"
}{
"message": "You’re on the Team plan, renewing on 3 November. You’ve used 34 of 40 seats."
}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 | Off. It runs as soon as the details are complete. |
| Customer verifies their email first | On. The customer proves who they are with an email code or your site’s signed login before it runs. 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 | Used as it comes, since it needs no button. It runs once the customer is verified, such as a sender whose domain passes DMARC. |
| Plan | Scale and above. |
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 apps
- Memberships and subscriptions
- Utilities and service accounts
Tips for adapting it
- Sign your users’ logins (
data-user-tokenorDazza.identify), so they’re verified without an email code. - Reply with the fields customers ask about, such as plan, renewal date and usage, plus a
message. - Never return passwords, full card numbers or anything a customer shouldn’t see in a chat.
- If your billing is in Stripe, Stripe’s MCP server can answer many billing questions without any code.
How does Dazza know who’s asking?
From a code sent to the user’s email, or a login your app signs. Your system gets the verified email as customer.verified.email.
What does my system receive?
A signed JSON request with the email, the conversation and how the user was verified. Reply with JSON within 10 seconds.
Which plan do I need?
Calling your own system is on Scale and above. Stripe over MCP is on Growth and above.