Service
Loyalty Management
Earn, burn, tiers, and partner rewards written so a finance owner can explain them — and so campaign and billing tell the same story.
A loyalty point is a promise. It is also a liability. Innova Core Technologies implements loyalty management on operator programmes where those two facts have to live in the same system. From Riyadh we design earn, burn, tiers, and partner rules that customer experience can run and that finance can read without a translation layer of slides.
Loyalty sits beside campaign management, Sugar CRM, and revenue and billing. If campaign can grant points that billing cannot reverse, the programme will stall. If CRM cannot see the tier, care will guess. If MongoDB holds a rich profile with a different party id, the customer will earn twice or not at all. We treat those threads as one CX programme, not as four vendors.
Earn, burn, and the rule written once
The earn rule must be one sentence. The loyalty engine, the campaign offer, and the RBM product have to use that sentence. When marketing writes a second version in a deck, operations inherit two currencies. We workshop the rule with marketing, BSS, and finance in the room until it is boring. Boring is the goal. Creative sits on top of a rule that reconciles.
Burn is where customers notice breakage. A high-value redemption, a partial reversal, and a customer who must not earn because they are suppressed or in collections — those cases belong in the design, not in a hypercare ticket. Tiers are commercial policy. They must be visible to CRM and campaign, and they must not be recalculated in three places with three rounding stories.
Partner earn is still your liability. Retail and lifestyle partners are useful. They also create events you do not fully control. The integration needs a dispute path, timeouts, and a record of what you accepted. A happy API with no exception process is how points leak and how a steering committee loses trust.
Delivery on the stack you already have
We do not invent a parallel currency nobody can support. Discovery maps the partner and product constraints already in the estate, including the focused technology partners that sit under Data, Integration, CX, and Automation programmes. Configuration and integration stay inside that picture. Data security is part of the same scope: who may adjust a balance, who may export a member file, what the audit trail shows when a partner file is loaded.
Identifiers stay dull. The member, the account, and the MSISDN should match CRM and billing. Campaign segments that earn must be built from those keys, not from a marketing spreadsheet that drifted last quarter. Testing proves a grant, a burn, a reversal, and a suppressed customer. Defects are written so a vendor or an internal squad can act. Software upgrades of the loyalty platform are planned with freeze windows shared with campaign and RBM.
What “finance can read†means
It means a Tuesday report that explains opening balance, earn, burn, expiry, and adjustments without a war room. It means a campaign grant that RBM can price or reverse. It means a partner earn that can be disputed. It means care can see the same tier the customer sees in digital. That is repeatable delivery. It is also why we write operating practice: who owns a rule change, how a correction is approved, which log is truth.
Work already done with operators and integrators such as Systems Arabia, STC, Zain KSA, Mobily, Airtel, Maalim Al Khabra, and Smart Solutions taught the same lesson. Loyalty that only marketing loves will be rewritten by finance. Loyalty that only finance loves will not be used. The programme has to be both. If that is the work in front of you, request a callback. A coordinator in Riyadh will return it.