Public reviews and marketplace ratings
Business listings, app store reviews and marketplace seller ratings, including the star rating, date, branch and any reply already posted.
Gather
Every review, survey answer, ticket and mention in one stream.
Connect the places customers already talk to you. Kingsclap pulls comments in on a schedule, removes duplicates, tags each one with its source, location and product, and keeps the original text so every number can be traced back.
- Public reviews Syncing1,284
- Marketplace ratings Syncing736
- NPS and CSAT surveys Syncing562
- Helpdesk tickets Syncing917
- Chat transcripts Syncing403
- Social mentions Syncing348
- CSV imports Syncing120
- API and webhook Syncing64
One stream, de-duplicated4,434
Feedback Collection
What it covers
Surveys
NPS, CSAT and post-visit surveys. Scores and free-text answers stay linked, so a 3 comes with its reason.
Helpdesk and chat
Ticket subjects, first customer messages and chat transcripts. Agent replies are kept out of the analysis.
Social mentions
Brand mentions and comments on your own posts, filtered for spam and giveaway noise.
CSV and spreadsheet import
Upload historic exports to get a baseline on day one. Map columns once and reuse the mapping.
API and webhook
Send comments from your own app, kiosk, WhatsApp flows or in-store tablets. Each record needs only text and a timestamp; everything else is optional metadata.
Workflow
What happens to a comment on the way in
- 01
Pulled or pushed
Connectors sync on a schedule. Imports and webhooks arrive as they happen.
- 02
Cleaned
Exact and near-duplicate comments are merged. Spam, empty ratings and bot text are set aside, not deleted.
- 03
Tagged
Source, date, rating, location, product and channel are attached from the metadata you provide.
- 04
Redacted
Phone numbers, emails, order IDs and card fragments are masked before analysis.
In detail
Metadata that makes comparison possible
Location
Branch, city or region. Mapped from listing IDs, store codes or a column in your import.
Product or service
SKU, category or menu item, when the source provides it.
Team
Shift, counter, delivery partner or support queue.
Time
Original posting time, not import time, so trends reflect when customers spoke.
FAQ
Questions teams ask
How far back can we import?
As far back as your exports go. Most teams load 12 months of history so trends and seasonality are visible from the first week.
Do we need all sources connected to start?
No. Many teams begin with reviews and one survey, then add helpdesk data once they have seen the first fix-first list.
What if a source has no connector?
Use a scheduled CSV import or the webhook. Anything that produces text and a date can be brought in.
Is anything written back to the source?
Only approved review replies, and only where the source allows replies through its official channel. Nothing else is written back.
Insight Engine
Works together with
Next step
Your fix-first list is already sitting in last month’s feedback.
Send us an export of reviews, survey answers or tickets. On the demo we sort it live and show you what we would fix first, with the comments behind every theme.