What GermainUX Watches
Find the Cause
Alert and Act
Set It Up
Overview
A customer writes to support: “I tried three times to update my card on your portal, and it keeps saying something went wrong.” The support agent can’t see what the customer saw. They pass the case to engineering, engineering can’t reproduce it, and the case goes back and forth until the customer gives up. The case has the customer’s words, not what the application did. It doesn’t say which request failed, since when, or whether anyone else hit it. Without that evidence, a real bug looks like a one-off, and the customers who failed and didn’t complain stay invisible. GermainUX records what every signed-in customer does and runs into on your portal: clicks, the requests behind them, the error messages they see, rage clicks, feedback and releases. With the GermainUX MCP Server, the support agent asks an AI assistant such as Claude about that customer in plain language. The assistant finds the session, reads what happened, checks how many other customers hit the same error and which release started it, and links to the evidence in GermainUX. It then drafts the engineering ticket with that evidence, ready to file in Jira.Questions It Answers
- What happened to account 100482 when they tried to update their card?
- Is it only this customer, or did others hit the same error?
- Which customers are affected, and what do they have in common?
- Since when, and did a release change something?
- What should the engineering ticket say, and where is the evidence?
- Is it fixed?
What GermainUX Watches
The assistant answers from the same KPIs the Workspace shows. Each signal is tied to the customer and the session it came from.Find the Cause
The investigation runs from one customer out to everyone, in one conversation with the assistant:- Find the customer’s session by their account number, and read its story: what they did, which request failed and which message they saw.
- Query the failing request for every customer over the same days. The assistant groups the failures by country, browser, page or any other field, and finds what the affected customers have in common.
- Look for a release that started it, and rule out what stayed normal.
- Ask for links to the evidence in GermainUX: the session replay, the analysis and the list of failures.
- Have the assistant draft the ticket with the evidence, file it in your ticketing tool, and ask again after the fix to confirm it worked.
Example: A Release Rejects Canadian and UK Postal Codes
At 09:00 UTC on a weekday, a portal release adds postal-code validation to the payment-method API. It only accepts US ZIP codes, so every card that a Canadian or UK customer saves gets an error. The portal shows “Something went wrong. Please try again.” That afternoon, account 100482 in Toronto tries three times, and the next morning their complaint reaches support.Find the customer's session
query_kpi), then reads the one from 18:40 (view_session_story). The customer opened Payment Methods, added a card and clicked Save Card three times. Each time, the request to save the card returned a 422 and the portal showed “Something went wrong. Please try again.” Between the second and third try, they rage-clicked Save Card, and before leaving they gave negative feedback. The assistant adds a link to the session in Session Replay (link_to_session_replay).
One Customer's Session, Told by the AI Assistant - Claude
Check who else
query_kpi) and groups the failures by country (get_field_values). In this example, 33 card saves failed between 09:00 and the next morning, against 2 in the same hours on the previous days. Canada has 25 of them, from 9 customers, and the United Kingdom 7, from 5 customers. The one other failure is a US customer who mistyped the card number. Account 100482 is one of 14 customers who couldn’t save a card. Most of them tried two or three times, and every one saw the same message.The same comparison is in the Workspace. In Aggregate Analysis of the failed card-save requests, Leading Factors rank the United Kingdom and Canada by country, and Montreal, Toronto and Calgary by city. Chrome 141 and Mobile Safari 18 rank too, only because most customers use them.
Failed Card Saves Analysis - GermainUX
Find what changed
query_kpi on Deployment Run): Customer Account release 2026.11.4 and an update of the payments-papi API. The API was rolled back at 10:15 and the failures carried on, so the Customer Account release is the change still in place.
Two Deployments Before the First Failure - Claude

Failed Card Saves Between the Release and the Fix - GermainUX

Release 2026.11.4 Marker Details - GermainUX

What the Release Changed - Claude
Rule out the rest

Nothing Else Broken - Claude
Draft the ticket
link_to_session_replay, link_to_analysis, link_to_drillthrough) and writes the bug, ready to paste into Jira. It names the release, the request and its 422 response, the countries affected, the number of customers, and the steps to reproduce with a Canadian postal code. Engineering doesn’t need to reproduce anything to start.The support agent files it in Jira. To keep the evidence in GermainUX too, they can add it as a Note on the customer’s session or on the analysis, assigned to the engineering team.Confirm the fix

Card Saves Before and After the Fix - Claude

Release 2026.11.5 Marker Details - GermainUX
Alert and Act
Most affected customers never complain, which is the reason to catch this sooner:- SLAs and outlier detection on the error rate of key requests, such as saving a card, by country, so a release that breaks one segment raises an alert
- Alerts when user-facing errors or rage clicks rise on a page, by email, Microsoft Teams or Slack
- Synthetic user scenarios that save a card with a Canadian and a UK test account right after each release
- Automated actions that roll back the release when the card-save SLA fires, with approval before they run
- Percent change SLAs on negative feedback, so a rise in complaints on one page reaches the product team the same day
Set It Up
Each step adds value on its own. The assistant can answer more questions the more of the portal GermainUX monitors.Monitor the portal
Identify the customer
Show releases on the timeline
application.name == "Customer Account", or the releases of your other applications show on the portal’s charts too.Enable the MCP Server for support
Connect the AI client
Additional Resources
MCP Server
Analysis Dashboard
Use Cases
Get Help
Every support team has its own portal, customer identifiers and ticketing workflow. The GermainUX team can help you identify customers in their sessions, bring your releases onto the timeline, set up the MCP Server for your support agents, and agree what a good engineering ticket includes.Contact GermainUX Support
Can't Find What You Need?
The content of this document is proprietary to GERMAIN SOFTWARE.

