Feedback collection
Request business reviews, testimonials, and NPS through links and emails.
Bring customer feedback into view
Collect reviews, testimonials, and NPS with moderation and embeddable widgets.
Customers write at review.<domain>/write (stars, title, text, name, optional role and company, consent to publish) or answer an NPS survey (0 to 10 with a follow-up question), from QR codes, personal links at /r/<token> or request emails sent by a cron with one reminder; Payments, Meetings and websites ask through POST /api/v1/requests, and customer lists come in by CSV. Low ratings, NPS answers and reviews without consent go to private feedback for the team; happy customers see a button to review the business on Google. The moderation inbox publishes, hides, features, tags and replies, with profanity checks in English and Hindi, spam and duplicate checks and email alerts. Approved reviews appear on a brand-styled wall at /reviews with AggregateRating markup and in /embed.js widgets (carousel, grid, badge, testimonial) in Shadow DOM. Insights show the average rating, the NPS and themes; Claude drafts replies in the brand voice, summarises themes and sentiment and picks verbatim highlights. Product reviews stay in Store. reviews.appneural.com holds every domain; review.<domain> holds one domain's reviews.
What Reviews does for you.
Request business reviews, testimonials, and NPS through links and emails.
Review incoming feedback before deciding how to present it.
Use a review wall and embeddable widgets.
A suggested path for Reviews. What you can do depends on your access in the app.
Choose the review or feedback request to share.
Work through the feedback in the moderation inbox.
Review the wall or widget used to display feedback.
Live host, inventory, governance, health checks, verification, dependencies and history.
Customers write at review.<domain>/write (stars, title, text, name, optional role and company, consent to publish) or answer an NPS survey (0 to 10 with a follow-up question), from QR codes, personal links at /r/<token> or request emails sent by a cron with one reminder; Payments, Meetings and websites ask through POST /api/v1/requests, and customer lists come in by CSV. Low ratings, NPS answers and reviews without consent go to private feedback for the team; happy customers see a button to review the business on Google. The moderation inbox publishes, hides, features, tags and replies, with profanity checks in English and Hindi, spam and duplicate checks and email alerts. Approved reviews appear on a brand-styled wall at /reviews with AggregateRating markup and in /embed.js widgets (carousel, grid, badge, testimonial) in Shadow DOM. Insights show the average rating, the NPS and themes; Claude drafts replies in the brand voice, summarises themes and sentiment and picks verbatim highlights. Product reviews stay in Store. reviews.appneural.com holds every domain; review.<domain> holds one domain's reviews.
Product reviews belong to Store; the customers asked belong to Customers and Contacts.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
reviews.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.