Customer Experience
Loyalty that finance can read on a Tuesday
A loyalty point is a promise. If campaign can grant it and billing cannot reverse it, finance will find you. Customer-experience programmes in the Kingdom stall less on creative than on this reconciliation. Marketing wants movement. Finance wants a trail. Care wants a tier they can say out loud. If those three groups do not share a sentence, you do not have a loyalty programme. You have a monthly argument with a brand name.
Innova Core Technologies implements loyalty next to campaign management, Sugar CRM, and revenue and billing, from Riyadh. We do not treat points as a marketing toy. They are a liability and a CX tool at the same time. The work is to write earn, burn, expiry, and partner rules so both facts remain true after the project team has gone.
Write the earn rule once
The rule that sits in the loyalty engine, the campaign offer, and the RBM product must be the same sentence. When marketing writes a second version in a slide, operations inherit two currencies. Workshop it until it is boring. Boring is how a Tuesday report works: opening balance, earn, burn, expiry, adjustments. Creative belongs on top of a rule that reconciles, not in place of one.
Identifiers have to be dull. The member, the account, and the MSISDN should match CRM and billing even if MongoDB holds a richer profile. Campaign segments that earn must be built from those keys. A spreadsheet that drifted last quarter will earn the wrong people and miss the ones you meant to keep. Suppression is part of the rule: a customer in collections, or a customer who opted out, must not earn because someone cloned a segment.
Partner earn is still your liability
Retail and lifestyle partners are useful. They also create earn events you do not fully control. The integration needs a dispute path, timeouts, and a record of what you accepted — not only a happy API. Points that arrived twice, arrived late, or arrived for a customer you do not recognise are not “partner issues” you can park. They are your balance sheet until you can show the exception.
Access follows the same logic as the rest of data security. Who may load a partner file, who may adjust a balance, what the audit log shows. A loyalty admin role that can rewrite history without a trail is a finance defect waiting for a date.
Test a burn that hurts
Prove a high-value burn, a partial reversal, and a suppressed customer who must not earn. If those three pass, a steering committee has something better than a demo of a points balance. Add the campaign grant that RBM must reverse, and the CRM view of the tier after the burn. Testing that only shows a green earn on a test MSISDN has not proved the programme.
Software upgrades of the loyalty platform belong on the same freeze calendar as campaign and billing. A version move that changes rounding or expiry while marketing is mid-campaign is how you buy hypercare you did not budget. Rollback is a test case. Operating notes are the handover: who owns a rule change, how a correction is approved, which log is truth.
What “readable on a Tuesday” looks like
It looks like finance not needing a war room to explain the week. It looks like care quoting the same tier as the app. It looks like campaign unable to grant what billing cannot see. That is certified, repeatable CX, not a launch event. It is the standard we take into work with operators and integrators we have already sat with, including Systems Arabia, STC, Zain KSA, Mobily, Airtel, Maalim Al Khabra, and Smart Solutions.
If loyalty is live and the sentences have already split — or you are about to stand a programme up — request a callback. Write to Info@innovacore-tech.com, or start with the Loyalty Management and Campaign Management services. The point is the same: one customer, one rule, one trail.