Submit a story or event
template.
The Submit a story or event template is a ready-made Dazza workflow for story tips, pitches and event listings. Dazza collects name, email, title and details, plus date and link 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 someone wants to pitch a story, send a tip, or get an event or venue listed. You can change that sentence, and Dazza follows the new one.
“I’ve got a story you might like.”
“Can you list our event?”
“How do I send you a press release?”
“Our venue opens next month. Would you cover it?”
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 | — | ||
| Title | Short text | Required | — |
| Date | Date | Optional | For events |
| Link | Link | Optional | — |
| Details | 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 for sending that in. Our editors read everything and will reply if it’s a fit.
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
- Newsrooms and magazines
- What’s-on and listings sites
- Community and trade publications
Tips for adapting it
- Ask for the venue and the price as details, so an event listing needs no follow-up.
- Make Link required if you only consider pitches with a source.
- Add a decision: if Details mentions “press release”, share the link to your press page instead.
- Say how long your editors usually take in what the person is told.
Does Dazza decide whether a story is a fit?
No. It collects the pitch with everything your editors need, and your editors decide.
Can people send photos?
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.
Can Dazza use it on email?
Not as it comes. It asks the person 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.