Unblocking a real-time decisioning integration
Led the client-side resolution of an integration failure between the campaign platform and a real-time decisioning engine that had stalled campaign development with the vendor.
- Role
- Technical lead (client side)
- Where
- stc Bahrain
Some specifics are anonymised to respect commercially sensitive information.
Context
Real-time decisioning lets campaigns respond to a customer in the moment — during a call, a session, or an event — rather than in a nightly batch. It depends on a working integration between the campaign platform and the decisioning engine.
Problem
The integration was failing, and campaign development with the vendor had stalled because of it. The failure sat across a boundary — partly platform configuration, partly decisioning-engine setup, partly the message contract between them — so neither side owned it end to end.
What I did
I took ownership of the whole path from the client side: reproduced the failure, isolated where the request was breaking, and worked through the platform configuration and the message contract with the vendor until the round trip succeeded. Then I documented the working setup so it would not regress.
Result
The integration went from failing to live, which restarted the campaign development that had been waiting on real-time decisioning. The documented setup gave both sides a known-good baseline to build further campaigns on.
What I learned
Cross-boundary failures need one person to hold the whole path, even the parts they do not own, or each side keeps handing the problem back.