Pass an enquiry to the team
template.
The Pass an enquiry to the team template is a ready-made Dazza workflow for passing questions the AI can’t fully answer to your team. Dazza collects name, email and what it’s about, 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 wants to get in touch with the team about something you can’t fully answer, or asks to be contacted. You can change that sentence, and Dazza follows the new one.
“Can someone from the team get back to me?”
“I’ve got a question about a large order.”
“Who do I talk to about a partnership?”
“It’s not urgent, but I’d like a person to look at this.”
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 | — | ||
| What it’s about | Long text | Required | — |
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 passed that to the team and they’ll be in touch by email.
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
- Any business that wants every enquiry in one place
- Teams replacing or backing up a contact form
- Anything Dazza can’t fully answer from your knowledge
Tips for adapting it
- Rename it for what you get most, such as “Wholesale enquiry” or “Press enquiry”, and change When should Dazza use it? to match.
- Add a Choice detail for the topic, then decisions that send each topic its own way: to the team, to a link, or to a person straight away.
- Change what the customer is told so it says when you’ll reply, and how.
- Keep it short. Three details is enough for most enquiries, and Dazza never asks for something it’s already been told.
How is this different from a handover?
A handover passes the live conversation to your team. This collects a tidy request, so your team can reply later by email and the customer doesn’t wait in the chat.
Who gets told?
The request lands in the Team queue of your inbox and your team gets an email. Each person can turn those emails off in Settings → Notifications.
Can Dazza use it on email or WhatsApp?
Not as it comes. It asks the customer 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.