Gets the details.
Gets it done.

Workflows let your AI agent finish jobs, not just answer questions. For a return, a booking change or a quote, Dazza gathers what’s needed, checks your rules, then sends it where it should go.

THE CONVERSATION → THE JOBWORKFLOW
FROM “CAN I…?” TO DONE.
22 READY-MADE STARTING POINTS
3 WAYS TO FINISH THE JOB
Yes? CUSTOMER CONFIRMS FIRST
1 line DESCRIBE IT, DAZZA DRAFTS IT
COLLECT. DECIDE. DO.
01 / COLLECT

Asks once.
Asks properly.

Each workflow lists the details it needs. Dazza asks for what’s missing, never for what it’s already been told, and checks emails, numbers and dates as it goes.

  • Text, email, phone, number, date, link and choice
  • Required or optional, with help text
  • The customer confirms before it runs
02 / DECIDE

Your rules.
Applied in code.

Add decisions like “refunds over £100 need a manager”. They’re checked by the system, not left to the AI, so the same request always gets the same outcome.

  • Decisions on any detail
  • A different outcome per decision
  • Team approval for the big ones
03 / DO

Done.
And on record.

Send it to your team’s inbox, share a link to book or pay, or call your own system. The customer sees what happened, and so do you.

  • Send to your team, with an email alert
  • Share a link to book, pay or apply
  • Call your system with a signed request
THE CUSTOMER → THE DETAILS 01
EVERYTHING YOUR TEAM NEEDS, FIRST TIME.

Where the job
goes next.

Pick one per workflow, or let your decisions choose between them.

01

Send to your team

The request lands in your inbox with every detail, and the right people get an email.

INBOX + EMAIL ALERT
02

Share a link

Hand the customer a button to your booking page, a form or a payment link, with the details they gave.

BOOKINGS, FORMS, PAYMENTS
03 SCALE

Call your system

Dazza sends a signed request to your API, Zapier, Make or n8n, and replies with what comes back.

SIGNED WEBHOOKS

Helpful by nature.
Careful by design.

Every workflow has checks you choose.
None of them rely on the AI behaving.

01 / CONFIRM

Nothing without a yes.

Dazza shows the customer exactly what it’s about to send and waits for them to press Confirm.

02 / APPROVE

Big calls go to a person.

Mark a workflow, or one decision in it, as needing approval. Your team says yes or no from the inbox.

03 / VERIFY

Proves who they are first.

For anything about a customer’s own account, ask for a code sent to their email, or trust your site’s sign-in.

04 / DRAFT

Describe it. Dazza builds it.

Write what should happen in a sentence. Dazza drafts the details to collect, the decisions and the outcome for you to check.

Workflows,
explained.

Step by step in the help centre.

Do I need a developer?

Not for most workflows. Sending to your team and sharing a link take a few clicks, and there are 22 starting points. Calling your own system needs a web address that accepts a request, which tools like Zapier, Make and n8n give you.

Can Dazza change orders or issue refunds?

Only through your own systems, and only in the ways you allow: a workflow that calls your system, or a tool from a connection such as Stripe. Without one, Dazza collects the request and sends it to your team to do.

Can I see a workflow as a diagram?

Yes. Switch the editor to Canvas to see each step as a card, from what Dazza collects to where the job goes, and drag steps to reorder them.

What stops it doing something it shouldn’t?

Workflows only run when their details are complete and, if you choose, after the customer confirms, your team approves and the customer proves who they are. Decisions are checked in code, not by the AI.

Can I try a workflow before customers see it?

Yes. Set it to Test and it only runs in your preview chat. Calling your system also has a Send a test button.

How do I know what happened?

Every run appears in the conversation with its details and result, and in Insights alongside how often each workflow ran.

YOUR AI CUSTOMER SERVICE AGENT

Less back-and-forth.
More sorted.

A WALL & FIFTH PRODUCTGOOD SERVICE. GOOD FEELING.