Integrations
Put every customer answer where your team already works.
Every answer can reach the people who act on it. Survizo writes each member's answers and scores to their contact in your CRM, so the people who talk to that customer see what they said. Your other systems can pull results whenever they need them, and get an alert the moment a member finishes a survey. Invitations go by email, or from your own WhatsApp Business number to people who have opted in.
A worked example
See where one completed response goes.
A member finishes a three-question survey. Here is what lands on that customer's contact in your CRM, and what your other systems are told the moment it happens. The answers are made up, and every code and column name is exactly what Survizo uses.
What goes in
| Question and its code | Answer |
|---|---|
| NPS How likely are you to recommend us to a friend? | 9 |
| CSAT How satisfied were you with your last delivery? | 4 of 5 |
| REASON What is the main reason for your score? | It came a day early. |
Give each question a short code, like NPS, and that code follows its answers everywhere. Leave one out and Survizo codes it by position, as Q1, Q2 and so on.
What your other systems are told
| Part | What it carries |
|---|---|
| What happened | response.completed |
| Delivery number | One id for this response, the same on every attempt |
| Signature | A signature that proves the message came from Survizo |
| Contents | The ids of the response, the survey and the person who answered, the time it was submitted, and every answer |
| Each answer | Its question code and type, the value, the option label and a number where there is one |
The contact record in your CRM
| Column | Value |
|---|---|
| Survizo NPS | 9 |
| Survizo NPS (previous) | The score it replaced |
| Survizo NPS recorded | When this was submitted |
| Survizo CSAT | 4 |
Survizo also keeps the full response in your CRM, with each of the three answers saved under its code, NPS, CSAT or REASON.
Developer API
Your other systems can pull surveys, answers and member details on their own.
Your developers will find every detail on the developer page, with a place to try each request on your own community. Your key stays inside that page and is forgotten when you leave.
What your systems can read
Surveys arrive with their questions, codes, option labels and scales. Each answer arrives under its question's short code, the same code your Excel and SPSS files use. Members arrive with their details and the segments they belong to, and your systems can ask for any member's latest NPS, CSAT and intent scores. They can also ask Survizo to refresh a segment first, so the member list they get back is up to date.
Results arrive in batches of up to 200. Give a start time and your systems get back only newer responses or members, so a nightly update stays small and quick.
- Answers by question code
- Surveys, members, segments
- Batches of up to 200
Keys that open one community, and only what you tick
Each key works for one community, and when you create it you tick exactly what it may do. There are six choices: read responses, read members, read surveys, read segments, manage webhooks and invite people. You see the full key once. We keep only a scrambled fingerprint of it, so nobody, our team included, can read it back. If a key is lost, you switch it off and make a new one.
The key decides which community your systems can see. Ask with it for another community's records and Survizo answers as if they do not exist.
- One community per key
- Six permissions you choose
- Shown once, never kept readable
Swap keys without interrupting anything
A new key can expire after 90 days, after one year, or never, which is the default. The key list shows each expiry and flags keys that have lapsed or will lapse within a fortnight. Rotate replaces a key in one action. It makes the new key, moves the old key's webhooks across and only then switches the old one off, so your systems miss nothing.
Each key can make 120 requests a minute and each community 240, so an old key and its replacement both run at full speed during a switch. A system that asks too fast is told how many seconds to wait.
- 90 days, one year or never
- 120 a minute per key
- 240 a minute per community
Invite people straight from your CRM or booking system
Your CRM or booking system can add people to the community with the details it already holds, such as a loyalty tier or a city. You can use those details to choose who gets a survey, and only your team sees them, never other members. Each person gets the community's branded invitation email, a WhatsApp message from your own number if they opted in, or both. Anyone who has unsubscribed or opted out is skipped. Your systems can also send a survey to named members or a whole segment, by email, on WhatsApp or both.
Built-in limits stop a mistake in another system from flooding your members. Each request can add up to 500 people, and nobody gets more than one invitation email, or WhatsApp message, in 24 hours. Your systems can send up to 5,000 invitation emails a day, and as many WhatsApp messages. Past that, people are still added to the member list, ready to invite from there.
- 500 people per request
- One message per person per 24 hours
- 5,000 a day on each channel
Webhooks
Your systems hear the moment something happens.
Choose the moments your systems hear about
Add a webhook from the Developer API page in Survizo, or from your own systems, and choose what it should hear about. It can hear about a completed response with all its answers, a member joining or leaving, a change in a segment's membership, and a poll closing. One webhook can take several events.
A webhook can only send what its key is allowed to read. One that receives answers needs a key that can read responses. News of a member joining or leaving includes their email address, so it needs a key that can read members.
- Several events per webhook
- Answers in the event
- Sends only what its key may read
Deliveries you can verify, retry and inspect
Each webhook has its own signing secret, shown once when you add it. Every message is signed with that secret, so your systems can prove it came from Survizo before acting on it.
If a delivery meets a server error or a failed connection, Survizo tries twice more, after half a second and after two seconds. Every attempt keeps the same delivery id, so your system can skip a repeat. If your system refuses a message, Survizo takes that as final and does not send it again. Survizo sends only to the secure public address you enter, never anywhere it redirects, so answers go nowhere you did not choose.
The Developer API page lists each webhook's last twenty attempts, with the time, the event and the reply. A Test button sends one straight away, so you can check your system is listening before real answers arrive.
- HMAC-SHA256 signature
- Up to three attempts
- Last 20 attempts listed
Your CRM
Answers and scores reach the contact your team already uses.
The CRM connection runs on Microsoft Dynamics 365: a community owner connects the environment once. From then on, Survizo writes to it each time a member completes a survey. It updates the contacts you already have, and lists any member with no matching contact so you can check them. Turn on one switch and your saved segments appear in your CRM, ready for its marketing journeys and refreshed every fifteen minutes. A log shows what each update did, and disconnecting stops the updates and deletes the stored connection secret.
Connect
In Survizo, the community owner starts the connection, and whoever administers your CRM signs in with their own work account. Survizo then sets itself up in the CRM they pick, with only the access it needs and never full administrator rights. Your administrator can also set it up by hand from the set-up guide.
Survizo makes room for your answers
On first connection, Survizo creates four tables of its own, for surveys, responses, answers and segment membership. It adds score fields to your contacts and shows you each step as it goes.
Choose the match and the scores
Match members to contacts by email address, or by a loyalty number column you name. Choose whether NPS, CSAT and intent are written to the contact. Questions coded NPS, CSAT or INTENT are picked up automatically, and you can add codes of your own.
Answers flow in, and your history catches up
Each response reaches your CRM the moment a member finishes, with every answer saved on its own. Press Sync now and Survizo adds all your earlier responses in the background. You can run it again at any time without creating duplicates.
Reach members on WhatsApp, from your own number.
Your own number, and it stays yours
Connect your community's own WhatsApp Business number and send invitations by email, on WhatsApp, or both. Your connected systems can announce a new study the same way. The number and the account stay yours, and you pay WhatsApp's charges directly.
You connect the number from the WhatsApp page in Survizo, with a set-up guide to walk you through it. WhatsApp approves each message wording before it is used, and you see in Survizo whether every message was delivered and read.
- Your own Business number
- You pay WhatsApp directly
- Messages approved by WhatsApp
Messages go only to people who said yes
Before you send on WhatsApp, you tick a box to confirm these people agreed to hear from your business there. Survizo then skips anyone without a number or an opt-in on record, and anyone who has opted out. It also skips anyone messaged in the last 24 hours, and stops once the day's WhatsApp allowance is used. Either way, it tells you who was skipped and why. Each message shows as queued, sent, delivered, read or failed.
- Opt-in confirmed
- 24 hours between messages
- Delivered and read status
At a glance
Everything that connects, at a glance.
A key per community
Choose what each key may do. Shown once, it can expire after 90 days or a year.
Answers by question code
One set of codes across your exports, the API, the webhooks and your CRM.
Signed webhooks
New responses, members, segment changes and closed polls reach your systems as they happen.
Invitations from your systems
Your systems invite people by email and WhatsApp, with limits so nobody is flooded.
Your CRM
Answers and scores land on the matching contact, and unmatched members are listed for you.
WhatsApp outreach
Your own number, opted-in members, and the status of every message.
Next up
Where to go from here.
Analysis and exports
Numbers you can stand behind, in files that match what you saw.
See how many people stand behind every chart, compare groups of members, and send PowerPoint, Excel and SPSS files that match the screen exactly.
Analysis and exportsSecurity and privacy
Know where your members' data lives, and who can reach it.
See where your members' data lives, who can reach it and how every support visit is logged. Hosted in the US, with 35 days of database backups.
Security and privacyThe next step
Book a fit call.
Thirty minutes with the people who build Survizo. Bring a study you have coming up. You'll leave knowing whether Survizo fits it and how soon you could launch.