Meralco's contact volume is a function of billing cycles and weather; agentic conversations answer bill questions with account-grounded math and turn outage chaos into proactive, area-specific updates.
Meralco is the Philippines' largest electric distribution utility, serving Metro Manila and surrounding provinces with on the order of eight million customer accounts.
Public factTyphoons and grid events produce outage-driven contact surges every storm season across its franchise area.
Public factRate adjustments regularly make bills a public topic; billing-inquiry spikes follow generation-charge changes.
Public factOutage callers mostly want the same two answers — is my area affected, and when is restoration — which agents cannot personally know either.
Reasoned inferencePayment-arrangement and reconnection conversations carry hardship sensitivity requiring careful, policy-bounded handling under ERC consumer rules.
Reasoned inferenceValidate with the account team before outreach: Outage-management system integration readiness and area-mapping granularity · Regulated-procurement path and pilot approval timeline · Current storm-event contact volumes and hotline capacity
Limited internal ability or appetite to build the core platform — strong candidate for the packaged solution
Evidence: A regulated utility procures technology through formal vendor processes and has no internal AI platform organization; it will buy a proven, contained solution with regulatory-grade logging and contractual accountability.
Why they won't build the full stack: Utility engineering centers on grid, metering, and outage systems; conversational AI is a procurement category, and ERC-facing accountability favors contractual vendor commitments over internal experiments.
Rate-adjustment cycles reliably spike billing inquiries and complaint volumes across the franchise area.
GTM implication: Time the pilot to land before the next rate adjustment or typhoon peak, when the before/after contact-volume contrast is starkest.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Outage reporting & restoration updates In-channel outage confirmation and proactive area-specific restoration updates that suppress repeat calls. | Storm surges multiply inbound exactly when field crews and lines are most strained. Friction today: Customers call repeatedly for restoration estimates; hotlines saturate; social media fills the vacuum. | Viber/WhatsAppSMSVoice | |||
Bill explanation & payment arrangements Account-grounded bill explanations and policy-bounded installment arrangements completed in-conversation. | Rate-change months spike inquiries; hardship handling is regulatorily sensitive. Friction today: Bill questions need account-level math agents assemble manually; arrangements require branch visits. | VoiceViber/WhatsApp | |||
Service applications & move-ins Guided application intake with document checklists and proactive status through energization. | Metro Manila's housing churn generates constant connection, disconnection, and transfer requests. Friction today: Document-heavy applications stall; status calls follow. | Viber/WhatsAppWeb |
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 Meralco's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for Meralco: A regulated utility will pilot narrowly first; outage communications is the highest-pain, fastest-proof single workflow to start with.
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.
“Public trust in Meralco is rebuilt or spent during every storm and every rate change. Proactive, honest, account-grounded communication at scale is trust infrastructure.”
“A Launch pilot needs only outage-management and notification integrations — a contained project with highly visible public benefit.”
“Storm-night hotline saturation is an annual certainty; proactive area updates convert thousands of inbound calls into zero-touch notifications.”
“Bill-explanation quality decides complaint volumes in rate-adjustment months; account-grounded conversational math answers what scripts cannot.”
“ERC consumer-protection obligations are met with consistent, logged communications and policy-bounded arrangements — evidence on every interaction, not a sample.”
“A fixed-price Launch pilot with consumption usage fits regulated procurement, and the storm-season before/after contact data makes the ROI case itself.”
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.
The distribution utility for Metro Manila and surrounds — around eight million customer accounts with intense billing and outage contact patterns, but regulated-utility procurement makes the motion deliberate.
Pilot framing with customer-retail leadership: proactive outage-update automation for one distribution area ahead of peak typhoon season.
Entry: Outage reporting & restoration updates · Launch package · 8–10 weeks to a live, measured pilot. 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.