Surveys
Three questions by phone, with the answer already structured.
A questionnaire emailed after a delivery has a response rate everybody knows and nobody says out loud. A short call, made at the right moment, with three questions, has a different rate. It also has a different risk, and this page states that just as plainly.
The assistant dials from a list you supply, asks the questions in the order written, records each answer as structured output with the same values, and ends the moment somebody says they do not want to take part. It does not persist and offers nothing in return.
When a call beats a form
It is worth it when the timing matters and the answer is short. It is not worth it for a twenty-question survey, which should not exist by email either.
After a delivery
Did it arrive, in what condition, how satisfied. Three questions, under a minute.
After a call-out
Was it fixed, did they arrive on time, would you recommend. Dialled the next day, not the next week.
A recommendation score
A number and a reason. The reason is the useful part, and on the phone people actually give it.
Checking a closed complaint
Whether the problem is really resolved, which the ticketing system does not know.
Updating details
A short call confirming contact details, which is the least intrusive survey there is.
How a short survey is run
A good telephone survey is short, asks the questions in the same order every time, and stops at the first sign the person does not want to take part.
- 01 Upload the list and the timing The contacts and, ideally, the date of the event being asked about. Extra columns become variables usable in the questions.
- 02 Say who is calling and how long it takes The company, the reason and the real duration, in the first sentence. A false duration estimate is the fastest way to lose the answer.
- 03 Ask the questions in order The same ones every time, with the answers in a structured output. Consistency is the only thing that makes the data comparable.
- 04 Stop at the first refusal No means no. The contact is marked, and the suppression applies to later campaigns too.
- 05 Write the results Into a sheet or your system, with the answers in fields rather than as free text somebody has to read.
What comes out at the end
A survey whose output is a list of transcripts is not a survey, it is deferred work. Here the answers come out in fields.
| The answers | As structured output, with the same fields and the same possible values across every call. |
|---|---|
| In the results sheet | One row per contact in Google Sheets or Airtable, ready to aggregate. |
| The refusals | Marked explicitly, so they do not reach the next list. |
| The reasons for the ones not dialled | From the campaign fixed values, so you know what base the result was built from. |
What it does not do, and where it goes wrong
A badly run automated survey does not just produce bad data, it produces people annoyed at the company that called them.
- It does not persist or persuade It does not rephrase a question somebody declined and does not try again in the same call.
- It offers no incentives It promises no discounts and no prize draws. A survey paid for with something no longer measures what you thought it measured.
- It guarantees no representativeness It dials the list you give it. Whoever answers a phone is not a sample, and we do not pretend otherwise.
- It does not analyse sentiment It records what the person said, in the values you defined. It infers no emotional state from a voice.
- It does not take over the basis for the call The right to call somebody for a survey is yours, as are the hour and the frequency. The product gives you the window, the suppressions and the written trail.
What people ask about surveys
How many questions are too many?
Three is good, five is the limit, and beyond that the drop-off rises quickly. If you need ten questions, the call is not the right channel, and a form sent by SMS after the call works better for the rest.
Do people answer an automated system?
Some do, especially immediately after a concrete event they have an opinion about. We have no figures of our own comparing it to a human interviewer and we are not inventing any, because that is exactly the kind of number a vendor who measured nothing would publish.
What happens if somebody says not to call them?
They are marked and enter the suppression list, which applies to every later campaign rather than only this one. The assistant confirms briefly and ends, asking nothing further.
Can it call a set interval after the event?
Yes, if the list carries the event date. The campaign is built over the list you upload, and the right moment matters more than the wording of the questions does.
Where to go next
Outbound campaign
Contacts, pacing, window, compliance, start, report.
Developers
A REST surface with OpenAPI, webhooks, MCP, and a tenant boundary enforced in several places.
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. - 2 Structured output is what makes answers comparable across calls. The suppression list applies at organisation level, not only to the current campaign.