When Mitsui Sumitomo and Aioi Nissay Dowa become one company in 2027, two contact-center estates, two claims-communication models and two sets of scripts must become one; an agentic layer deployed above both claims systems delivers a unified, script-governed customer conversation now — banking service-consolidation synergies years before core-system integration completes, with the conduct-governance upgrade the sector's recent FSA orders demand.
MS&AD reached final agreement to merge Mitsui Sumitomo Insurance and Aioi Nissay Dowa Insurance effective April 2027, creating Japan's largest non-life insurer as Mitsui Sumitomo Aioi Insurance.
Public factThe FSA issued business-improvement orders to both core units over personal-data handling and fair-competition issues, putting communications conduct under regulatory watch during the merger.
Public factMerger execution requires harmonizing two agency networks, two claims operations and two contact-center estates while serving customers without interruption.
Reasoned inferenceTyphoon and cat surges hit both books simultaneously; a shared elastic intake layer is worth more than either company's alone.
Reasoned inferenceDuplicate status-call and document-chase load across two claims models makes pre-merger communication automation one of the few synergies bankable before systems integrate.
Reasoned inferenceAgency channels of both companies will generate heavy transition inquiries (branding, product mapping, procedures) through 2027 — a predictable contact wave no one is staffed for.
Seller hypothesis — validateValidate with the account team before outreach: Integration-office structure and who owns service/claims consolidation · Contact-center estates and vendor contracts of both companies · Improvement-order remediation requirements touching communications · Claims-system integration constraints for a two-stack routing layer
Technically capable but needs industry workflows, integration, acceleration, or managed operations
Evidence: Both units have digital programs and the group has data capability, but merger-integration bandwidth is the binding constraint — internal teams will be consumed by systems consolidation through 2027; a partner-delivered platform above both stacks is the only realistic way to unify the frontline early.
Why they won't build the full stack: No integration office builds new conversational infrastructure mid-merger; every internal engineering hour is committed to systems consolidation, while a partner-led layer delivers the unified customer experience and banks synergy before day one.
MS&AD announced and finalized the merger of Mitsui Sumitomo Insurance and Aioi Nissay Dowa into Mitsui Sumitomo Aioi Insurance, effective April 2027, creating Japan's largest non-life insurer.
GTM implication: Sell into the integration program: a shared frontline is early, measurable merger synergy with no core-system dependency.
The FSA issued business-improvement orders to both merging units over data-handling and fair-competition issues.
GTM implication: Conversation governance across both entities is remediation evidence during the most scrutinized period in the group's history — lead with it.
| Workflow | Why it matters here | Value | Complexity | Speed | Channels |
|---|---|---|---|---|---|
Unified auto claims FNOL and proactive status desk One conversational front door with per-company system routing behind it; status calls fall and conduct consistency is evidenced across both books. | Claims communication is duplicated across both companies today and must be one experience by 2027 — starting above the systems, not after their merger. Friction today: Two intake models, two script sets, two status-call queues; customers of the future merged company get different experiences by legacy brand. | VoiceApp chatWebLINE | |||
Catastrophe-surge communication protocol (shared) Pooled elastic intake with triage; first response in minutes across both brands. | Cat events hit both books at once; a shared elastic layer converts two surge problems into one absorbed curve. Friction today: Both companies surge-staff separately for the same typhoon; neither has enough. | VoiceSMSLINEWeb | |||
Merger-transition inquiry desk for customers and agencies Transition questions answered from a governed, single source of truth; human teams reserved for complex portfolio cases. | The 2027 merger will generate a predictable wave of product-mapping, branding and procedure questions from customers and tens of thousands of agencies. Friction today: Transition FAQs land on service lines staffed for steady state; agencies queue behind consumers. | VoiceWebApp 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 MS&AD Insurance Group's measured baseline. Package price covers implementation only; recurring usage billed separately.
Why this package for MS&AD Insurance Group: Spanning two companies' claims and service estates through a merger is inherently multi-BU, multi-integration work — Transform scope with a phased path that tracks the integration timeline.
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 merger's promise is scale economics; a shared conversational frontline is the rare synergy bankable before day one — and visible proof to the market that integration is producing value early.”
“Core-system integration will take years; an agent layer above both claims stacks delivers one customer experience now, decoupling service consolidation from the hardest systems work.”
“Two contact estates, two surge-staffing plans, one typhoon; pooling elastic capacity across both books is the first operational synergy this merger can actually cash.”
“You must harmonize scripts, conduct standards and service levels across two companies under regulatory watch; a platform that enforces one approved script set and logs 100% is your integration tool, not just a channel.”
“With business-improvement orders live during the merger, evidence-grade conversation governance across both entities — script enforcement, complete logs, human payout gates — is the control environment the FSA expects to see.”
“Merger synergies are promised to the market on a timeline; communication-layer consolidation books measurable cost-per-contact synergy in year one, priced per conversation with no core-system dependency.”
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.
MS&AD is executing Japan's biggest insurance merger — Mitsui Sumitomo and Aioi Nissay Dowa combine into one company in April 2027 — which forces consolidation of two claims and service estates; a shared agentic frontline is the merger synergy that can be banked before the systems merge.
Engage the merger integration office: position the shared conversational layer as an early-synergy workstream, starting with a two-brand FNOL pilot in one region.
Entry: Unified auto claims FNOL and proactive status desk · Transform package · 14–20 weeks phased across units. 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.