> ## Documentation Index
> Fetch the complete documentation index at: https://docs.z360.biz/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your first Work pipeline

> Build a Work pipeline, connect its form, and run a safe test before real requests arrive.

A **pipeline** is the recipe for one kind of job. You build it once, and every request that comes through it becomes a Work Item with its own agent.

This guide takes you from nothing to a tested pipeline. Plan for about 30 minutes. Most of that time goes into the goal.

## Before you start

Make sure you have:

* **Work turned on.** You see **Work** in the Z360 sidebar. If you see **Leads** instead, your organization uses Inquiries, the legacy system. See [Coming from Inquiries](https://docs.z360.biz/guides/work/frequently-asked-questions.md#coming-from-inquiries).
* **At least one sending channel.** A connected email address (**Settings → Emails**) or a phone number (**Settings → Phone → Manage**). The agent can only contact people from channels you own.
* **Wallet balance.** The agent's AI usage is billed to your wallet. See [Manage your prepaid wallet](https://docs.z360.biz/guides/settings/manage-prepaid-wallet-usage-controls-and-statements.md).
* **A job in mind.** Pick one real, repeatable job. Write down who needs to be contacted and what "finished" means. You will need both for the goal.

## Build the pipeline

Go to **Settings → Pipelines** and click **Add New**. You can also get there from **Work → Manage pipelines**.

The pipeline has seven steps. Save each step to unlock the next one.

**1. Basic Info: name, stages, and sources**

Give the pipeline a **Pipeline Name** your team will recognize, such as "Maintenance requests", and a short description.

Add your **Stages**. These are the milestones a job passes through, in order. Three to five is plenty.

Add **Sources** if requests arrive from more than one place, such as "Website" and "Tenant portal".

> [!TIP]
>
> Name stages after what has happened, not what someone should do. "Vendor contacted" tells you more at a glance than "Contact vendor".

**2. Intake Flow: the form**

Build the form people fill in to start a job. Ask only for what the agent needs to do the work.

A Work form does not need name, email, and phone fields the way a lead form does. If the job is about a property or an order, ask about that. Do include contact details for anyone the agent must reach.

> [!NOTE]
>
> The answer to the first **Short Answer** field becomes the start of the Work Item's title, followed by the pipeline name. Put your most recognizable field first. With "Property address" first, a title reads "14 Maple St, Unit 2 | Maintenance requests".

**3. Agent: the rules and the goal**

This step decides how the agent behaves. It has four parts:

* **[Approval policy](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md#approval-policy)** — how much the Work agent may do without asking. For your first pipeline, choose **Ask for approval** so you can watch every move.
* **[Reasoning mode](https://docs.z360.biz/guides/working-with-ask-z/approvals-and-reasoning.md#intelligence)** — how capable the AI model is. New pipelines start on **Everyday**. Choose **Advanced** when a job needs planning across several people.
* **Mass outreach** — leave this off for now. Turn it on later if you expect large batches. See [Mass outreach](https://docs.z360.biz/guides/work/mass-outreach.md).
* **Goal** — your instructions to the agent, in plain language.

The goal is the part that matters most. Take your time with it, and follow [Write a goal the agent can follow](https://docs.z360.biz/guides/work/write-a-pipeline-goal.md).

For the Work-specific controls, such as changing the rules for one Work Item, see [Approvals and control](https://docs.z360.biz/guides/work/approvals-and-control.md).

![The Agent step of a pipeline. Approval policy and Reasoning mode selectors are at the top. Below them, the Mass outreach switch is on and two buckets are listed, each with a bucket name, a channels selector, and a description. The Goal box is at the bottom with a pencil icon on its right.](https://mintcdn.com/z360-fe526747/sOi4qySNiv1nnWzq/images/work/pipeline-agent-step.png?fit=max\&auto=format\&n=sOi4qySNiv1nnWzq\&q=85\&s=c8010be8a65a252cfcc3d5a459a28fcd)

The Agent step. In this example Mass outreach is switched on, with two buckets.

**4. Schedule: working hours**

Set the **Weekly Availability** for this pipeline. The agent times its outreach inside these hours, so nobody gets a follow-up at 2 AM. See [Working hours](https://docs.z360.biz/guides/work/approvals-and-control.md#working-hours).

**5. Branding: how the form looks**

Set the header text, button text, and colors so the form matches your brand.

**6. Configurations: defaults for new Work Items**

Choose what every new Work Item starts with:

* **Default Assignee(s)** — the teammates who own new Work Items. They get a notification for each one.
* **Default Stage** — where new Work Items start. This is usually your first stage.
* **Default Source** — used when a request does not say where it came from.

You can also turn on a consent checkbox and choose what people see after they submit: a thank-you message or a redirect to your website.

> [!NOTE]
>
> **Pipeline Outbound Call Limit**, **Cost Per Lead**, and **Value Per Secured Lead** are used by lead pipelines. They do not change how a Work pipeline runs today, so you can leave them as they are.

**7. Integration: connect the form**

Your pipeline is ready. Choose how requests will reach it:

* **Direct Link** — a page you can share in an email, a text, or a QR code.
* **Embed Code** — paste it into your website to show the form there.
* **API / Webhook** — let another tool send requests straight to the pipeline.

For more on sharing forms, see [Share Z360 forms via direct link and embed code](https://docs.z360.biz/share-z360-forms-via-direct-link-and-embed-code.md).

## Test it before you share it

Run one test with yourself as the customer. It takes five minutes and shows you what your customers and your team will see.

**1. Submit the form yourself**

Open the **Direct Link**. Fill in the form with your own phone number or email address as the contact, then submit.

**2. Find the Work Item**

Open **Work** and look in **All Work**. For a few seconds your test may show **Agent thread starting** under its title.

**3. Open it and watch the agent**

Click the title. The agent's chat opens with the **Work Summary** panel beside it. With **Ask for approval** on, the agent asks before each action. Read what it plans to do, then approve.

**4. Play the customer**

When the message reaches your phone or email, reply the way a real customer would. Then try not replying, and check that the follow-up arrives when your goal says it should.

**5. Check the result**

Did the stage move when you expected? Did the agent stop and ask where the goal says to ask? If something is off, fix the goal and run the test again.

### What to check after the test

* The Work Item title is easy to recognize in a list.
* The first message sounds like your business.
* Messages came from the email address or phone number you expected.
* Each stage changed at the right moment.
* The agent status ended as **Completed** or **Failed**, not stuck on **In progress**.

When the test runs the way you want, share the link or embed the form. Once you trust the pipeline, consider moving the approval policy to **Auto**.

## Tips

* **Start with one pipeline for one job.** A pipeline that tries to cover three different jobs needs a goal nobody can follow, including the agent.
* **Copy what works.** To build a similar pipeline, open the menu on a pipeline's row in **Settings → Pipelines** and duplicate it.
* **Pause without deleting.** Switch off **Active Status** in the pipeline list to stop the form from accepting new requests.
* **Let Ask Z help.** Ask Z can create and update pipelines for you. Describe the job and it will ask what it needs to know.
* **Re-test after every goal change.** A small wording change can alter what the agent does.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.