Sales and Service
Contact Routing
sd-contact-routing · bian-sales-service
A BIAN service domain in Sales and Service. It applies the Process functional pattern to the Contact Routing Record, with the Contact Routing Record Procedure as its control record — one independent Spring Boot microservice on the platform's Cilium eBPF mesh.
View repository ↗The 162-domain platform ↗
Business DomainChannels
Functional PatternProcess
Asset TypeContact Routing Record
Control RecordContact Routing Record Procedure
USEWhat it is used for
Representative use cases for the Contact Routing service domain within a BIAN-aligned core-banking landscape.
- Operate the Contact Routing Record touchpoint and expose its sessions/events to the bank
- Route customer contacts and service orders to the right fulfillment domain
- Capture channel telemetry for fraud signals and experience analytics
APIBIAN semantic API
The control record (Contact Routing Record Procedure) is exposed through uniform BIAN action terms. Java 21 · Spring Boot 3, OpenAPI at /swagger-ui.html, health at /actuator/health.
| Method | Path | BIAN action |
|---|
| GET | /v1/service-domain | Service metadata |
| POST | /v1/contact-routing-record-procedure/initiate | Initiate |
| GET | /v1/contact-routing-record-procedure/{crId}/retrieve | Retrieve |
| PUT | /v1/contact-routing-record-procedure/{crId}/update | Update |
| PUT | /v1/contact-routing-record-procedure/{crId}/control | Control (suspend / resume / terminate) |
INTBackend integrations
The systems and standards a real deployment of Contact Routing would transact with.
- Digital banking: Backbase, Temenos Infinity
- ATM/POS: NCR, Diebold Nixdorf, Verifone, Ingenico
- Contact center: Genesys, Twilio Flex, Amazon Connect
RUNRun it yourself
Each service domain is its own standalone Spring Boot repository — clone and run in seconds, or deploy onto Kubernetes with the bundled Helm chart behind the Cilium mesh.
# run this service domain standalone
git clone https://github.com/Sreenivas-Sadhu-Prabhakara/sd-contact-routing
mvn -f sd-contact-routing spring-boot:run
curl localhost:8080/v1/service-domain
# or deploy onto Kubernetes (Cilium eBPF mesh)
helm upgrade --install sd-contact-routing ./helm -n bian-sales-service
FAQQuestions
What is the BIAN “Process” functional pattern?
A Process service domain executes and tracks a defined operational procedure, step by step, to completion. Contact Routing applies it to the Contact Routing Record.
What is a BIAN service domain?
BIAN (the Banking Industry Architecture Network) decomposes a bank into independent service domains, each owning exactly one business capability. Contact Routing is the service domain for Channels; it manages the Contact Routing Record Procedure and exposes it through standard BIAN action terms.
What business area does Contact Routing belong to?
Contact Routing sits in the Sales and Service business area — the customer-facing sales, servicing and channel domains that run the customer lifecycle. It runs in the bian-sales-service namespace as one independent Spring Boot microservice.
Is Contact Routing production-ready?
It is an educational reference implementation: a real BIAN REST API over an in-memory store, ready to be filled with domain logic. It is not a live bank and is not affiliated with BIAN.
SEEIn the landscape
Contact Routing is one of 162 BIAN service domains on the platform. Explore the rest: