Skip to content
EffiZoom

AgencyZoom how-to and templates

AgencyZoom workflows for service requests and renewals

How to set up AgencyZoom service pipelines so every request has an owner, a stage and a confirmation, and where renewal workflows fit beside them.

Co-Founder, EffiZoom; licensed insurance agent

· Updated · 5 min read

A good AgencyZoom service workflow does three things for every request: it gives the request an owner, it puts it in a stage that says what happens next, and it tells the customer you have it. Build those three into each service pipeline and most of the chaos goes away. Keep claims in their own pipeline, keep routine service (add a driver, a certificate, a payment question) in another, and let renewals run on their own timeline beside them.

That is the shape. Here is how to build it.

Separate claims from service first

AgencyZoom’s guidance is direct on this: keep Claims separate from the Service pipeline. Routine service requests, adding a driver or sending a certificate, are mostly in your control. Claims are not. You build both under My Agency, Pipelines, and the pipeline you pick is only a default, so a CSR can still choose a different one when a ticket is a special case. Source: Service Pipelines.

The same article notes that Onboarding, Renewals and Surplus Renewals pipelines work a little differently from Service and Claims. Treat them as their own thing, not as more service stages.

Give every ticket an owner

AgencyZoom calls this out in the same article: when a ticket is created, focus on who owns it. That is the whole game in service. A request with no owner sits in a stage looking handled while nobody is handling it.

Two settings help here. You can control who sees each service pipeline, everyone, a job role or specific people, so a CSR is not wading through pipelines that are not theirs. And a task is one of the touchpoint types you can add in Lifecycle Automation, which puts the work on a person’s list instead of leaving it in a column. Source: Build Automation for Sales Pipelines.

A simple test: pick any open ticket and ask who is supposed to touch it next and by when. If the answer is not on the ticket, the workflow has a gap.

Stages that say what happens next

Most agencies need fewer service stages than they think. A starting point:

  1. New request. Just landed. Someone reads it and decides what it is.
  2. Working. The owner is on it.
  3. Waiting on carrier. The ball is with the underwriter or the carrier’s service center.
  4. Waiting on customer. You need a signature, a document or an answer.
  5. Done. Completed with a resolution.

The two “waiting” stages earn their place. They are where requests stall, and splitting carrier from customer tells you who to chase. A ticket that sits in Waiting on customer for five days needs a reminder to the customer. One that sits in Waiting on carrier needs a call from your CSR. Different stage, different automation.

If you take calls through a phone system that creates tickets from transcriptions, give those their own entry stage so raw transcripts get a quick review before they mix with clean requests. There is a walk-through of that in Service Pipeline Mastery.

The automation that belongs in service

Service automation is smaller than sales automation, and that is on purpose. AgencyZoom documents that automation can be attached to all service pipelines, with examples like a text or email confirming you received the request, or a customer satisfaction request. Source: Service Pipelines.

That points at the three touchpoints that pay off:

  • On New request: a short confirmation to the customer. “We got your request to add a driver. Sarah is on it.” This one message cuts down the “did you get my email” calls.
  • On Waiting on customer: a reminder after a couple of business days, asking for the one thing you need.
  • On Done: a short note that it is finished, and, if you use one, a satisfaction request.

Everything else in service should be a task to a person, not a message to the customer. Service customers want the thing done, not a drip.

Where renewals fit

Renewals are not a service request. They are a timeline that runs off the policy’s expiration date, and they work best as their own sequence: a review well before the date, a clear ask closer in, and a thank you after. The cadence and the messages are covered in Best Renewal Email Sequences for Insurance Agencies in AgencyZoom.

The link between the two is the hand-off. When a renewal review turns up a change, a new car, a new driver, a remodel, that change becomes a service request with an owner in your Service pipeline. Do not try to work the change inside the renewal sequence. The renewal keeps its timeline. The change gets its own ticket.

Service requests from other systems

If your phone system, website form or answering service should create tickets, AgencyZoom’s January 2026 release expanded the Service Request API with endpoints to create, update and complete service requests, and to read service pipelines, stages, categories, priorities and resolutions. It also added Zapier triggers for when a request is created or its status changes. Source: Release Updates, January 2026.

That is useful, with one warning. A request created by another system still needs an owner and a stage. Automating ticket creation without fixing ownership just makes the pile grow faster. AI scales exactly what you give it, clean or messy. So does a form.

Doing it yourself, or having it written

Setting up service pipelines is an afternoon for an admin who knows how the agency actually works. Write the stages on paper first, put an owner rule next to each one, then build the three touchpoints above and test them on yourself. The setup guide has the Lifecycle Automation menu path.

If you want the messages and tasks written for you, the Architect reads your real AgencyZoom setup, pipelines, stages, lead sources, tags and team, asks about your agency, and builds the package in about two minutes once the plan is set. Texts are checked to stay under 160 characters, subject lines between 30 and 60, and it only uses names that exist in your account. It writes English and Spanish in one package. It only reads your AgencyZoom. You import the files yourself, they arrive switched off, and you read every line before anything runs.

The Architect is part of EffiZoom Pro, $39 a month or $374 a year, with a 7-day trial.

FAQ

Questions about this topic

Should claims and service be in the same AgencyZoom pipeline?

No. AgencyZoom's own guidance encourages agencies to keep Claims separate from the Service pipeline, because routine service requests are within your control and claims are not.

Can AgencyZoom service pipelines have automation?

Yes. AgencyZoom documents that automation can be attached to all service pipelines, for example a confirmation text or email that you received the request, or a customer satisfaction request.

Can other systems create AgencyZoom service requests?

Yes. AgencyZoom's January 2026 release expanded the Service Request API with endpoints to create, update and complete service requests, plus Zapier triggers when a request is created or its status changes.

Keep reading

AgencyZoom how-to and templates · Guide

AgencyZoom automations for new leads, stage by stage

What AgencyZoom automation should do in New, Contacted and Quoted, and in Smart Cycle, with the settings that decide whether a new lead hears from you on time.

· 5 min read