Subscription problem
template.
The Subscription problem template is a ready-made Dazza workflow for subscribers’ delivery, address, cancellation and billing problems. Dazza collects name, email and problem, plus details 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 a subscriber has a problem with their subscription, delivery, address or billing. You can change that sentence, and Dazza follows the new one.
“My magazine hasn’t arrived this month.”
“I’ve moved. Can you update my address?”
“How do I cancel?”
“Why have I been charged twice?”
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 |
|---|---|---|---|
| Name | Short text | Required | — |
| Required | — | ||
| Problem | Choice | Required | Haven’t received an issue, Change of address, Cancel subscription, Billing question, Something else |
| Details | Long 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. Our subscriptions team will sort this and email you.
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
- Print and digital publishers
- Subscription boxes and memberships
- Any business with recurring orders, with the options renamed
Tips for adapting it
- Add a decision on Problem: if it’s “Cancel subscription”, share the link to your account page, where subscribers can cancel themselves.
- Turn on Customer verifies their email first if your team acts on address changes without checking.
- For billing questions, connect Stripe over MCP so Dazza can look up a verified subscriber’s invoices itself.
- Rename the options for your business, such as “Box didn’t arrive” or “Skip a month”.
Can Dazza cancel a subscription itself?
Only through your own systems, such as a Stripe tool connected over MCP, which asks the customer to confirm and needs a verified customer. Without one, Dazza collects the request and your team does it.
Should subscribers verify first?
For anything that changes their account, yes. Turn on Customer verifies their email first (Growth and above) and only the person who owns the email can send the request.
Can Dazza use it on email?
Not as it comes. It asks the subscriber to press Confirm. Email and messaging apps have no buttons, so Dazza only uses workflows there that don’t need one. Turn Customer confirms first off if you want Dazza to use it on email, WhatsApp and the rest.