Client Handoff: Streamlining UAT Without Forced Logins
Reducing friction during the User Acceptance Testing phase using falconer.js.
The final stretch of any web agency project is User Acceptance Testing (UAT). This is where the client reviews the staging environment and identifies final issues before the site goes live.
Agencies often disrupt this phase by adding friction. They ask the client to create an account on Jira, BugHerd, or Maker.io, or ask them to install a Chrome extension.
Why friction breaks feedback
A client just wants to click what looks broken and say, “Change this.” Forcing them to jump through authentication hoops creates resistance.
Rather than installing an extension or navigating to a secondary Trello board, the client will usually fall back to what is easiest: sending an unstructured email thread full of ambiguous complaints like “The homepage image is too big.”
Falconer.js
FeedbackFalcon’s client widget focuses on removing this friction.
By adding a single script tag—<script src="falconer.js"></script>—to the head of your staging site, the FeedbackFalcon widget appears for every visitor.
A client opens the staging URL, clicks the widget, highlights a visual element, and types their feedback. They do not need to install anything or log in.
The system handles attributing the feedback to the correct project and pushing the context back to the engineering team. It bridges the gap between the client and the developer.