Learn how the Agent Rating component in ServiceNow FSM Paris holds the numbers customers assign to agents. This overview contrasts it with performance logs, agent scores, and customer feedback, helping you understand where ratings live and how they evolve over time.

Multiple Choice

Which plugin stores the agent rating record for FSM Customer Experience?

Agent ratings for FSM Customer Experience are stored by the Agent Rating component, which uses the wm_agent_rating table. This is the dataset that records the numeric ratings customers give to agents after interactions, allowing you to track performance over time. Other data lives elsewhere: performance logs are in wm_agent_performance, computed or stored agent scores reside in wm_agent_score, and customer comments live in wm_customer_feedback. Since the question asks which plugin stores the agent rating records, the Agent Rating (wm_agent_rating) is the correct choice.

When teams talk about field service, the human touch often matters as much as the hardware and schedules. In ServiceNow’s Field Service Management (FSM) world, the way customer feedback becomes data you can act on is built right into the data model. One piece of that puzzle that deserves a closer look is the Agent Rating component. This isn’t just a pretty label in a table; it’s the dataset that holds the numeric ratings customers give to agents after interactions. In FSM Customer Experience, the Agent Rating record lives in the wm_agent_rating table, and understanding its role helps fly-under-the-radar insights turn into real improvements.

Let’s zoom into what Agent Rating actually does

  • What it captures: The agent rating record is a focused snapshot of customer sentiment. It stores a numeric score tied to a specific interaction or period, offering a clean signal about performance from the customer’s perspective. Think of it as a bite-sized thermometer reading that you can compare over time.

  • Why it matters: Numbers tell a story when you plot them against time, agent, and work type. A rising rating trend might reflect improved communication, better on-site execution, or smoother issue resolution. A dip could flag gaps to bridge—whether that means additional training, updated processes, or clearer service expectations with customers.

  • How it fits with other data: FSM also collects data in other places—like performance logs or qualitative feedback. The Agent Rating table provides the quantitative backbone, while other sources (such as wm_customer_feedback for comments or wm_agent_performance for activity logs) add context. Together, they give a fuller picture of customer experience.

The data ecosystem around ratings: a quick tour

  • Agent Rating (wm_agent_rating): The star of the show for numeric scores. It ties a rating to a particular agent and interaction context. This makes it easy to drill down: who tended to get higher scores, and in what scenarios?

  • Agent Score (wm_agent_score): This is a computed or stored score that aggregates various signals into a single metric. It’s useful for quick dashboards and heatmaps of performance across teams or regions.

  • Performance Log (wm_agent_performance): Think of this as the activity ledger. It records actions, outcomes, and sometimes operational details that influence how a rating might be earned or interpreted.

  • Customer Feedback (wm_customer_feedback): The flavor text—the comments customers leave. The notes can illuminate why a rating was high or low, offering qualitative nuance that a number alone can’t convey.

Why the Agent Rating table stands out

  • Precision over time: Ratings are often time-bound. You can align them with service windows, dispatch cycles, or specific field service campaigns. This temporal aspect helps you see how experiences shift as processes evolve.

  • Individual agent focus: Because the rating ties to a specific agent, it’s straightforward to recognize who consistently scores well and who could use targeted coaching. It’s like having a performance lens focused on the human element of service delivery.

  • Actionable signals: A spike or drop in ratings can trigger concrete steps—adjusting routing logic, updating knowledge articles, or tweaking how technicians communicate with customers. It’s less about vanity metrics and more about real-world impact.

Common patterns and practical implications

  • Pattern: Ratings improve after training or after introducing a new tool. You might notice a gentle upward drift after a coaching session or a rollout of a mobile checklist that keeps technicians aligned with best practices.

  • Pattern: Ratings vary by service type or location. Some jobs may inherently carry more complexity or higher stakes in customer perception. Segmenting ratings by work type or geography helps pinpoint where to invest in process changes or resource adjustments.

  • Pattern: Qualitative comments fill in the gaps. A number might be neutral, but a quick note like “polite and professional, but the ETA was off” can point to process friction that numbers alone miss.

Best practices for working with Agent Rating data

  • Tie ratings to meaningful events: Link a rating to the service call, work order, or field service interaction. This makes it easier to map a customer sentiment to what happened on site.

  • Combine with context: Don’t rely on the score alone. Cross-reference with wm_customer_feedback to surface explicit reasons behind ratings. If a rating dips, the comments can quickly guide you to the root cause.

  • Segment for clarity: Analyze by agent, skill, region, service type, and time period. Different teams may reveal different strengths and opportunities.

  • Guard privacy and ethics: Ratings reflect customer opinions. Treat the data with care, especially if it’s possible to identify customers or sensitive scenarios. Anonymize where appropriate and adhere to data governance guidelines.

  • Use dashboards with intention: Build visuals that answer practical questions—“Which agents have the highest average ratings this quarter?” or “Do ratings improve after a particular training module?” Dashboards should guide action, not overwhelm with numbers.

  • Plan data hygiene: Regularly check for missing or inconsistent records. A rating without a linked interaction is like a message with no sender—it’s hard to interpret.

A day-in-the-life with the data

Imagine a dispatch team that’s trying to understand why some field visits feel smoother than others. They pull Agent Rating data alongside performance logs and customer feedback. They notice that visits flagged as “urgent” sometimes receive lower ratings, but only when the ETA slips by more than 15 minutes. The data points don’t just tell them “something’s off.” They point to a workflow adjustment: tighten ETA estimates, perhaps adjust the on-site process checklist, and communicate more clearly with customers about delays.

Another example: a regional service desk sees a trend where recent hires are gradually earning higher ratings as they accumulate experience. This pattern nudges leadership to review onboarding content and mentorship structures. It’s not about pushing numbers up for the sake of it; it’s about recognizing that early-stage agents might benefit from structured guidance that accelerates confidence and competence in the field.

Relating to the broader FSM Paris release

Paris brings refinements across the board for ServiceNow FSM, and the Agent Rating construct sits nicely at the intersection of customer experience and workforce management. It’s designed to be practical, not ornamental. The focus is on making ratings reliably ingestible, linkable to the right interactions, and easy to visualize in dashboards that operations teams actually use. If you’ve worked with other ServiceNow data models, you’ll notice the pattern: dedicated tables for distinct data slices, with clear relationships to workflows, tickets, and service calls. The Agent Rating table is the clean, purpose-built receptacle for customer sentiment numeric data, designed to connect the dots between customer experience and agent performance.

A few notes on the ecosystem

  • Data lineage matters: When you pull a rating, you’re often joining it to the associated work order, the agent profile, and the service call timeline. Understanding those joins helps prevent misinterpretation and makes reporting more reliable.

  • Real-world friction points exist: Not every rating is perfectly clean. Some customers may rate without a full context, or there might be edge cases where the rating isn’t tied to a completed interaction. Having processes to validate and, if needed, flag such anomalies keeps insights trustworthy.

  • There’s value in velocity: The sooner you can surface a drop in ratings, the faster you can respond. A lightweight alerting rule that flags unusual rating patterns can be a win for both customers and agents.

Digging a little deeper: what isn’t in the Agent Rating table

  • It doesn’t store narrative only: It’s a numeric score at its core. Textual feedback lives in wm_customer_feedback or in other related fields. The score is the anchor, the comments add texture.

  • It isn’t the only lens on performance: You’ll still want to look at wm_agent_performance for actions and outcomes and wm_agent_score for aggregated performance views. The Agent Rating table complements these, it doesn’t replace them.

What this means for teams in practice

  • A practical mindset: Treat Agent Rating as a pulse check on customer sentiment tied to a specific interaction. It’s a living metric you can monitor, trend, and respond to with concrete improvements in service delivery.

  • A collaborative approach: Ops, CS, and field technicians can all benefit from listening to ratings. Shared dashboards that include both numbers and comments help align expectations and foster improvements without finger-pointing.

  • A continuous loop: Collect, analyze, act, and re-measure. The feedback loop is where the magic lives: ratings spark changes, changes impact experiences, and experiences feed new ratings.

Tying it all together

In the FSM Customer Experience landscape, the Agent Rating (wm_agent_rating) is the sturdy thread that ties customer sentiment to the human element on the ground. It’s the dataset that makes it possible to track how an individual technician’s performance is perceived over time, and it works in harmony with other data stores to give a comprehensive view of service quality. The act of rating isn’t just a number—it’s feedback that can guide coaching, process tweaks, and better customer communication.

If you’re exploring how customer experience translates into actionable insights within ServiceNow FSM, start with the Agent Rating table. Look at the trends, correlate them with the context you can access in wm_agent_performance and wm_customer_feedback, and let those signals guide sensible, human-centric improvements. After all, behind every number is a real customer and a real moment of service—and that moment matters more than any chart.

And yes, the Agent Rating (wm_agent_rating) is the key piece that stores those pivotal rating records, the quiet workhorse that keeps the feedback loop honest and usable. If you’re curious to see how a few well-placed adjustments to data visibility or dashboard design can sharpen decisions, that’s where the journey begins.