Spark is executing one of the toughest resets in Australasian telecom — revenue declining, dividends rebased, and an expanded cost program targeting more than a hundred million dollars of annualized savings — while its contact centers still resolve routine mobile and broadband service with New Zealand labor; an agentic frontline that automates the routine majority and covers every renewal window with retention discipline is the largest service-economics lever still unclaimed by the program, deliverable within the fiscal year the market is watching.
Spark is New Zealand's largest telecommunications provider across mobile, broadband and digital services, with FY25 revenue and earnings declining amid a weak NZ economy.
Public factSpark's expanded SPK-26 operating program targets significant net labour and opex reductions, building to well over NZ$100 million of annualized benefits, with an operating-model overhaul and IT partnership underway.
Public factThe dividend was rebased and capital discipline tightened, keeping cost delivery under intense market scrutiny quarter by quarter.
Public factA shrinking enterprise segment concentrates pressure on consumer economics, where cost per contact and churn decide margins.
Reasoned inferenceNZ labor costs and a tight service-labor market make contact-center economics structurally difficult at Spark's scale.
Reasoned inferenceOffshore outsourcing of service work is politically sensitive in New Zealand, making onshore AI capacity an attractive middle path.
Reasoned inferenceValidate with the account team before outreach: SPK-26 program scope and whether frontline automation is already claimed within it · The IT-partnership perimeter and its automation mandate · Current chatbot containment and CCaaS vendor commitments · Renewal coverage rates and churn by product line
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: Spark's reset explicitly moves work to partners — the operating-model overhaul and IT-services partnership signal a company buying outcomes, not building platforms; conversational AI at production grade is a governed buy that fits the declared direction of travel.
Why they won't build the full stack: A company cutting labor and opex against a public target cannot fund speculative AI builds; a bought platform with human gates delivers bookable run-rate savings inside the program window the market is grading.
Spark's FY25 results showed adjusted revenue down around 4% and EBITDAI down around 9%, with the expanded SPK-26 program targeting NZ$80-100 million of net labour and opex reduction in FY25 and well over NZ$100 million annualized by FY27.
GTM implication: Sell directly into the named program: frontline automation as a bookable contributor to the public savings target, deliverable within the window investors are grading.
Dividend rebasing and capital discipline keep every opex line under quarter-by-quarter scrutiny.
GTM implication: Position pilot economics as fast, measurable and reversible — the procurement profile a stressed balance sheet requires.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Consumer service and billing line Routine service resolved in-conversation; cost per contact cut measurably within the program window. | Routine mobile and broadband service is the dominant volume class carrying full NZ labor cost through a declared cost emergency. Friction today: IVR deflection frustrates; routine requests queue; every human contact fights the cost program. | VoiceApp chat | |||
Renewal retention and win-back Full renewal-window coverage with policy-bounded offers; saves attributed weekly. | In a shrinking-revenue market, defending the subscriber base is cheaper than any growth initiative available. Friction today: Save capacity covers a fraction of expiring plans; churn decisions happen without conversations. | VoiceSMSApp chat | |||
Broadband fault triage Diagnostics-grounded triage resolves routine faults; visits booked only when warranted. | Fault calls are long, expensive and churn-inducing when unresolved. Friction today: Script-based triage and truck rolls for restart-grade faults burn cost the program needs back. | VoiceApp chat |
Voice & channel orchestration, telephony, conversational execution, session/state, routing, integration build. Capability coverage validated during implementation.
API access to these systems is the critical-path dependency.
Identity-bound sessions, policy-bounded actions, 100% audit logging, human approvals at defined points, in-tenant intelligence.
All figures are modelling estimates from the labeled inputs above — nothing here is customer-provided yet. The pilot's first job is replacing these assumptions with Spark New Zealand's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Spark New Zealand: Consumer service plus retention plus broadband triage are the classic telecom Scale bundle, and the cost-program clock argues for multi-workflow impact in one deployment rather than serial pilots.
Packages cover implementation and integration only. Recurring costs are billed separately: Tilicho Labs platform usage (~$0.15/call-min indicative, usage only), Google Cloud consumption, telephony/carrier charges, managed operations, and support & optimization. No package includes unlimited usage.
“The market is grading Spark on cost delivery each half; frontline automation is the largest single opex line the program hasn't yet claimed — and one that improves service while it saves.”
“You're already re-platforming IT through partnership; a governed agent layer over BSS APIs fits that architecture and delivers benefit inside the program window, not after it.”
“Every FTE of routine service is arithmetic against the program target; elastic automation covers demand while your operating-model reset proceeds without service-quality risk.”
“Defending the base costs less than any acquisition; full-coverage renewal conversations with offer discipline is the churn lever your current save capacity can't reach.”
“NZ Privacy Act-aligned processing, approved-offer enforcement, vulnerable-customer routing and 100% logging — control that improves as automation grows.”
“The program's credibility rests on visible run-rate savings; measured cost-per-contact reduction on the consumer line is bookable inside a fiscal half with usage-based run cost.”
Written from this account's own research — the strategic signal, the capability gap, the entry workflow, and the modelled economics — not a mail-merge template. Pick the moment and the persona, edit anything, then copy or open in your mail client.
Customer-safe by construction: drafts are composed only from customer-facing fields. Account tier, build-vs-buy classification, priority score, internal routing, and partner-commercial detail are not inputs to the composer, so they cannot appear in a draft. Money figures are always framed as modelled from the customer's own volumes. Read before sending — you own what goes out.
New Zealand's largest telco in the middle of a hard reset — declining revenue, a deep cost-out program and an operating-model overhaul — where service automation is not an innovation story but survival arithmetic for the margin line.
Propose a program-aligned Scale deployment: baseline consumer-line economics with the transformation office, targeting bookable run-rate savings within two quarters.
Entry: Consumer service and billing line · Scale package · 10–14 weeks to production across priority workflows. Human fallback throughout; success thresholds agreed before build.
Start the pursuitResearch-based priority-account universe assembled from public information, market scale, communication volume, and solution fit. This is NOT an authoritative list of top Google Cloud customers; existing Google Cloud relationships are noted only where publicly reported. Validate every account with the account team before outreach.