Skip to content

Dashboard templates

Manufacturing · Customer service

A plant selling to B2B customers with a customer service team handling quality complaints, warranty claims and delivery inquiries via technical hotline, email, Zalo and the dealer portal. Output, OEE, scrap and quality plus ticket volume, response speed, satisfaction and tickets per 10,000 units by item.

Free plan with no time limit · No card required · Sample workspace ready in minutes

For B2B customer service teams at factories handling quality complaints, warranty claims and delivery status questions from the technical hotline, email and the dealer portal. The "Complaints by item" dashboard calculates tickets per 10,000 good units for each item, so high-volume items are not unfairly blamed. The two customer service dashboards cover response time, resolution rate and CSAT, with the production dashboards (output and OEE, downtime, quality) right alongside. Needs machine, item, production order, machine shift and support ticket data.

Use this template to

  • Pick which items need their inspection process reviewed when complaints per 10,000 units rise.
  • Compare which channel answers customers slowest and reset resolution time commitments.
  • Bring warranty ticket counts to the monthly quality meeting alongside scrap rate.

6 ready-made dashboards

Complaints by item

Tickets linked to manufactured items against good output, next to scrap rate, to see which items draw the most complaints.

  • Support tickets per 10,000 good units
  • Item-linked support tickets
  • Scrap rate
  • CSAT (satisfaction rate)
  • By item
  • Tickets per 10,000 units by item group
  • Weekly item-linked tickets by category

Customer service

Ticket volume, response and resolution speed, and customer satisfaction by channel and category.

  • Support tickets
  • Average first response time (hours)
  • Resolution rate
  • CSAT (satisfaction rate)
  • Daily tickets by category
  • By contact channel
  • Tickets by category
  • First response by channel group
  • NPS
  • Call abandonment rate

CS agents

Productivity, speed and quality of handling for each customer service agent and team.

  • Resolved tickets
  • Tickets per agent per day
  • First contact resolution rate
  • Ticket reopen rate
  • Results by agent
  • CSAT by team
  • Weekly CSAT by team

Output and OEE

Good output, output value and OEE broken into availability, performance and quality rate by workshop, machine and shift.

  • Good output
  • Output value
  • OEE (overall equipment effectiveness)
  • Scrap rate
  • OEE by machine
  • Weekly OEE by workshop
  • Performance by shift
  • Weekly good output by workshop

Downtime

Machine downtime by reason, machine and workshop; unplanned downtime drags availability down.

  • Downtime minutes
  • Unplanned downtime share
  • Availability
  • Downtime minutes by reason
  • Downtime minutes by machine
  • Weekly downtime minutes by workshop

Quality and production orders

Scrap and inspection defects by item and defect type; completed production orders and on-time rate.

  • First pass yield (FPY)
  • Inspection defect rate
  • Completed work orders
  • On-time completion rate
  • Quality by item
  • Defect rate by defect type
  • On-time rate by workshop
  • Monthly on-time rate

Ask Si as soon as the build finishes

  • “How did item-linked support tickets change compared with last month?”
  • “What is driving support tickets per 10,000 good units this quarter?”
  • “Show call abandonment rate by month for the last six months.”
  • “Where is average first response time (hours) highest this month, and why?”

28 defined metrics

Versioned definitions, shared by dashboards, Si, reports and MCP.

MetricDefinitionUnit
Item-linked support ticketsSupport tickets created in the period whose reference code matches a manufactured item (quality complaints, warranty, delivery about that item); can be broken down by item, item group and ticket category.Count
Support tickets per 10,000 good unitsItem-linked support tickets divided by good output in the same period, times 10,000. Shows how many tickets customers open about an item for every 10,000 units the plant produces; comparable between high- and low-volume items.= Item-linked support tickets * 10000 / Good outputNumber
Call abandonment rateCalls where the customer hung up before reaching an agent divided by all inbound calls.= cs_abandoned_calls / Inbound callsRatio (%)
Average first response time (hours)Average hours from when the customer created a ticket to the agent's first response, over tickets created in the period that have a response.= cs_first_response_hours_total / cs_responded_ticketsNumber
Average resolution time (hours)Average hours from creation to resolution for tickets resolved in the period.= cs_resolution_hours_total / Resolved ticketsNumber
Inbound callsCalls into the call center in the period, including calls abandoned by the customer.Count
CSAT (satisfaction rate)Share of surveys with a CSAT score of 4 or 5 on a 1-5 scale, among surveys with a valid CSAT score.= cs_csat_positive / Survey responsesRatio (%)
First contact resolution rateTickets resolved with a single contact and never reopened divided by tickets resolved in the period.= cs_fcr_tickets / Resolved ticketsRatio (%)
NPSNet Promoter Score = (promoters 9-10 minus detractors 0-6) x 100 / NPS responses. Scale -100 to 100.= cs_nps_points * 100 / cs_nps_responsesNumber
Ticket reopen rateTickets resolved in the period that were ever reopened divided by tickets resolved in the period.= cs_reopened_tickets / Resolved ticketsRatio (%)
Resolution rateTickets created in the period that are resolved divided by tickets created in the period.= cs_created_resolved / Support ticketsRatio (%)
Resolved ticketsTickets resolved in the period (by resolution date); status resolved or closed with a resolution timestamp.Count
Survey responsesPost-support surveys with a valid CSAT score (1-5), by customer response date.Count
Support ticketsSupport tickets created in the period (by creation date), any status.Count
Tickets per agent per dayTickets created in the period divided by agent working days with tickets.= Support tickets / cs_agent_daysNumber
AvailabilityRun minutes divided by planned minutes. The first component of OEE.= mfg_run_minutes / mfg_planned_minutesRatio (%)
Completed work ordersWork orders completed in the period, by completion date.Count
Inspection defect rateDefective samples divided by inspected samples across the inspection lots in the period.= mfg_defect_qty / mfg_inspected_qtyRatio (%)
Downtime minutesTotal machine downtime minutes recorded in the period, for every reason (including changeovers and scheduled maintenance).Number
First pass yield (FPY)Good output divided by total output. The quality component of OEE.= Good output / Total outputRatio (%)
OEE (overall equipment effectiveness)Availability x performance x first pass yield, computed on the period totals.= (mfg_run_minutes / mfg_planned_minutes) * (Total output / mfg_ideal_output) * (Good output / Total output)Ratio (%)
On-time completion rateWork orders completed on time divided by work orders completed in the period.= mfg_on_time_work_orders / Completed work ordersRatio (%)
Good outputGood units (total output minus scrap) produced in the period's shifts, by shift date.Count
Output valueGood output multiplied by the item's standard selling price, by machine shift date.Currency
PerformanceTotal output divided by the ideal output for the run time. The second component of OEE.= Total output / mfg_ideal_outputRatio (%)
Total outputTotal units produced in the period's shifts, including both good units and scrap.Count
Scrap rateScrap units (total output minus good output) divided by total output.= (Total output - Good output) / Total outputRatio (%)
Unplanned downtime shareUnplanned downtime minutes divided by total downtime minutes.= mfg_unplanned_downtime_minutes / Downtime minutesRatio (%)

Data you need

Required

machine, item, work_order, machine_shift, cs_ticket

Add if you have it (unlocks more metrics)

downtime_event, quality_inspection, cs_agent, cs_survey, cs_call

Three steps to this dashboard

  1. 1

    Connect your data

    Upload an Excel file or connect a source with: machine, item, work_order, machine_shift, cs_ticket.

  2. 2

    Approve Si's proposal

    Si proposes how to read your tables and map them to the industry's standard model; you fix anything highlighted and approve.

  3. 3

    Dashboards and Q&A

    The build gives you 6 dashboards and 28 metrics; ask Si anytime.

Data sources for this template

Connectors with a setup guide that feed the entities this template needs. Excel always works.

Related templates

Build Manufacturing · Customer service with your own data

Free plan with no time limit · No card required · Sample workspace ready in minutes