Identify the request from the ticket
Ticket SC-88214, request type returns credit, order 5109-77340 identified
Trade
depending on who opens the ticket.Open agent
Enlarge demo
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
The ticket contains an order number and one angry sentence. The service agent looks up the order in the shop system, the shipping status with the carrier, the return in the returns portal and the history in the CRM. Only then does she start writing, and the next colleague words her reply to the same request differently.
310
tickets a day
That is how many requests reach the service centre during the promotion week.
4
system switches
Shop system, carrier, returns portal and CRM for a single ticket.
7
request types
From shipment status to complaint, each type takes its own route.
9 minutes
per ticket
Most of it goes on piecing the facts together.
Four minutes after receipt, the draft with shipment status and returns history is in the ticket, and the service agent reviews it instead of compiling it: 60% faster processing.
The 60% speed-up in processing is this agent's headline figure. The 310 tickets a day and nine minutes per ticket sketch a promotion week in e-commerce service; they were not counted in any actual service centre.
The agent writes draft replies from the order and returns data; only what the service agent approves goes out.
Ticket SC-88214, request type returns credit, order 5109-77340 identified
Return booked into the warehouse on 4 August, credit still outstanding on 26 August
Draft in ticket SC-88214, 3 evidence lines with dates
It saves the draft in the ticket. The service agent decides whether the draft goes out as it stands.
It states the returns deadline, the receipt date and this customer's previous cases. Whether a credit is granted outside the deadline is decided by the service agent under the company's rules.
It relays the status reported for order 5109-77340. If the parcel is sitting unscanned in the distribution centre, the status it gives stays at the last scan.
Connected systems
Shop system
CRM
ticket system
Operations
Deployment model
Data processing
Responsible teams
How quickly is the Retail Customer Service Agent ready to use?
Where is the data processed?
Where does the figure “60% faster processing” come from?
All agents
50%
less data maintenance effort
PIM, e-commerce
15%
lower return rate
E-commerce, customer service
20%
less excess stock
Logistics, purchasing
25%
higher campaign performance
Marketing, e-commerce
40%
less audit effort
Legal, management
20%
less planning effort
HR department, store management