Skip to main content

CUSTOMER STORY

Connect devices and apps to diagnose pickup issues

Watch the interview

ABOUT LINQU

About the customer

Linqu Smart develops and operates smart locker systems, providing logistics solutions for community deliveries and parcel collection. Each collection involves a user scan, locker communications, lock controls, and backend interfaces, so the coordination between devices and applications directly affects the final delivery experience.

Smart devices Industry
Smart locker systems Business focus
Communities and delivery Serves

With Guance’s flame graphs and tracing, we can identify slow mobile pages and failed deliveries.

Zhang HaoweiOperations Director, Linqu Smart

The challenge

One failed locker opening can span devices and applications

Linqu Intelligent connects user actions, smart-locker communication, and backend APIs. When a user reports a failed scan or a locker that will not open, the team needs to reconstruct the action before checking the device, connection, or service.

01

Operation logs, device state, and API calls were stored separately. Investigators had to coordinate several entry points and manually align times and devices.

02

An error message alone did not explain the relationship between MQTT connections, lock control, and backend requests. This also made handoffs between support and technical teams harder.

KEY RESULTS

30%

Expected reduction: Locker-failure diagnosis time

25%

Expected reduction: Remote collaboration hours

15%

Expected reduction: Monitoring maintenance effort

Customer interview

Linqu Intelligent · Customer interview

Connect devices and apps to diagnose pickup issues

SOLUTION

Linqu Intelligent × Guance — Solution

01

Link records through devices and user actions

Device communication, operation logs, APIs, and resource health enter a common view. Reviewing changes by device and time gives a failed locker operation an investigation context.

30%

Expected reduction: Locker-failure diagnosis time

Smart lockers connect delivery, device control, and parcel collection
02

Connect app experience to backend calls

RUM observes the app experience while APM covers key APIs. Teams can move from user actions and app errors to service calls, related logs, and backend runtime state.

25%

Expected reduction: Remote collaboration hours

Alert context connected to analysis and investigation guidance
03

Give alerts device and business context

Monitoring covers connections, lock control, and key interfaces. Responders can review the related device and service trends to define the scope of the investigation.

15%

Expected reduction: Monitoring maintenance effort

BUSINESS IMPACT

Turn a user's report into a specific issue that teams can investigate together

01

Less manual reconstruction across tools

Device and application records can be checked for the same period, helping teams identify where the workflow failed.

02

Remote collaboration centers on evidence

User experience, device state, and backend calls give support and technical teams a shared starting point instead of repeated descriptions of vague symptoms.

03

Recurring problems leave a usable trail

Connection and service trends preserve evidence for reviewing similar failures without restarting every investigation.

Build observability around your business

Work with Guance to connect telemetry, investigate service issues, and give teams shared operational context.