Feedback your coding agent can act on.

Your users click what is wrong. Loopback takes the screenshot, lets them draw on it, files the issue in your tracker, and keeps the conversation in your app until it is fixed.

Request access Sign in

Northwind Billing

InvoicesInvoice 2041

Design retainer, September: €1,200.00
Early payment discount, 10%: −€120.00
VAT 25.5%: €275.40
Total due: €1,475.40

Download PDFPay now

Report something

The total still charges the full amount. I applied the 10% discount and it shows in the list, but not in the total.

Screenshot, with your markSend

Issue #113 opened in northwind/billing
Open
Picture, the element, the page and the browser, in the issue body.
Your coding agent replied to the reporter
In progress
"The discount was applied after VAT. Fix is in #118. Does the total look right now?"
Back in the app, the reporter sees
You have a reply1

One loop, from the click to the fix.

The user clicks the broken partLoopback takes a screenshot, and they draw on it to show what is wrong.
An issue opens in your trackerThe screenshot, the page and the browser details go in with it.
Your agent picks it upWhatever coding agent you already use can work the issue. So can a developer.
The user gets the reply in your appQuestions and answers go back and forth in the widget, right where they reported it.

Everything around the request.

You see the screenshot with the user's drawing on it.
You know the page, the element, the browser, who reported it and when.
The whole history is in one timeline, and every entry is copied to the tracker.
Need more? Ask from the item, and the user answers in the widget.

Built for your coding agent.

It picks the issue up from the tracker it already works in.
It can ask the user a question through Loopback and get the answer back the same way.
When the fix ships, it marks the item ready for the user to check.

northwind/billing · Issue #113

Total ignores the discount

Reporter: The total still charges the full amount. I applied the 10% discount and it shows in the list, but not in the total.

Element: dd.invoice-total, on /invoices/2041

Browser: Safari 26, iPhone, 390×844

Picture: attached, with the reporter's mark

Your coding agent · through Loopback, to the reporter

I can reproduce it: the discount is subtracted after VAT is added. Before I change it, was the discount applied before or after you added the VAT line?

Anna Virtanen · from the widget

Before. The discount was already there when I added VAT.

Your coding agent · through Loopback, to the reporter

Thanks. Fixed in #118, the total now reads €1,355.40. Marking it ready for you to check.

Next up: the interview.

Loopback's own agent will ask the follow-up questions right after the report, while the user still has the page open.
In development.

Your tracker, your agent, a thin widget.

Your tracker is the record.: Issues, comments and the closing pull request stay in GitHub. There is nothing to migrate onto.
Bring the agent you already use.: The loop runs on plain issue comments and one small API.
A widget, not a suite.: One button on your app and one inbox for the team. No portal, no help desk.

Put a feedback button on your app that your agent can answer.

One script tag in your app, one repository to file into.

Request access Sign in