Panel 1 — Cancellation Request & Reason: The customer asks to cancel "The Multi-managed Snowboard...Panel 1 — Cancellation Request & Reason: The customer asks to cancel "The Multi-managed Snowboard...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Panel 1 — Cancellation Request & Reason: The customer asks to cancel "The Multi-managed Snowboard" from order #1065, giving "changed my mind" as their initial context. The AI correctly identifies the order and item, then asks for a reason before proceeding — the customer replies "It's expensive." The panel is cut off mid-response, but it's already showing "requires human approval since..." starting to appear.
Panel 2 — Identity Verified & Escalated: The AI states cancelling the item requires human approval because the refund amount of $610.06 exceeds the auto-approve limit, and asks for the email used on the order. The customer provides it (Russel.winfield@example.com), and the AI correctly confirms that even after identity verification, this still requires human approval due to the dollar amount, and says it will forward the request to the team.
Icon cards for me, bouquets are such a visual purchase that a scannable icon beats reading "small/medium/large" every time. Did the compact chips version convert worse in testing, or are you still gathering data on that?
Niva - AI Automation Agency Template (Contact page)
📌 What's Included
13+ fully designed pages, covering the entire buyer journey:
Home — hero, problem/solution framing, services, industries served, integrations, process, stats, case study previews, testimonials, pricing, FAQ, and final CTA
About — origin story, mission, values, team, and company stats
Services — a full breakdown of each service line with outcomes and use cases
Case Studies — a CMS-powered index plus a detailed single-case-study template (problem → approach → solution → results)
Blog — a CMS-powered index and article template, ready for SEO content
Contact — a conversion-focused form paired with direct calendar booking
404, and legal pages — Privacy Policy, Terms of Service, and Cookie Policy included
📌 Ideal For
AI automation agencies and consultancies
Workflow automation specialists and system integrators
Custom AI agent developers
AI strategy and operations consultants
Freelance automation experts positioning as a boutique agency
SaaS companies offering AI-powered services to B2B clients
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.