Sales reps at a broadband comparison platform were spending the first 90 seconds of every call doing one thing: looking up the customer's current energy and internet plan in three separate tabs. By the time they'd found the right package to pitch, the customer had lost interest. The handoff rate was high. The close rate wasn't.
The Problem With Disconnected Systems
The CRM held contact history. The energy portal held Kraken data. The NBN Co lookup tool sat in a third browser tab. None of them talked to each other. According to Salesforce's State of Sales report, sales reps spend nearly 64% of their time on non-selling activities — and disconnected tooling is one of the biggest contributors. In a contact centre selling on inbound volume, every wasted minute is a lost conversion.
The Integration Architecture
The solution was a real-time screen-pop: when a call landed in Genesys Cloud, the system triggered a background API call to Kraken using the customer's phone number as the lookup key, then cross-referenced the NBN Co address API to pre-fetch available plans at their premises. By the time the rep accepted the call, a sidebar panel in the CRM showed: current plan, contract end date, eligible upgrade paths, and the best NBN tier available at the customer's address.
- Genesys Cloud EventBridge integration fired on call-accepted webhook
- Lambda function orchestrated parallel Kraken API + NBN address API calls
- CRM sidebar populated via WebSocket push before rep finished the greeting
- Response time: average 340ms end-to-end under normal load
- Fallback: graceful degradation to manual lookup if API returned >1s
What Changed After Go-Live
Average handle time dropped from 9.4 minutes to 5.9 minutes — a 37% reduction — in the first 30 days post-deployment.
The reps stopped tabbing. Escalations dropped because reps were starting from context instead of asking customers to repeat information they'd already given. The team lead reported that the opening 60 seconds of calls felt 'completely different' — reps were more confident and customers felt recognised.
Five Lessons From This Integration
- Design for the rep's workflow first, not the API's data model. Reps needed one answer, not a JSON blob.
- Sub-400ms is the threshold. Slower than that and the data arrives after the greeting — useless.
- Build graceful fallbacks before go-live. APIs fail. Reps should never be stuck waiting for a spinner.
- Log everything for the first 30 days. Usage patterns revealed three fields nobody looked at — simplified the UI.
- Involve the team lead in UAT. They caught three field-labelling issues QA missed because they knew the words reps actually use.
The integration took six weeks from requirements to production, including security review and UAT. The business case paid back within the first billing cycle based on improved conversion alone.