One company that never sees its customers online. One that automates everything. One that asks inside the apps it runs. The same two questions doing the work in all three.
We set up a quick NPS survey with a QR code, printed it and left it in every customer pack. It gave us immediate insights, crucial for enhancing the customer experience and keeping an eye on quality across the laundromats.
David D., Washr
Washr runs laundromats. A customer drops off a bag, picks it up clean, and leaves. No checkout, no account, no email address. Most survey tools start with "upload your list", and Washr doesn't have one. This is true for a huge part of the physical economy, and it's the gap the QR code closes.
One public survey link, printed as a QR code and left in the pack that comes back with every finished order. Downright generates the code itself: PNG for a sticker, SVG for a designer, a PDF ready to print. No app, no signup, no extra tool.
The customer scans it and rates the order in a single tap, usually while the laundry is still in their hands. The timing helps: nobody has to remember anything.
The open question after the score is where a branch learns that a machine keeps eating coins, or that the new opening hours are the reason people are happy. The score alone would never tell them that.
There is no script and no IP recorded on the survey page. An answer stays anonymous unless the customer leaves an address to get a reply, and only then do they become a contact.
We build forecasting tools, so we know the value of a signal you can act on. With a simple Make automation, Downright sends customer feedback surveys after the right events and brings every response into our workflow. The scores show us where we stand; the open-ended responses help us decide what to build next.
Mattia D., Predictabl
Predictabl builds forecasting tools. Mattia wired customer feedback into the product the way he wires everything else: two Make.com automations, no code written, no dashboard anyone has to remember to check.
When something worth asking about happens in their product, a Make scenario tells Downright to survey that customer. The survey arrives while the experience is fresh, which is a big part of why people answer it.
The moment somebody answers, Downright pushes it straight into the same automation: the score, the comment, and who wrote it. No exports, no checking a dashboard.
If the score is 6 or less, Make posts it to the Slack channel the team is already watching, comment included. Someone can follow up the same day, while it still matters to the customer.
The scores tell Predictabl where they stand. The open answers tell them what to build next, in the words of the people who will use it.
The plumbing behind this is one webhook and two Make scenarios. The technical details live in the API reference.
I run Downright inside the apps I look after. A WebView opens the survey, the score is one tap, and the app closes it the moment it reaches the done URL. No SDK, no interruption, nothing for the customer to install or dismiss. The open answers are what the product teams actually use.
John S., Fractional CMO
John is a fractional CMO, and the customers of the apps he looks after are never on a website and never in an inbox: they are in the app. So the survey goes there too, and it goes there quietly. The same two questions, opened inside the app itself, answered without anyone being sent to a browser, and without anything that feels like an ad.
A WebView loads the survey link with nothing else around it: no header, no footer, no SDK to add, no popup fighting the app. Just the question and the scale, in the app's own skin, at the moment the app chooses.
The score is one tap. The open question follows, and the answer is written right after the thing it is about, which is when people actually say something.
When the survey finishes it navigates to a known done URL. The app watches for it, closes the panel, and has the score in hand if it wants to do something with it. Nobody dismisses anything.
Same rule as everywhere else: no script, no IP recorded, and an answer stays anonymous unless the person leaves an address to get a reply.
The same embed works on a web page, where it sizes itself. Both recipes are on the integrations page.
Washr asks on paper, Predictabl asks by API, John's clients ask inside their apps, and none of them pays extra for the privilege: every channel is on every plan, so the choice is only ever about where your customers are.
One public URL anyone can answer, on a receipt, a door, a machine. The QR comes straight out of the dashboard as PNG, SVG or a printable PDF. That is the whole Washr story.
Your system decides who gets asked, and when. One call per person, fired by whatever event means "this customer has just experienced us".
Paste a list or upload a CSV; Downright sends it and throttles it, so no one is asked twice in a quarter however many surveys you run.
The scale sits inside your own page or app, and the answer is recorded without the customer going anywhere.
Free plan, no credit card. The API and webhooks are on it too.