Classify incoming mail by request type
Overnight run at 04:10, 486 messages, 9 request types, 12 unassigned
Energy
Only then can anyone answer it.Open agent
Enlarge demo
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
The inbox mixes emails, portal messages and scanned letters in a single queue. Every message is opened, matched to a request type, linked to its contract account via the customer number and then moved to the right queue. Only then does the actual reply begin, and everyone on the team writes it differently.
480
messages a day
Emails, portal messages and scanned letters all flow into one queue.
9
request types
From meter readings to instalment changes, each one goes to a different queue.
2 minutes
per assignment
Open it, look up the customer number, find the contract account, pick the queue.
16 hours
of routing a day
The total appears in no plan, yet the team spends it every single day.
At eight o'clock the early shift opens a queue in which every message is already linked to its contract account, and the 16 hours of routing shrink by up to 70%.
The reduction of up to 70% in routing effort is this agent's headline figure. The volume, request types and minutes per assignment describe a typical day in a utility's customer service; they are illustrative, not measured.
The customer adviser decides whether the reply goes out; the agent classifies the incoming message, links it to the contract account and attaches a draft.
Overnight run at 04:10, 486 messages, 9 request types, 12 unassigned
Contract account 8814-2207 for meter number 1EMH0074392, matched via the supply address
entwurf_zaehlerstand_8814-2207.docx, 3 inserted values with sources
The draft waits in the customer advisers' inbox. The adviser handling the case approves and sends it.
If a customer asks for a reminder fee to be waived, it moves the case, with the payment history, to the receivables management queue. The team lead signs off the decision.
It puts the message in the exceptions queue and notes which details it searched for. The inbox specialist makes the assignment.
Connected systems
SAP IS-U billing system
customer service CRM
document management
Operations
Deployment model
Data processing
Responsible teams
How quickly is the Customer Service Inbox Agent ready to use?
Where is the data processed?
Where does the figure “up to 70% less manual routing effort” come from?
All agents
50%
faster processing
Grid planning, engineering
60 to 75%
less data entry effort
Grid services, customer service
50%
less manual review effort
Billing, network operators
55%
faster processing
Grid services, customer service, grid connection
60%
fewer follow-up queries
Customer service, heat sales, municipal account management
up to 65%
less handling time
Customer service, billing