Use Case Scenario
This scenario continues the AUS Bank story told in CRM Use Case Scenario, Campaign Use Case Scenario and Telephony Use Case Scenario. Nothing in those scenarios changes here.
Background
AUS Bank's collections team now calls overdue customers first and answers the ones who call back. A gap remains. Before a call, an agent has to know whether the customer's identity check is complete, and that information lives in PolicyHub KYC, a separate system run by the bank's compliance team. Agents open it in another window, search for the customer and copy the result into a note.
"My agents lose a minute on every call switching windows, and some skip the check altogether. I want the PolicyHub record to simply be there, next to the customer, in the CRM."
Daniel, Collections Manager
Two more requests followed. The analysts wanted collections figures in their BI tool without exports. The compliance team wanted PolicyHub to tell the CRM when a policy is about to renew.
What the Team Asked For
- PolicyHub data inside the CRM. Agents should see a customer's PolicyHub record as a normal CRM module, without a second login.
- No custom development. The bank wanted to connect PolicyHub without writing a backend service.
- A safe connection. The credential for PolicyHub should be kept in one place, and a token that expires should be renewed automatically.
- Data for the analysts. The BI tool should read CRM data directly, with its own limited credential.
- Events pushed in. PolicyHub should notify the CRM of renewals as they happen.
- Clear limits. Only a few administrators should manage connections.
How the Team Met Those Requirements
The connection to PolicyHub
A collection named PolicyHub KYC holds PolicyHub's base address, its default headers and a Bearer Token. Two APIs sit inside it, List Customers for the customer list and Get Customer for one record, built on the collection's base address.
The reshaping
PolicyHub replies in its own format. A Post Script on each API turns the reply into the data and pagination format the CRM requires. A collection script fetches a new token when the old one expires.
- Agent: Opens the Policy Customers module
- CRM: Calls List Customers or Get Customer
- PolicyHub: Replies, and a Post Script reshapes the reply
- Result: The customer record appears in the CRM
The module
An external CRM module named Policy Customers reads its list from List Customers and its single record from Get Customer. The customer reference is its primary key. The module is for looking up records, so the optional create, update and delete APIs were left empty.
The analysts and the renewals
The analysts received a service account with a limited role and connected their BI tool through its database connection. A webhook named Policy Renewal Notice gave PolicyHub an address to post renewal notices to.
The access limits
The API and Webhook permissions were switched on only for two administrators. Agents received only the permissions to view the Policy Customers module.
The PolicyHub token is stored on the collection. Anyone who can open the collection can see where it is configured, which is why access to Integrations is limited.
Outcomes
| Area | Before | After |
|---|---|---|
| Checking a customer's PolicyHub status | Second window, copied by hand | A module in the CRM |
| Building the connection | A custom backend | A collection and two APIs |
| Expired tokens | Pasted again by an administrator | Renewed by a script |
| Data for the analysts | Exported files | A direct connection |
For AUS Bank, the CRM, Campaign and Telephony gave the collections team the customer, the call and the outcome. Integrations added the last piece: the identity check from another system, available in the same place.
Where Each Part Is Documented
| Guide | Covers |
|---|---|
| Configuring the Integrations Use Case | How it was built |
| Collections | The connection to PolicyHub |
| Creating an API | List Customers and Get Customer |
| Response Format the CRM Requires | The reshaping |
| Creating an External Module | The Policy Customers module |
| Connecting BI and Database Tools | Data for the analysts |
| Webhooks | Renewal notices |
| Integrations Permissions | Who manages connections |