When Production Stops, Who Responds? How to Make Support Calls Reliable

Quick Answer

When production stops, most factories rely on phone calls, walking the floor, or andon lights that no one monitors. Reliable support calls require three things: instant digital routing to the right person, automatic time-based escalation, and automated downtime documentation. Manufacturers using this approach -- like Gazelle -- have reduced unplanned line downtimes by 35%.

Every assembly line stops. The question is what happens in the minutes after it does and whether the right person responds before that stop becomes an expensive problem.

Most manufacturers still manage support calls the way they did twenty years ago: an operator pulls an andon cord, a light turns on, and someone hopefully notices. Or they make a phone call, walk the floor, or ask a colleague. Meanwhile, the line stays down and the clock keeps ticking. According to Siemens' True Cost of Downtime 2024 report, unscheduled downtime costs the world's 500 largest companies $1.4 trillion annually up from $864 billion in 2019.

Workerbase is an Execution Layer platform that sits between your planning systems (ERP, MES) and frontline workers to guarantee that work on the shop floor actually happens. Correctly, on time, and across shifts. In this post, we break down why traditional support call processes fail, what reliable digital support calls look like in practice, and what leading manufacturers are achieving when they close this gap.

What makes traditional andon systems unreliable?

Traditional andon systems were designed for visibility, not execution. A light turns on. A board updates. But nothing guarantees that the right person sees it, responds to it, or documents what happened.

The failure pattern is consistent across factories. First, the operator signals an issue but the signal goes to a physical location (a light tower, a board), not to a specific person. If the team lead is on break, in a meeting, or at the other end of the hall, nobody responds. Second, there is no built-in escalation. If the first responder doesn't react, the issue stays unresolved until someone physically notices. Third, when the issue is finally resolved, documentation is either manual (paper forms filled out after the fact) or skipped entirely.

Competitor platforms have improved the visibility layer: digital dashboards, real-time alerts, and centralized monitoring. But visibility alone doesn't close the gap. Knowing that a line is down is not the same as guaranteeing that the right person is already on the way. What's missing is the execution layer: the system that assigns, routes, escalates, and documents support calls as a structured workflow, not just a notification.

What do reliable digital support calls look like?

Reliable support calls follow a four-step digital workflow that removes every manual handoff and decision point from the process.

Step 1: Instant digital notification. When an operator encounters an issue, they trigger a support call directly on their shop floor device. The system knows who is on shift, who has the right skills, and who is available. The request is routed to the right person immediately, with full context: which station, what type of issue, what has already been tried.

Step 2: Automatic acceptance or escalation. The responding team lead receives the request on their device with a clear accept/reject action. If no one accepts within a defined time window (for example, five minutes) the system automatically escalates to the shift lead. No issue falls through the cracks, regardless of shift changes, breaks, or availability.

Step 3: Guided resolution. The responder follows digital work instructions on their device if needed. Step-by-step guidance, relevant documentation, or checklists that ensure the issue is resolved correctly the first time.

Step 4: Automated documentation. Once the issue is resolved and the line restarts, the downtime reason, response time, and resolution steps are captured automatically. This creates a clean data trail for root cause analysis and continuous improvement without anyone filling out a paper form after the fact.

The result is a process where every support call is automatically assigned, tracked, escalated if needed, and documented.

How does a digital support call work inside Workerbase?

Seeing the workflow in action makes the difference tangible. In our recent webinar "When Production Stops, Who Responds?", Robin Heesen walked through a live demonstration of the entire support call process inside Workerbase.

The demo covers three perspectives simultaneously. From the operator's view: triggering a support call in two taps on a shop floor tablet, selecting the issue category, and immediately notifying the right colleague. From the team lead's view: receiving the request with full context, accepting it, and starting the resolution process.

Every step is logged. Every handoff is tracked. And when the line restarts, the downtime reason is captured automatically.

Watch the full live demo on Youtube.

Which KPIs improve when you digitize support calls?

The impact of digitizing support calls shows up across multiple operational KPIs, not just response time.

Unplanned downtime reduction. Gazelle, Europe's leading bicycle manufacturer, reduced unplanned line downtimes by 35% after digitizing their andon process on the final assembly lines with Workerbase with ROI achieved in under three months. Read the full Gazelle customer story.

Response time improvement. Industry data shows that digital andon implementations typically reduce response times to line stoppages by 40% or more. With automatic routing, the time between "line stops" and "right person is notified" drops from minutes (or longer) to seconds.

Annual cost savings. Porsche achieved seven-figure annual savings by digitizing support calls on their final assembly line and additional execution gaps like real-time vehicle information access and vehicle movement orchestration. Read the full Porsche customer story.

Root cause analysis quality. When every support call is documented automatically -- downtime reason, response time, resolution steps -- you build a dataset for continuous improvement that simply doesn't exist with manual processes. Recurring issues become visible. Patterns across shifts emerge. This is the foundation for reducing the same problems from coming back, which is the core promise of any issue management system.

What are the most common mistakes with support call processes?

Even manufacturers who recognize the problem often fall into patterns that prevent real improvement.

Mistake 1: Treating visibility as execution. Installing dashboards and digital andon boards is a start, but it doesn't guarantee anyone responds. As Oliver Hoffmann, CTO at thyssenkrupp Rasselstein, observed about the broader challenge: "Issues that have been frustrating for a long time are resolved rapidly" -- but only when you move beyond visibility to structured execution.

Mistake 2: Relying on phone calls and personal networks. When the response path depends on knowing who to call and whether they pick up, the process is inherently unreliable. It breaks during shift changes, holidays, and staffing fluctuations. A system-based approach routes to the role, not the person.

Mistake 3: Skipping documentation to save time. Manual documentation after the fact is either incomplete or doesn't happen. This means you lose the data you need for root cause analysis and the same issues keep returning. Automated capture at the point of resolution solves this without adding any burden to the operator or responder.

Mistake 4: Over-engineering the rollout. Many manufacturers hesitate because they see digital transformation as a massive IT project. Workerbase runs independently or integrates with your existing systems like SAP, MES, QMS, SCADA. You don't need to replace anything. The typical path starts with a single use case, calculates the business value, and expands from there.

Frequently Asked Questions

What is a digital support call in manufacturing?

A digital support call is a structured, system-driven workflow that replaces manual andon signals, phone calls, and walking the floor. When an operator encounters an issue, they trigger a request on their device that is instantly routed to the right person based on shift, skills, and availability. The system handles escalation and documentation automatically, creating a reliable process for every line stoppage. Learn more about digital andon systems and how they differ from traditional approaches.

How much does unplanned downtime cost in manufacturing?

According to Siemens' True Cost of Downtime 2024 report, unscheduled downtime costs the world's 500 largest companies $1.4 trillion annually. Aberdeen Research estimates the average manufacturing facility loses approximately $260,000 per hour of unplanned downtime. Even in mid-sized plants, the cumulative cost of repeated short stoppages (each just 10 to 30 minutes) adds up to significant annual losses.

What is the difference between a digital andon and a traditional andon system?

Traditional andon uses physical signals like lights, cords, boards to make problems visible. Digital andon goes further by routing alerts to specific people, enforcing time-based escalation, and capturing documentation automatically. The key difference is execution: traditional andon tells you something is wrong, while a digital andon system like Workerbase guarantees the right person responds and the resolution is tracked.

Can digital support calls integrate with our existing ERP and MES systems?

Yes. Workerbase is designed to sit between your planning systems (ERP, MES) and your frontline workers as the Execution Layer. It integrates with SAP, MES platforms, QMS, SCADA, and other shop floor systems. You don't need to replace your existing systems. Workerbase connects to what you already have and closes the execution gap between planning and the people doing the work.

What results have manufacturers achieved with digital support calls?

Gazelle reduced unplanned line downtimes by 35% with ROI in under three months. Porsche saves millions annually across their final assembly operations. thyssenkrupp reports that "teams are actively asking to implement Workerbase because they see that it works."

What's telling is how these manufacturers got there. Gazelle started with a single pilot line at one plant, digitizing their andon process as their first use case. Once the results were proven (faster response times, automatic escalation, and clean downtime data for the first time) they rolled out across all assembly lines in that plant, then expanded to additional plants entirely. Along the way, they closed further execution gaps beyond support calls. The MyFactory press article on the Gazelle case details this expansion path. It's a pattern we see consistently: start small with the problem that hurts most, prove the value in weeks, then scale at your own pace across lines, plants, and use cases. That's how leading manufacturers are closing the Execution Gap.