Fintech Ecosystem Orchestration: Unifying Fragmented Support Channels into a Governed Intercom Stack
A scaling Mexican digital SOFIPO struggled with a fragmented "Frankenstack" that erased customer context between voice and digital support.
We consolidated Zendesk and Infobip into a unified Intercom environment via Apache NiFi. Integrating Vozy voice-bots and Incode KYC ensured clean context handoffs, accelerating loan disbursements.
Executive Summary
Context
A mid-sized Mexican digital SOFIPO was burdened by a fragmented support stack (Zendesk, Infobip, SendGrid) that prevented real-time context sharing and inflated operational costs during a period of rapid customer growth.
What We Built
We engineered a unified fintech support ecosystem centered on Intercom, integrating third-party voice (Vozy), identity (Incode), and messaging gateways (Airmovil) into a single governed workspace.
Tech Stack
- Intercom (Chat/Bots/Ticketing), Vozy (Voice Bots), Incode (KYC Video), Apache NiFi (Middleware).
Not a fit for organizations that rely purely on voice-only support or those without the technical capacity to manage API integrations between specialized fintech microservices.
The Challenge
"Context fragmentation" defined the failure mode. A customer might start an interaction with a Vozy voice bot to inquire about a loan, but upon switching to digital chat or video verification via Incode, all previous context was lost. This forced customers to restart their authentication and inquiry process multiple times, leading to high drop-off rates in the lending funnel.
Simultaneously, the bank was paying for redundant seat licenses across Zendesk and Infobip, with no single source of truth for customer interaction history. The technical team faced the additional constraint of needing to maintain Mexican GDPR compliance while syncing sensitive financial data from a legacy core into this multi-vendor support stack.
Our Approach
Apache NiFi bridged the legacy core and the new Intercom-centric ecosystem, a strategy we called "Stack Consolidation via Middleware." Every tool in the stack referenced the same customer ID and compliance status. We had to choose between a complex, long-term sync for Zendesk and a hard cutover. We picked the hard cutover: decommissioning Zendesk and moving straight to Intercom’s unified helpdesk forced a single workflow for all agents.
To solve the voice-to-chat gap, we engineered a custom handoff protocol between Vozy and Intercom. The voice bot’s intent data gets pushed into Intercom as a "pre-filled" conversation before the user even types their first message. We also embedded Incode’s video verification directly into the Intercom messenger interface.
Impact
30% Reduction in Agent Redirection
Unified Customer Context
Voice, chat, and video interactions consolidated into Intercom, so customers no longer had to repeat information during channel switches. This "Zero-Friction Handoff" directly improved the completion rate for complex loan applications.
Decommissioning of Legacy Tech Debt
Replacing Zendesk and Infobip removed redundant licensing costs. Consolidating the stack into a unified environment reduced the technical management burden on the bank’s internal DevOps team.
Secure KYC Video Integration
We built an API bridge that captures intent and entity data from Vozy voice interactions. When a user is escalated to digital chat, this data is pushed into Intercom as custom attributes, so the agent or bot immediately knows the previous voice-based context.
Apache NiFi serves as the "Fintech Router," pulling real-time customer data from the legacy banking core and distributing it to Intercom and Vozy. That means a "Do Not Contact" flag or a balance change reflects across all communication channels within seconds.
An omnichannel orchestration architecture utilizing Apache NiFi as a compliance engine to connect a legacy core banking system with Intercom. It integrates Incode KYC for video verification and Vozy Voice Bots for intent-driven handoffs. This centralized model remedies context fragmentation, reducing agent redirection while enforcing PII tokenization and rate limiting.
FAQ