JapanEnergy utilityScale · $100K
TEPCO

Cost discipline as obligation — agentic billing, moving and outage service for TEPCO's tens of millions of accounts

No Japanese company has a deeper structural obligation to cut operating cost than TEPCO, which funds Fukushima decommissioning and compensation from earnings; an agentic frontline that absorbs the March-April moving-season spike, resolves billing and contract questions in-conversation, and handles outage communication at storm scale converts a fixed contact-center estate into consumption-priced capacity — automation economics that read directly onto the group's publicly mandated cost commitments.

Entry use case
Moving-season start/stop and billing service desk
Expected outcome
Absorb the spring moving spike and routine billing volume with in-conversation contract changes, cutting cost per contact and seasonal surge staffing.
Recommended next step
Workshop with TEPCO Energy Partner service leadership before the next moving season: baseline the spring spike and billing volumes, then scope a Scale pilot on start/stop and billing.
What we understand

TEPCO's operating reality

TEPCO's post-Fukushima framework obliges it to fund decommissioning and compensation from operations, making sustained cost reduction a quasi-regulatory commitment rather than a preference.

Public fact

Kashiwazaki-Kariwa unit 6 restarted in early 2026 after local consent, expected to improve earnings by on the order of a hundred billion yen annually — raising, not lowering, scrutiny of operational discipline.

Public fact

Retail liberalization exposed TEPCO Energy Partner to churn from new power companies, making service experience a retention variable, not a monopoly afterthought.

Public fact

Japan's March-April moving season concentrates start/stop-of-service requests into a brutal seasonal spike that fixed staffing meets with long queues every year.

Reasoned inference

Smart-meter coverage means most billing and usage questions are answerable from data in real time — the gap is conversational access, not information.

Reasoned inference

Typhoon outage events swamp phone lines with restoration-status calls that a proactive push model would largely suppress.

Seller hypothesis — validate

Validate with the account team before outreach: Moving-season volume curves and current surge-staffing cost · CIS write-access constraints for in-conversation contract changes · Outage-communication stack and storm-day call statistics · Group posture on external platforms given public-scrutiny sensitivities

Build vs buy

Why we have a right to win here

Buy-led target

Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution

Evidence: TEPCO's engineering is power-systems engineering; customer-service technology is vendor-delivered, and the group's financial position forbids speculative internal platform builds — a governed buy with measurable payback is the only fundable shape.

Why they won't build the full stack: A company whose earnings are pre-committed to decommissioning cannot fund multi-year internal AI development; a bought platform delivers moving-season and storm-day capacity at consumption pricing, with savings reportable against public cost commitments this fiscal year.

What management is signalling

TEPCO's post-Fukushima framework publicly commits earnings to decommissioning and compensation funding, keeping cost reduction a standing management obligation.

Reported factannual reports and business-plan disclosures · ongoing

GTM implication: Frame automation savings as contributions to the publicly mandated cost commitments — the internal language every TEPCO approval speaks.

Kashiwazaki-Kariwa unit 6 restarted in early 2026 following local consent, with an earnings improvement on the order of ¥100 billion annually anticipated.

Reported factpublic disclosures and results commentary · Jan-Feb 2026

GTM implication: Restart economics increase scrutiny of everything else — operational modernization pitches land well while the spotlight is on discipline.

What already exists (don't pitch this)
  • Web and app self-service for contracts and billing
  • Smart-meter data coverage across the service area
  • Outage-information web pages and notifications
  • IVR and outsourced contact-center estate
What customers still can't do end-to-end (pitch this)
  • →In-conversation contract start/stop without queues
  • →Proactive two-way outage communication at storm scale
  • →Plan-optimization outreach beyond direct mail
  • →Keigo-quality voice automation for the older, phone-first base
Opportunity map

Where agentic communications pays off first

WorkflowWhy it matters hereValueComplexitySpeedChannels
Moving-season start/stop and billing service desk
Contract start/stop, plan and billing questions executed in-conversation against CIS; the spike absorbs without seasonal hiring.
The hikkoshi spike is the utility's most predictable capacity crisis, and billing questions are the year-round volume floor.
Friction today: March queues stretch as movers arrange start/stop by phone; billing questions require CIS lookups agents swivel through.
VoiceWebApp chatLINE
Outage and restoration communication
Proactive restoration updates by area with two-way status conversations; call volume suppressed and vulnerable-customer checks prioritized.
Storm-day information demand is instantaneous and total; call queues at exactly the moment trust is most exposed.
Friction today: Restoration-status calls flood lines during typhoons; updates lag; vulnerable customers cannot get through.
SMSLINEVoiceWeb
Retention and plan-optimization outreach
Consent-governed conversations optimize plans within the approved matrix before the switch decision; saves attributed.
Liberalized-market churn makes proactive plan conversations a retention lever the incumbent has data advantages to win.
Friction today: Switch-risk customers get direct mail; outbound capacity touches a fraction; plan complexity confuses.
VoiceLINESMS
Watch the change

Moving-season start/stop and billing service desk: today vs the agentic model

Scenario: On March 28th a Yokohama tenant arranges electricity stop at the old flat and start at the new one in a single evening conversation that also flags a better plan for her new all-electric building — no hold queue at the utility's worst week, contract writes straight to CIS, and the seasonal temp-staffing line shrinks next year.
Today
same interaction, two worlds
Agentic layer
Languages served
2–3 staffed
10+ in one deployment
Platform capability
Cost per contact
$13.50 median assisted
$1.84 median self-service
Benchmark
QA coverage
1–2% sampled
100% scored
Platform capability
Sources & assumptions
  • · Languages served: Platform capability: Gemini + Chirp speech
  • · Cost per contact: Gartner customer service cost benchmarks, 2024
  • · QA coverage: Platform capability: every interaction logged and evaluated
  • · Gartner, customer service cost benchmarks (2024): $13.50 median assisted vs $1.84 self-service per contact
  • · McKinsey, digital-first collections research: 20–25% NPL reduction among leaders; up to 40% opex reduction with gen AI
  • · Baymard Institute: ~70% average cart abandonment (meta-analysis)
  • · IAMAI–Kantar via IBEF (2025): 900M+ Indian internet users; 98% consume Indic-language content
  • · LeadSquared and vendor funnel studies: 78% of students choose the first institution to respond (directional, vendor data)
  • · HDI / ITSM operator benchmarks: $15–25 per L1 ticket; 40–60% of L1 volume is resets/status (validate per customer)
  • · Conventional-flow wait times and volumes are typical operator patterns — assumptions to replace with the customer's own baseline
  • · Agentic-flow behaviors (context retention, 100% logging, in-line policy checks) are platform capabilities, not projections
Recommended solution

One integrated stack, opinionated for this account

Channels · Tilicho Labs
VoiceWebApp chatLINESMS

Voice & channel orchestration, telephony, conversational execution, session/state, routing, integration build. Capability coverage validated during implementation.

Intelligence · Google Cloud
Gemini reasoningEnterprise groundingWorkflow agentsMulti-agent orchestrationGoverned actionsEvaluation & analytics
Systems · TEPCO
CIS/billingSmart-meter dataCRMOutage managementGIS/area dataChurn scoringOffer matrix

API access to these systems is the critical-path dependency.

Trust & languages
JapaneseEnglish

Identity-bound sessions, policy-bounded actions, 100% audit logging, human approvals at defined points, in-tenant intelligence.

Business case

The economics, with your numbers

Addressable monthly interactions2.5M
Seller assumption — replace in discovery
Current cost per interaction ($)$4.0
Industry benchmark scale — validate
Automation / assistance rate (%)55%
Seller assumption — pilot proves this
$10.0M
Current operating cost / mo
$60.2M
Modelled gross benefit / yr
0.0 mo
Payback on Scale
1036%
3-yr ROI (modelled)
Automated/assisted interactions per month1.4M
Modelled AI run-cost per month (usage + cloud, system estimate)$481K
New monthly operating cost$5.0M

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 TEPCO's measured baseline. Package price covers implementation only; recurring usage billed separately.

Recommended package

Scale — $100K implementation

Scale · $100K · A multi-channel production deployment10–14 weeks to production across priority workflows

Why this package for TEPCO: Moving/billing service plus outage communication are two bounded, high-volume workflows on CIS and outage systems — Scale scope with retail-competition retention as the expansion path.

Included
  • 4–6 channels
  • 2–3 priority workflows
  • Multiple enterprise integrations
  • API credential & security setup
  • Advanced orchestration
  • Multilingual support
  • Agent Assist / human escalation
  • Production analytics
  • Expansion roadmap
Not included
  • ✕Usage & consumption (billed separately)
  • ✕Enterprise-wide governance build-out
  • ✕Multi-BU rollout
Recurring costs (separate from the package)

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.

Customer resources required
  • · API access + credentials for: CIS/billing, Smart-meter data, CRM
  • · A named business owner for moving-season start/stop and billing service desk
  • · Security review counterpart and policy sign-off (CIS/billing scope)
  • · Baseline metrics for the pilot's success thresholds
Executive messages

What to say to whom

President / CEO

“Cost discipline is TEPCO's public obligation, not a target; frontline automation is discipline you can point to — measured, auditable, and felt by customers as better service rather than austerity.”

CIO / CTO

“A governed agent over CIS, smart-meter and outage systems — bounded integrations, APPI-grade handling, full audit trails — delivers modernization without waiting on core-system programs.”

COO

“You staff for March and carry it all year, then typhoons break the model anyway; elastic conversational capacity absorbs both spike patterns at consumption cost.”

Head of Customer Service (TEPCO Energy Partner)

“Moving-season queues and storm-day floods are your two worst weeks; an agent that executes start/stop in-conversation and pushes restoration status turns both into ordinary days.”

Chief Risk / Compliance Officer

“APPI-aligned handling, human gates on hardship and disconnection matters, 100% logged conversations — governance fit for a company whose every operational choice faces public scrutiny.”

CFO / Procurement

“Every yen of contact-center cost competes with decommissioning obligations; conversation-priced service against your own cost baseline is the cleanest efficiency line you can report.”

Outreach

Pre-built offer emails for TEPCO

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.

Moment in the deal
Cold outreach — no prior conversation
Who it's addressed to
Cares about: The workflow itself and its daily failure modes
Register
Length
Draft — edit freely before sending
Open in 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.

The pursuit

Tier 1 — immediate strategic pursuit

Why this tier

Japan's largest utility carries the Fukushima compensation and decommissioning burden that makes cost discipline existential, serves tens of millions of accounts through liberalized-market churn, and just restarted Kashiwazaki-Kariwa — every operational yen saved is a yen the balance sheet demands.

30 / 60 / 90-day plan
  • Day 0–30: Workshop with TEPCO Energy Partner service leadership before the next moving season: baseline the spring spike and billing volumes, then scope a Scale pilot on start/stop and billing.; confirm sponsor and baseline data access; validate: Moving-season volume curves and current surge-staffing cost
  • Day 31–60: architecture & security review with the platform team; Tilicho Labs scoping on Voice + Web; pilot scope signed
  • Day 61–90: Scale package kickoff; moving-season start/stop and billing service desk pilot in build; success thresholds locked with the Head of Customer Service (TEPCO Energy Partner)
Recommended next step

Workshop with TEPCO Energy Partner service leadership before the next moving season: baseline the spring spike and billing volumes, then scope a Scale pilot on start/stop and billing.

Entry: Moving-season start/stop and billing service desk · Scale package · 10–14 weeks to production across priority workflows. Human fallback throughout; success thresholds agreed before build.

Start the pursuit

Research-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.