Skip to main content
All use cases

Customer record update automation.

Change requests pile up in a shared mailbox while staff update records field by field. With Exekra, each request is picked up as it arrives and applied through the screens your staff already use; the service team handles only the incomplete or unusual ones.

How it runs with Exekra.

How it is done today

  • Read change requests from a shared mailbox or a file
  • Find the customer in the core system
  • Update the record, field by field
  • Reply to confirm, or ask for what is missing

With Exekra

  1. 1Picks up each request as it arrivesA mailbox or folder arrival trigger
  2. 2Finds the customer and updates the recordSteps in the core system's web or desktop screens
  3. 3Checks the change tookReads the record back before moving on
  4. 4Sends incomplete requests to the service teamA Hub worklist
  5. 5Confirms to the customerAn email step

Where people stay involved

The service team handles requests that are incomplete or unusual.

What could improve

  • Records are updated the same day, the same way
  • Every change is traceable to its request and run
  • Staff spend their time on the customers who need a person

On your own servers.

The automation is built and tested in Exekra Studio, then runs on a Runner inside your network, governed and measured in the Hub. The documents it handles, the credentials it uses and the record of every run stay on your machines.

How Exekra is deployed and secured

Where this process comes up

  • Banking
  • Insurance
  • Telecommunications

Other processes

See it on your own customer record updates.