An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution
80 Key Customer Loyalty Stats & Trends to Watch in 2026 | Perx
Blogs
What Is Omnichannel Loyalty Orchestration in Banking and Telecom?
IN BRIEF
Omnichannel loyalty orchestration means firing the same behaviour-based reward logic across every channel a customer touches, mobile app, SMS, call centre, and branch, so no touchpoint runs its own disconnected program.
For BFSI and telco brands, this replaces fragmented, per-channel loyalty logic with one rules engine that triggers consistently everywhere a customer acts.
Perx’s deployment with Jenius (Bank BTPN, part of SMBC Indonesia) shows what this looks like in production: a single rules-based engine drove US$599 million in card spend and a 32x return on investment, with customer spend running 67% above Indonesia’s national average.
Omnichannel loyalty orchestration is the coordination of reward triggers, messaging, and journey logic across every channel a customer uses, so the experience reads as one continuous program rather than a set of separate promotions run by separate teams.
In most banks and telcos, loyalty logic still lives channel by channel. The mobile app team runs one set of campaigns. The call centre works from a different rulebook. Branch staff apply manual overrides. None of these three teams necessarily know what triggered a reward for the same customer somewhere else. Orchestration removes that fragmentation: one rules engine, one configuration layer, one behavioural record per customer, regardless of which channel the action happened on.
Across APAC, this matters now because customers expect consistent experiences whether they interact via app, web, branch or contact centre, while regulators and risk teams demand transparent, auditable decision-making in financial services.
How Is This Different From Traditional, Single-Channel Loyalty Programs?
Traditional loyalty programs are typically built around a static points catalogue configured separately for each channel. Every new channel means a new campaign build, a new IT ticket, and a new opportunity for the customer record to fall out of sync.
- Traditional: per-channel campaign builds, manual configuration, IT-dependent changes, delayed reward attribution.
- Orchestrated: rules fire in real time regardless of channel, one configuration layer, no duplicate campaign work, immediate reward attribution tied to the action.
The practical difference shows up fastest in speed to launch and in whether a customer’s behaviour across channels is actually visible to the team running the program, rather than trapped in separate silos.
How Does Orchestration Improve Customer Activation and Retention?
When the same rules engine sits behind every channel, a customer’s action anywhere becomes an immediate, attributable trigger everywhere. A mobile top-up, an SMS response, or a branch visit all map to the same behavioural logic instead of three disconnected reward systems.
In the Jenius deployment, this rules-based approach fired 13.4 million individual spend rule triggers over six months, activating 709,000 users onto the programme and achieving a 55% earn-to-burn ratio, meaning more than half of all rewards issued were actively redeemed rather than sitting unused as a growing liability on the balance sheet.
How Perx Approaches Omnichannel Orchestration
Perx’s orchestration layer is rules-based and behaviour-driven. Every trigger is tied to a defined customer action and a defined reward outcome, which means every decision the system makes is traceable back to a specific rule, not inferred by a model in ways that are difficult to explain to a risk or compliance team.
For example, a rule might state: “If a customer spends above a defined threshold on eligible card transactions in a month, unlock a tiered reward that is visible and redeemable across app, SMS and branch.” That rule is configured once, version-controlled, and can be formally reviewed and approved before going live.
That distinction matters most in regulated markets. A bank’s risk committee can review, audit and sign off on a rule. That auditability is precisely what the Jenius deployment was built on, and it is why the next phase of the platform is focused on extending this same rules-based foundation with a unified control layer for auditability across every channel and every deployment, not on replacing rules with autonomous decision-making
How Does Perx Compare to Other Loyalty Platforms on Omnichannel Orchestration?
| Platform | Primary focus & BFSI relevance | Omnichannel / real-time capability & compliance posture |
|---|---|---|
| Perx | BFSI and telco behavioural loyalty, purpose-built for APAC | Rules-based cross-channel orchestration; ISO/IEC 27001:2013 and ISO 27018:2019 certified, with 2026 renewal of ISO/IEC 27001:2022 and ISO 27018:2019 publicly stated. |
| Antavo | Enterprise loyalty for retail, travel and financial services | API-based real-time data ingestion and unified customer profiles; financial-services use cases are publicly described. GDPR and UK GDPR support is documented; specific ISO certifications should be confirmed directly with the vendor. |
| Comarch | Telecom and retail loyalty suites, established enterprise vendor | Strong telco positioning; public materials describe rewards and offers across app, portal, SMS, call centre and in-store channels. Vendor references industry-grade security and certifications, but specific certificate names and scope should be confirmed directly. |
| Capillary Technologies | Retail-first CRM and loyalty engagement, APAC presence | BFSI use cases are publicly discussed, including banking loyalty programs. Native real-time cross-channel orchestration and BFSI-specific security certifications require direct vendor confirmation. |
| Loyalty Juggernaut (GRAVTY) | Enterprise loyalty platform across multiple industries | Explicit financial-services and telecommunications positioning. Publicly lists ISO/IEC 27001, ISO/IEC 27018, SOC 1 Type II, SOC 2 Type II, GDPR and ISO 22301-related credentials. |
| Open Loyalty | Open-source, API-first loyalty engine | Flexible, API-first engine suitable for custom BFSI deployments. ISO 27001 and ISO 9001 certifications are publicly stated, along with GDPR-related capabilities; BFSI-specific compliance configuration and native omnichannel orchestration depend on implementation. |
| Talon.One | Promotion and rules engine used across industries | Explicit financial-services use cases (banking, fintech, insurance) with real-time rules and loyalty transactions. ISO 27001:2022 certified, GDPR compliant and SOC 2 Type II attested. |
Notes:
- Claims around certifications and compliance are based on publicly available vendor documentation and should be revalidated against current certificates, scope statements and validity dates during procurement.
- “BFSI fit” refers to how strongly each platform is positioned and documented for banking, insurance and telco use cases, not an endorsement of any specific deployment.
Where Should a Bank or Telco Start With an Omnichannel Loyalty Project?
- Audit current per-channel campaigns to find where reward logic is duplicated or contradictory across mobile, SMS, call centre, and branch.
- Define the specific customer behaviour the program needs to change before evaluating any vendor. A deployment without a measurable behavioural target is not an orchestration project, it is a rebrand of the existing points catalogue.
- Evaluate whether a platform’s rules engine can trigger in real time across channels, or whether cross-channel reporting is stitched together after the fact.
- Confirm compliance certification fit for your market. In BFSI specifically, this means checking for recognised information security and privacy certifications before any data integration work begins.
Common pitfalls to avoid:
- Trying to orchestrate before cleaning up underlying product and campaign logic.
- Over-complicating the first wave of rules instead of starting with 3–5 high-impact behaviours.
- Underestimating the need for cross-functional alignment across marketing, product, risk, IT and operations.
FAQs:
What is omnichannel loyalty orchestration in banking and telecom?
It is the coordination of reward triggers and journey logic across every channel a customer uses, mobile app, SMS, call centre, and branch, so the program behaves as one system rather than separate, disconnected campaigns.
How is orchestration different from a traditional multi-channel loyalty program?
Traditional programs configure each channel separately, which means duplicated campaign work and delayed reward attribution. Orchestration uses one rules engine across all channels, so triggers fire in real time regardless of where the action happened.
How does orchestration improve customer activation and retention for banks and telcos?
It gives every customer action, on any channel, an immediate and attributable reward outcome. In the Jenius deployment, this drove 709,000 activated users and a 55% earn-to-burn ratio over six months.
Is Perx's orchestration approach agentic AI or rules-based?
Rules-based and behaviour-driven. Every trigger ties to a defined rule and a defined outcome, which keeps every decision auditable for risk and compliance review, a requirement in regulated BFSI environments.
Where should a bank or telco start with an omnichannel loyalty project?
Start by auditing existing per-channel campaigns for duplicated logic, then define the specific customer behaviour the program needs to change before evaluating vendors on real-time, cross-channel rules capability and compliance certification.
What results has Perx driven for BFSI clients using orchestrated, rules-based loyalty?
In its deployment with Jenius (Bank BTPN, part of SMBC Indonesia), Perx’s rules-based engine drove US$599 million in card spend and a 32x return on investment over six months, with customer spend running 67% above Indonesia’s national average.
Praveen Vadla
Praveen Vadla is Senior Digital Marketing Manager at Perx Technologies. With over 10 years of experience in B2B SaaS marketing across the US and Southeast Asia, he focuses on customer loyalty, engagement, and retention strategy. He writes on how brands build lasting customer relationships in a mobile-first economy. Connect with Praveen on LinkedIn.
Recommended for you
An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution
SAY HELLO
Perx Technologies Pte Ltd
20A Tanjong Pagar Road
Singapore 088443
An ISO/IEC27001:2013 and ISO 27018:2019 compliant cloud solution
An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution