Receiving feedback is not the same as having permission to publish it.

That distinction shaped ReviewDesk, a customer feedback and testimonial system I designed and built at Noerong.

For a local business, the workflow starts after a completed job: request honest feedback, keep track of the response, and make the next step clear.

Three decisions shaped the experience:

1. Keep the customer journey focused. A branded page and private request link make it clear where to respond. Scheduled reminders stop after a response.

2. Separate feedback from public proof. Testimonial consent and administrator approval are distinct steps. Every rating receives the same public-review option, without filtering out unhappy customers.

3. Give the business a useful overview. The dashboard brings requests, responses, activity, and approval status together. Approved testimonials can appear on a public wall or an embeddable website widget.

I designed and developed the customer flow, dashboard, reminder worker, and widget using Python and FastAPI.

The loop shows the feedback page, business dashboard, and testimonial wall. All customer names, comments, and metrics are fictional demo data. The public demo sends no email and retains no visitor submissions.

The detail I care about most: permission is part of the product, not an afterthought.

Full case study: https://contra.com/p/mRRY2Pc6-review-desk-customer-feedback-and-testimonial-system

Creative work