A prospect is on your pricing page, comparing you to two other vendors. All three make the same claims — "world-class support," "customers love us." None of them prove it. Meanwhile your team has been collecting CSAT scores on every resolved ticket for six months, sitting at a solid 4.6 out of 5. That number is real, current, and completely invisible to the person who's about to make a buying decision, because it lives in Jira and nowhere else.
This is a strange gap. Teams will spend weeks getting their CSAT collection process right — timing, response rates, follow-up automation — and then let the resulting number die inside a service desk that only agents and admins ever look at. The data that could be doing marketing's job for free never leaves the ticket.
Why a Static Claim Doesn't Do the Job
"4.6/5 average rating" in your website footer, updated by hand once a quarter, isn't that different from just saying "customers love us." It's a claim, not evidence. What actually reads as credible is a number that visibly moves — one a visitor can reasonably assume is being recalculated from real, ongoing tickets rather than picked once and left to go stale.
That distinction matters more for JSM-based teams than most, because the whole point of running support through Jira Service Management is that every interaction is logged, timestamped, and measurable. You have the underlying data to make the badge honest. The only missing piece is a path from "score sitting in a Jira field" to "score rendered on a public page."
There's also an internal argument for this, separate from the marketing angle: a support team whose score is visible externally has a different relationship with that number than one where it's purely an internal KPI. Visibility changes behavior in both directions — it's harder to let a bad quarter slide when the number is on the homepage.
What Actually Has to Be True First
Before an external badge is possible, three things need to line up:
- You're collecting the right kind of feedback. Myra ships with a built-in CSAT survey and a built-in NPS survey for every space — both auto-generated, and both locked to prevent accidental renames or deletion so your historical reporting stays consistent. Either can feed a public score, or you can build a custom Feedback Survey if you want a different question or calculation strategy.
- The survey is scoped correctly. This is the part teams miss. Myra's Feedback Surveys run under one of three scopes — Request, Project, or Public. A Request-scope survey is tied to the lifecycle of an individual ticket and its score can only be shown in the portal or request context. If you want a score you can embed on an external site, the survey needs to be Project or Public scope — those are the ones that generate a public-facing link and widget.
- You've picked a calculation strategy that produces a number worth showing. Average is the obvious choice for a star-rating CSAT badge; NPS strategy is built specifically to roll responses up into Promoter/Passive/Detractor and produce the standard -100 to +100 score. Whichever you pick becomes the number that gets rendered — so make sure it's the one you'd actually want a prospect to see.
Setting Up the Badge
Once you have a Project- or Public-scope survey collecting real responses, the rest lives in the survey's Display configuration section:
- Display Text — the label that sits next to the number ("Customer Satisfaction," "Support Rating," whatever matches your site's voice). Use the built-in preview to check it actually reads well before it's live.
- Measurement Range — a rolling window, in days, that the score is calculated over. This is the setting that keeps the badge honest — instead of an all-time average slowly going stale as your team improves (or a single bad week never fully recovering from), the badge reflects a recent, defined window of service quality.
- Portal Score Display — shows the live score at the top of your JSM customer portal. Worth turning on regardless, since it's the internal-facing sibling of the external badge.
- Public Score Display — the one you actually want here. Toggling it on generates a custom HTML snippet. Copy it, drop it into your site — pricing page, homepage, support page, wherever a visitor would reasonably want proof.
One configuration step gets skipped often enough that it's worth calling out explicitly: if your website enforces a Content Security Policy, the widget will silently fail to load until you update your CSP headers to allow the script and style sources the widget depends on. It's not a bug — it's the CSP doing exactly what it's supposed to do, blocking a script source it doesn't recognize. Add the directives for the widget's origin to script-src and style-src, and it renders normally.
The Takeaway
If your team already has a CSAT or NPS survey running in JSM with a real response volume behind it, you're one scope check and one settings toggle away from a trust signal your sales page currently doesn't have. The number is already true — it's just been locked inside a tool your prospects never see. Confirm the survey is Project or Public scope, set a measurement range that reflects recent performance rather than an all-time average, and put the badge somewhere a skeptical visitor is actually going to look before they decide whether to trust you.