Your team's avoiding five awkward calls a week. An outbound voice agent makes them all.

It's Tuesday. Your office manager has the Xero AR tab open. Five invoices, all 21 days overdue.

She's been looking at the same tab on Wednesday and Thursday too.

Nobody's been called.

Your office manager isn't lazy. She's just human.

Calling a customer for money is the worst job in your business. Even a polite chase ages the relationship. Your team feels it before they pick up the phone.

So they don't.

Five awkward calls a week, every week. The cost compounds in your debtor days, your bank balance, and the quiet erosion of how your team feels about Monday.

Want a system that makes the calls without the cringe?

The pattern: the system fires, not your team

This is Playbook 1 from the voice agent column we have been running.

Five playbooks beyond the AI receptionist. This one's the most-applicable for you. Every NZ business has at least one awkward outbound call category nobody on the team wants to make.

The pattern: an outbound trigger reverses the receptionist model.

The receptionist waits for the customer to call you.

The outbound trigger fires when something happens in another system. Then a voice agent makes the call you've been avoiding.

Same agent. Same minute pricing. Same 800ms first-token reply that doesn't sound like a robot reading a script.

Different job.

Four flavours that all ship in production today. Pick the one that matches the awkward call your team's hiding from.

Trigger 1: Xero says invoice is 21 days overdue

The most universal one. Got accounting? You're a candidate.

Every accounting system flags overdue debtors. Almost no NZ business actually chases them on day 21.

Want to see your flow?

Xero stamps an invoice 21 days overdue. Webhook fires. The voice agent dials the customer. Friendly, warm, no scolding.

Agent: "Hi, this is Tane calling from Heron Plumbing. We just noticed invoice 4-0-2-7 from late February is still on your account. Just want to check it didn't get lost. When can we expect it to land?"

Customer says, "Sorry, sorry, I'll do it tonight."

Agent: "Sweet as. I'll note that down. If anything changes, give us a ring back on this number. Cheers."

Your agent logs the answer. Tags the invoice "Promise to pay: today". Triggers a 24-hour follow-up if no payment lands.

Emails your AR mailbox a single 5pm digest of the day's calls and outcomes.

Your office manager wakes up Wednesday. Five awkward calls already done.

Three promises-to-pay logged. Two need a human follow-up because the customer's pushing back on work quality. The agent flagged both.

She makes two calls instead of five. About work quality, not money. Different conversation entirely.

You're not chasing money any more. You're triaging exceptions.

Trigger 2: Your CRM flags a dormant lead

This is the one we wrote up in detail. A US recruiter ran an outbound voice agent against 44,000 dormant HubSpot contacts. Booked 12 meetings in week one with leads that had been cold for over a year.

The pattern transfers directly to NZ.

Your CRM tags a contact "no engagement in 90 days". Trigger fires. Voice agent calls.

Agent: "Hi Pete, it's Maia from Coastal Mortgage. We chatted in February about the Mount Maunganui investment property. Did you end up moving forward, or has the plan shifted?"

Pete says, "Oh yeah, we put it on hold. The wife wants to wait till Spring."

Agent: "Fair enough. Mind if I drop you a 60-second voice memo when the next OCR call lands? Could change your maths."

Pete says yes. The agent logs the consent. Updates the CRM stage. Triggers the 90-day re-check.

Pete's not buying today. Pete's not lost either.

We covered the full HubSpot deployment in HubSpot dormant leads — 44,000 contacts, 12 meetings booked.

The mechanic transfers to whatever CRM you run. The trigger source changes. The flow doesn't.

(The first time we ran this on a real client's HubSpot, their sales manager rang me to ask if we'd hired three new BDRs overnight. We hadn't. Same agent.)

Trigger 3: A patient hasn't shown up to the follow-up clinic in 14 days

Healthcare flavour. The US version of this is running across 29 acute-care hospitals.

Patient gets discharged, AI calls 48 hours later to check on recovery. Escalates symptom flags to your on-call nurse.

Want the Christchurch version? Same flow, smaller scale.

A cardiac patient leaves Christchurch's Forte Health on a Tuesday. The clinic booked their follow-up for two weeks later. They never confirmed.

Trigger fires at day 12. The voice agent calls.

Agent: "Hi Mr Patel, this is Aroha from Forte Health. I'm just checking in on your recovery and confirming your appointment with Dr Chen on Thursday at 11am. How are you feeling?"

Mr Patel says, "Oh actually I've been feeling much better. I was going to cancel."

Agent: "Glad to hear it. Dr Chen still wants to see you for the routine check though. Should we keep the slot, or move it later in the month?"

Mr Patel says move it. Your agent reschedules in his calendar, sends an SMS confirmation, and updates Forte's PMS.

(He would have been a no-show. The clinic would have charged the cancellation fee. Mr Patel would have had a quiet row about the bill at his next visit. Nobody ends up in that loop.)

Trigger 4: A renewal date is two weeks away and the price went up 18%

Your most expensive customer to lose is the one who didn't know their renewal was coming.

They open the email. They see the new number. They Google "alternatives". They never reply.

You've trained them to leave by surprise.

(Fastest way to lose a loyal client: let them feel ambushed by their own renewal email.)

Hertz built the proactive version of this for car rentals.

A US insurer ran the same play for renewals. The AI voice agent calls your customer two weeks before the renewal email lands.

Walks the increase. Explains the why. Offers a longer-term commitment if they want to lock the old rate.

Your Auckland insurance broker version: client renewal lands in 14 days, premium up 18%. Trigger fires.

Agent: "Hi, this is James from Concord Insurance. I noticed your home and contents renews on the 23rd, and the new premium's coming in 18% higher. I wanted to walk you through why before the email lands. Got two minutes?"

The customer says yes nine times out of ten. The alternative is opening their inbox and feeling ambushed.

Agent walks the change. Explains the structural shift in the reinsurance market this year. Offers a 24-month lock at the old rate if they're happy to commit.

Half the customers take the lock. The other half feel respected. None of them rage-cancel.

Your Hamilton mortgage adviser version of this? Rate change lands. Adviser's clients all get a friendly heads-up call before the formal letter goes out. Their book retention goes from 71% to 89%.

Same pattern. Different trigger source. Different system update at the back end.

What every outbound trigger needs

Three pieces. None of them are exotic.

A trigger source. Xero, HubSpot, Salesforce, Patient Manager, your scheduler, your renewals table.

Anything that can fire a webhook or get polled by an integration. Most NZ businesses already have at least three of these. You just haven't wired them up.

A tight call script. Two-page max.

It includes the open, the qualifying questions, the three branches the conversation could take, and the disposition codes the agent uses to log outcomes. The voice agent does the rest.

An honest call window. NZ Privacy Act 2020 plus the Fair Trading Act calling-hours rules lock you to weekday 9am-8pm for marketing-shaped contact.

No calls Sunday. Account servicing has different rules. Get this right or your phone reputation gets nuked in a fortnight.

That's it. That's the whole stack.

Your shipping checklist

Me: "Show me the trigger source."

You: "Uhhh, Xero. I think."

Me: "Cool, write it down. Now show me where you get woken up about it."

That's how every one of these conversations goes the first time. Five questions to answer before you ship:

Then two more:

If you can answer all five, you're 7 to 11 days from live.

If you can't answer two of them, you're not ready yet. Fix the wish first, then bring the agent in.

(We've shipped variations of this for trades, healthcare, mortgage, real estate, and rent-arrears chase. We wrote up the property version in the rent arrears post. The pattern repeats. The trigger sources change.)

Pick the awkward call your team's been avoiding

Five awkward calls a week. Times 50 weeks. That's 250 conversations your team's been silently dodging this year.

Each one carries a cost you've stopped tracking because the dodge is so habitual.

Pick the one that's costing you the most. Wire one trigger.

Run 60 calls against a controlled list before you scale. Playbook 5 will cover why.

Then watch your office manager wake up Wednesday with three promise-to-pays already logged before her coffee.

Far out, that's a long article. Pick one trigger. Ship one experiment.