Skip to main content

What GermainUX Watches

Usage, frictions and feedback

Find the Cause

Two worked examples

Hear and Help Your Users

Feedback, help and synthetic tests

Set It Up

What to deploy and configure

Overview

Your organization invested in Oracle Siebel CRM, but users don’t always work the way it was designed. They skip a new view, repeat searches, keep a spreadsheet on the side, or give up on a task halfway. Most of them never open a ticket, so the problem stays invisible until adoption figures disappoint. GermainUX measures how users actually work in Siebel and shows why adoption stalls: the view nobody finds, the step that takes too long, the error that sends users to a workaround. It also gives users a quick way to tell you what they feel, alerts your support team when a user is stuck, and tests key workflows before users meet a broken one.
AdoptionFrictionAffected UsersAnalysisSession ReplayHelp the User
This page uses Oracle Siebel CRM as the example. The same approach works for any application GermainUX records, including customer-facing and eCommerce sites, where the people you hear and help are visitors.

Questions It Answers

  • Which Siebel views and features do users avoid?
  • Why do agents skip the new Service Request view?
  • Which step makes creating an order take so long?
  • Which teams, roles or locations struggle the most?
  • What do users say about Siebel, and what were they doing when they said it?
  • Which user needs help right now?

What GermainUX Watches

GermainUX combines usage, behavior, process and technical signals from every recorded Siebel session.
Adoption tab for Siebel with adoption, active users and friction per session, drilling down into friction analysis and recommendations

Siebel Adoption to Friction Analysis - GermainUX

Find the Cause

The investigation is the same for every adoption question. Start from the adoption KPI or the process that disappoints, find who is affected and where, rule out what stayed normal, and then watch one session as evidence. See Adoption Insights for the full method.
  1. Open the Adoption tab to see which signal moved: active users, feature usage, frictions or work time.
  2. Open the Analysis Dashboard on that KPI. Leading Factors show whether the problem concentrates in one team, role, view, location or browser.
  3. Open one affected session in Session Replay to see what the user saw and did.
  4. After the fix, compare the same KPI for the same users before and after the change.

Example: Agents Avoid the New Service Request View

Your team released a new Service Request view for the call center. In this example, about half the agents try it in the first days, but two weeks later only one agent in five still uses it. The others went back to creating Service Requests the old way.
1

Measure who uses it

Open feature-usage analysis for the new view. In the last 7 days, 25 agents used it, against 61 in the release week.
Analysis of clicks in the Service Request Quick Create View for the last 7 days, used by 25 agents against 61 in the release week, with daily clicks and the release markers on the Relationships chart

Usage of the New Service Request View - GermainUX

To see which teams still use it, compare one team with the others. In this example, 19 of the 25 agents who still use the view are in Technical Support, nearly the whole team. The other 6 come from the other three teams together.
Compare page of clicks in the Service Request Quick Create View in the last 7 days: 19 Technical Support agents with 2,619 clicks against 6 agents in the other teams with 464 clicks

Technical Support Against the Other Teams - GermainUX

2

Find what stops the others

Filter the frictions to the new view. Searches with no results and back-and-forth navigation point to a discoverability problem. Validation errors and slow saves point to a usability or technical one.
Analysis of searches with no results in the new Service Request view, grouped in the first days after its release on the Relationships chart

Searches with No Results on the New View - GermainUX

Analysis of Siebel error popups in the new Service Request view the day after its release, with errors per hour peaking on the release day, and markers for the user-facing errors across Siebel

Siebel Errors on the New View - GermainUX

3

Watch one agent try

Open a session where an agent opened the view and left it. Read its AI summary for where they gave up, then watch that moment in Session Replay.
You now know whether agents need training, a layout change or a technical fix. After the change, check that usage of the view grows for the teams that avoided it.

Example: Creating an Order Takes Four Times Longer Than Expected

The order-creation process is expected to take two minutes. In this example, users need almost eight minutes, in every team, and some keep notes outside Siebel to get through it.
1

Find the slow steps

Open the order business process. The step durations show where the time goes: adding line items takes over four minutes instead of one, and pricing and validating takes over two and a half instead of half a minute.
2

Rule out the technology

Check the errors and response times of those steps. If they stayed normal, the delay comes from the workflow itself, not from Siebel or its integrations.
Analysis of click response time in Order Entry - Line Items View, 1.161 seconds against 1.167 seconds the week before, flat on the Relationships chart

Response Time of the Order Line Items View - GermainUX

3

See where users wait or repeat

Open a slow order in Session Replay. The Business Process tab lists each step with its status and duration, so you can jump to the step where the user waited or repeated work.
Session Replay with the Business Process tab listing each step with its status, duration and timestamp

Business Process Steps in Session Replay - GermainUX

Simplify or automate the slowest step, then compare the process duration before and after the change.

Hear and Help Your Users

Analysis finds frictions after the fact. GermainUX can also hear from users while they work, help the ones who are stuck, and catch broken workflows before users meet them.

Let Users Share What They Feel

Make it easy and quick for users to tell you what they think. The GermainUX Feedback Popup appears inside Siebel, so a user can give a thumbs up or down, a rating or a short comment in a few seconds, without leaving their work or opening a ticket. Each response is linked to the user’s recorded session and their Siebel context: the screen, view and applet, the recent clicks, errors and business-process steps. Open the feedback in Session Replay to see what the user was doing and what they saw when they wrote it. Then group recurring comments with AI feedback analysis, so you act on the topics that come back most often.
Analysis of negative feedback from Siebel users on the day a new view is released, 27 responses against 6 the day before, peaking mid-morning

Negative Feedback on the Day of a Release - GermainUX

See User Feedback for Oracle Siebel CRM.

Engage Users Who Can’t Find What They Need

GermainUX detects, while it happens, that a user is stuck: repeated searches with no results, back-and-forth navigation between views, rage clicks, a negative feedback comment, or a conversation that doesn’t answer their question, picked up by sentiment analysis.
  1. Detect. Real-time monitoring and sentiment analysis flag the user who can’t find what they need.
  2. Alert. An alert tells your support team which user needs help, what they were trying to do, and links to the session.
  3. Respond. Your team reaches out to the user, through a notification or by email, and helps them finish the task.
Users get help before they give up on the task, use a workaround or open a ticket. See Proactive User Engagement.

Avoid Frictions with Synthetic Scenarios

Some frictions can be caught before any user meets them. A synthetic user scenario, recorded with the RPA Bot Recorder, runs a key Siebel workflow on a schedule, such as signing in, searching for an account and creating a Service Request. GermainUX alerts you when a step fails or slows down. Add HTTP checks for the web services and integrations behind the workflow.

Prioritize and Act

Each finding can start a response:
  • Adoption reports that deliver adoption trends, frictions and lost time to application owners and managers every week or month
  • SLAs on adoption, friction and process-duration KPIs, so a new or growing problem raises an alert
  • The AI Advice dashboard as the team’s shared list of improvements, ranked by estimated gain
  • Alerts by email, SMS, Microsoft Teams or Slack, routed to the team that owns the fix

Set It Up

Each step adds value on its own. Start with user monitoring, then add the rest.
1

Record Siebel sessions

Deploy RUM JS in Siebel Open UI, then create the Siebel UX Monitoring Profile with Session Replay and the privacy settings you need. Add each user’s team and role with User Role Lookup, so the analysis can compare them.
2

Configure your processes

Configure business processes for the workflows that matter most to adoption, such as order creation or Service Request handling, with their expected duration.
3

Turn on the feedback popup

Enable the Feedback Popup in the Siebel UX Monitoring Profile, and decide who reviews and responds to feedback.
4

Alert your support team

Create alerts on the frictions, negative feedback and sentiment that mean a user needs help, and send them to the channel your support team watches.
5

Test key workflows

Deploy the RPA Bot Recorder, then record a synthetic scenario for each critical workflow and run it from a GermainUX Engine.
6

Schedule the reports

Schedule adoption reports and the bulk session AI analysis for the teams that act on them.

Additional Resources

Adoption Insights

Measure and improve adoption

Oracle Siebel CRM

Users, processes, servers and more

Use Cases

More Use Cases

Get Help

Every Siebel deployment has its own applications, processes and user groups. The GermainUX team can help you choose the processes to monitor, set up the feedback popup and the support alerts, and record the synthetic scenarios for your key workflows.

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't Find What You Need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.