Solutions · Surveys
Your customer's opinion, in their voice — not in checkboxes.
The Survey and Feedback template calls after the visit or the purchase, asks permission before asking anything, and turns a low score into a human follow-up before it turns into churn.

A scene from your day
Your customer visited a branch yesterday. Today their phone rings: a friendly voice asks for two minutes and asks about that visit in particular — not about services in general — because Basher looked up their latest interaction before dialing.
They gave a seven out of ten, and got a single honest question: what would make it a ten? The next name on the list said four, so their words were captured verbatim and their name was flagged for a priority human follow-up.
Inside the platform
How the number branches in the template
This is the template's own map: context pulled before the call, permission whose refusal is respected, and a recommendation question after which the follow-ups branch three ways by the score.
Ready to configure
What comes pre-wired
The conversation arrives ready and you can reshape any step yourself. Actions that touch your systems — a confirmed booking, a ticket, a record update — go live once that system is connected during onboarding. Every line here exists in the product, not in a marketing deck.
It knows what it is asking about
Before dialing, the template pulls the customer's latest interaction — a visit, a purchase or a support ticket — so the questions are about one specific experience, not generalities.
in the code: lookup_recent_interactionA no is respected the first time
It asks permission and says it takes two to three minutes — and whoever declines is thanked and the call ends: an explicit template rule against persistence.
in the code: intent: decline → endQuestions that adapt to the number
Nine and above is asked what they loved; sevens and eights, what is missing; and anyone below seven is listened to without defense or justification.
in the code: nps_branch · ×3The unhappy do not vanish into averages
Low satisfaction, complaint, churn risk, upsell opportunity, urgent issue — five ready flag reasons that raise the customer to a human follow-up at a set priority.
in the code: flag_for_followup · ×5The customer's words, kept verbatim
Every answer is recorded as question and answer — a rating, literal text or a choice — so the customer's opinion reaches you in their words, not in a summary of them.
in the code: rating · text · choice · nps
Platform pillars
What it stands on
Every template borrows its strength from the platform itself — meet each pillar up close.