Get Started with Lens

Outcome

You will move from “Lens is available” to “we submitted and reviewed our first feedback item inside TMXIO.” This page walks a team through the first end-to-end loop: pick the site and environment, confirm the widget is reachable, submit one real piece of feedback, and review it from the TMXIO inbox.

Where you are

This page covers the TMXIO side of Lens: the inbox, list view, and item detail. The companion guide Lens for WordPress covers installing and configuring the widget on the site itself. If the widget is not yet installed, start there first.

Prerequisites

Before you start, make sure each of the following is true. Skipping any of them will make the first loop harder than it needs to be.

• A site is available in TMXIO and you have at least reviewer-level access.
• You know which environment you intend to review (production, staging, or a preview environment).
• Lens is enabled in TMXIO for that specific site and environment.
• The Lens widget is reachable on the site itself. If you are unsure, the Lens for WordPress guide explains how to verify the install.
• At least one reviewer has the URL they intend to leave feedback against.

The First Loop

The four steps below are the minimum path from “we turned Lens on” to “we acted on a real piece of feedback.” Run them once with a real reviewer rather than treating it as a tour; the goal is to confirm the loop works for your team, not to read about it.

1. Pick the site and environment.

   Open the correct site in TMXIO. Confirm the environment in the dashboard header before doing anything else. Lens behavior is environment-specific, so the environment choice changes which feedback you will see and where new items will land. If the team is reviewing staging, switch to staging now. If you are reviewing production, switch to production. Do not assume the default is correct.

2. Confirm the widget is available.

   Before inviting reviewers, load the site in the environment you selected and confirm the Lens widget is present and responsive. If the widget is missing, see Environment behavior and Lens settings in TMXIO. A common failure here is having Lens enabled in TMXIO but not aligned with the site-side install for the environment under review.

3. Submit the first feedback item.

   Create the first feedback item from the actual site experience you are reviewing. Pick something real: a copy issue, a visual bug, a question about an interaction. Avoid placeholder test items, because they make the rest of the loop harder to evaluate. Once submitted, return to TMXIO and confirm the item appears in the Lens list view for the same environment.

4. Review it in TMXIO.

   Open the new item from the Lens inbox. Confirm the page context, screenshot, and metadata look right. Decide whether the item should stay open, move into review, or be escalated to support. Add a comment that names the next action, even if the action is “no change needed.” See Review and triage feedback for the recurring pattern your team will use after this first loop.

What Success Looks Like

When the first loop is complete you should be able to answer all of the following without checking:

• The environment under review is the one your team intended.
• A real feedback item is visible in the TMXIO Lens inbox.
• That item has a clear next action recorded as a comment or status change.
• The team has a shared idea of how the next ten items will flow through the same path.

If any of these are still ambiguous, run the loop one more time with a different reviewer before scaling up.

Where to Go Next

Review and triage feedback Build a repeatable triage rhythm once items start arriving.

Manage a feedback item Work a single item from submission through closure.

Lens status workflow Keep the queue readable with consistent statuses.

Environment behavior Understand why environment isolation matters.