Get the Broken Visits on Your Website Ranked for You

If your website records visits, a muse can sort the broken ones for you. It reads the problems a recording tool has already spotted, ranks them by severity and how many visits each hurt, and hands you the short list worth watching first.

What it does

Recording tools catch the moments a visit goes wrong: a button clicked again and again, a script error, a click that does nothing, a page people leave halfway through. Nobody has time to watch hundreds of recordings. A muse can do the sorting. Connected to the tool, it pulls the open problems, ranks them by severity and visits touched, and reads the details: what happened, the steps leading up to it, your team's notes, and which recording shows it best. The muse reads a written summary of each recording, not the recording itself, so it picks what you watch. You still watch it. The muse prepares, you decide.

How to use it

1. Ask the muse to build a connector for your recording tool from its public instructions, and say in that first message: read-only, never change a problem's status.
2. Paste the workspace token into the secure credential box the muse shows you, never into the chat.
3. Ask the muse to list the websites it can see, then name the site to check.
4. Ask for that site's open problems, worst first, with the hurt visit count next to each.
5. Watch the recordings the muse names for the top few before you change anything.

What you need

• A website with a session recording tool installed
• A paid plan on that tool with a free trial, so you can test before paying
• A workspace token from the tool, for the secure credential box only
• A muse account that can build custom connectors

What to watch for

• Keep the connector read-only at the start. The one status-changing tool can mark something fixed when nobody has looked at it, and a closed problem leaves the morning list while the page stays broken. Allow a change once, only after watching its recording.
• The muse cannot see what the page looked like. It cannot tell you a button looked grayed out or where a visitor hesitated. Only the recording has that.
• Some problems arrive with no recording attached. The muse should report those instead of pointing you at a nearby one.
• Visitor records can carry a name and email address if your site identifies visitors. Decide whether the muse should hold that before creating the token.