Survey tools collect responses you never read.
Most survey tools end at the dashboard. The responses pile up in their own silo, in their own format, with their own analytics — separate from every other piece of customer feedback you have. So they don’t influence the roadmap; they generate reports.
Circuit’s surveys land in the same pipeline as Slack, transcripts, support tickets and the rest. An NPS detractor’s free-text comment doesn’t sit in a survey dashboard — it clusters with a Slack thread complaining about the same thing, and the resulting priority shows both the NPS score and the Slack quote. A cadence engine makes sure you don’t burn out your audience asking too often.
From a single API key to live responses.
Five formats and four templates, configured in three steps.
Bubble (corner FAB), Embed (inline), Banner (top or bottom bar), Thumbs (minimal up/down), or Trigger (full-screen modal). Each format suits a different surface.
Open-ended, NPS, CES or PMF. Each ships with a recommended question, scale and cadence — customisable per template.
One API key per account. Embed the snippet anywhere, attach the per-surface ID, done. Responses start landing right away.
Each response is clustered, scored and tied to its customer — and shows up on your priority list, not in a separate dashboard.
A cadence engine that protects your customers from you.
The hardest part of running surveys at scale isn’t sending them — it’s not sending them too often. Circuit’s cadence engine has six rules, with smart defaults per template, that make sure each customer is asked at the right moment.
Minimum days since signup, cool-down after response, wait after dismissal, wait after silent impression, lifetime ask cap, and cross-survey quiet period. Each tuned per template.
Showing one Circuit survey silences every other Circuit survey for that customer for a set window. No customer ever sees two of yours in a week.
Survey answers don’t sit in their own analytics. They cluster with Slack, transcripts, CSV imports and Reddit — under the same themes, ranked the same way.
How the cadence engine decides who to show what.
Six rules combine into a single decision: is this person ready for this survey? Each rule can be tuned; each template ships with a sensible default. Default cadences ship per template; one button resets your rules to the template defaults if you want to start over.
Don’t ask people who just signed up. PMF defaults to 30 days; NPS to 14; CES to 0 (event-driven).
Don’t ask again right after someone answered. NPS defaults to 90 days.
If someone closed the survey, don’t pop it back. NPS waits 30 days.
If someone saw the survey but didn’t interact, give them space. NPS waits 7 days.
A maximum number of times the same person ever sees this survey. NPS caps at 8.
After any Circuit survey, all surveys go quiet for this customer for N days. PMF defaults to 30.
Everything in the survey kit.
Bubble, Embed, Banner, Thumbs, Trigger. Match the format to the surface.
Open-ended, NPS, CES, PMF. Each with a recommended question, scale and cadence.
Ink, Clay, Greige, Forest — or a custom hex. Auto-contrast keeps text readable on any background.
Match the survey to the customer’s system preference, or pin it.
Toggle per survey — show what’s useful for the question you’re asking, hide what isn’t.
Send via email, in-widget, or both. Sender identity (name, logo, accent colour, footer) configurable per surface.
One key per account, displayed once at creation. Server-side hashed, never stored in plaintext.
NPS in 11 buckets, CES in 5, PMF in 4. The right view for the question you asked.
Asked and answered.
Standalone tools end at the dashboard. Circuit’s surveys land in the same ranked pipeline as every other customer signal — Slack, transcripts, CSV imports, Reddit. An NPS detractor’s comment clusters with a Slack thread saying the same thing, and the resulting priority shows both. The response shapes the roadmap, not a separate report.
Most survey tools let you over-ask. The cadence engine has six rules — minimum maturity, cool-downs after response, dismissal or impression, lifetime cap, and a cross-survey quiet period — so you don’t burn out your audience.
Four: Open-ended (5-emoji sentiment), NPS (0–10), CES (1–5 effort), and PMF (the Sean Ellis four-point scale). Each ships with recommended cadence and customisable copy.
Five: Bubble (corner FAB), Embed (inline DOM), Banner (top or bottom bar), Thumbs (minimal up/down), Trigger (full-screen modal). Different formats suit different surfaces; pick what fits.
One snippet, paste anywhere. Generate an API key once per account, drop the script tag on your page, attach a per-surface ID. Inline and Thumbs formats also need a DOM placeholder.
Yes — notifications can be in-email, in-widget, or both. Sender identity (company name, logo, accent colour, footer) is configurable per surface.