How the New Starhan System Revolutionizes Customer Service Workflow and Boosts Efficiency

Background

Customer service is critical for both user and driver experience. Traditional CSC ticketing systems required lengthy coding cycles and could not quickly adapt to business growth. Starhan, a new ticketing system with a graphical configuration and agile deployment, aims to provide low‑cost, high‑efficiency, high‑quality communication between drivers and the platform.

Business Goals and Core Metrics

Cost : Keep staffing costs stable while supporting increasing ticket volume.

Efficiency : Increase automation ratio and SLA compliance.

Experience : Achieve high call‑answer rates and satisfaction scores.

Challenges & Pain Points

Long release cycles : Even the fastest deployment required at least three days, limiting rapid business response.

Multi‑line support pressure : The development team must serve many business lines (city‑to‑city freight, enterprise logistics, moving, cold chain, car rental, etc.), stretching limited resources.

Heavy coding requirement : The legacy CSC system relied on state machines and embedded logic, making changes cumbersome.

Solution – Starhan System

Starhan introduces a core workflow orchestration capability that replaces fixed state‑machine logic with a highly configurable rule engine and visual process designer.

Design Principles

Business‑centric : Architecture aligns tightly with real‑world use cases.

Business abstraction : Key business attributes are extracted, abstracted, and recombined for reuse.

Open‑closed principle : Extensible via template methods and abstract factories, avoiding repeated wheel‑building.

Process Architecture

The workflow consists of Inputs (start), Connecting (links), Activities (system tasks), Activities (human tasks), Gateways (conditions), and Outputs (end). This design enables rapid configuration without coding.

Standardized Flow

Compared with mainstream engines (Activiti, Flowable, Compileflow, Turbo), Starhan’s engine is lightweight and business‑oriented, borrowing BPMN2.0 concepts while simplifying and splitting components.

Dynamic Process Management

Operators can use a graphical editor to build or adjust ticket‑handling flows in a day (T+1), eliminating the need for code changes.

Tools and Extensions

Tools integrate with downstream systems (billing, payment) via configurable nodes:

Execution nodes : Synchronous API calls.

Task nodes : Asynchronous operations such as approvals.

These extensions enable low‑cost, high‑efficiency processing.

Automation

Automation handles routine queries automatically, routing complex cases to human agents. Nodes such as data collectors, sub‑processes, and tool‑trigger nodes provide intelligent, modular automation.

Performance Optimization

Data caching : In‑memory and two‑level distributed caches reduce I/O.

Asynchronous processing : Event‑driven design, thread pools, and message queues lower latency.

Multithreading : Parallel execution of independent conditions and API calls, with careful thread‑pool tuning.

These measures yielded a >70% performance gain.

Reliability Enhancements

Comprehensive data recording : Full lifecycle data, cold storage for post‑mortem analysis.

Fast fault tolerance : Time‑outs, fallback results, and detailed exception stacks.

Monitoring & alerting : TraceReport component, Monitor platform, and threshold‑based alerts.

Overall Benefits

Starhan’s workflow orchestration dramatically improves efficiency, reduces errors, shortens onboarding, and boosts customer satisfaction. The modular, configurable approach is applicable beyond customer service to sales, supply‑chain, and other operational systems.

Conclusion

Introducing a flexible workflow engine in the ticket‑service scenario enhances system stability, performance, and user experience while supporting rapid business evolution.