Features
Ask the customer right after it happens
When your own system finishes an operation, it asks Hivenza for a personal link to your survey, and sends it the way you already contact customers. Every answer is tied to the operation, the branch and the person who served.
Get startedNeeds a plan with the API. Hivenza sends nothing itself.
From an operation to a result by team
- 1
An operation finishes
A withdrawal, a consultation, a repair, a delivery: your system knows what happened and who handled it.
- 2
It asks for a link
Your server asks Hivenza for a personal link to the survey, with the details of the operation attached.
- 3
You send it
Your own email, text message or receipt carries the link. Hivenza sends nothing to the customer.
- 4
Read the results
See averages by staff member, team and branch, and follow up on low scores.
What you get
For banks, telecoms, clinics, retailers, agencies and any team whose own system knows what just happened.
- You stay in charge of contact
- The customer hears from you, through your own channels. Hivenza only makes the link.
- Details stay private
- What your system sends about the operation is kept on Hivenza’s server. The customer’s page never shows it, unless you decide to show one detail, such as “You were served by Aïcha”.
- Results that mean something
- Averages by staff member, team and branch, with their trend over time.
- Fair to the people served
- A person’s average appears only once they have at least five answers. Written comments about a person stay hidden until someone who builds forms approves them.
- Its own permission
- Results by staff are about people at work, so they have their own permission, given to administrators by default.
- A low score acts
- A low score can alert a supervisor and open one ticket that names the operation.
- Safe by design
- The link is a signed token that holds no name or number, expires, and can be withdrawn. Requests are made from your server only, and every call is recorded.
- Signed webhooks
- Hivenza tells your system when a survey is answered, with a signature you can check, so you can follow up.
- Safe to retry
- Asking again for the same operation returns the same link, so a timeout never sends two.
- Tidied afterwards
- Invitations that were never answered are deleted 30 days after they expire. The answer keeps its context for as long as you keep the answer.
Needs a plan with the API
Your developers use a secret API key limited to this one job. The step-by-step developer guide has the request, the signature check and examples in curl, Node and Java.
Questions
Does Hivenza email or text my customers?
No. Hivenza makes the link and your system sends it, or prints it on a receipt.
Can the customer see who served them?
Only if you choose to show it. By default, nothing about the operation is shown to the customer.
Why are results hidden below five answers?
One or two answers would single a person out. Their average appears once there are at least five.
What does my developer need?
A secret API key, the survey’s id and the developer guide. There is no ready-made library: the guide and the reference are the kit.
Goes well with
- Developer guide: surveys after an operation
- Forms and surveys
- Workflows
- Campaigns
- AI knowledge
- AI procedures
- AI quality
- Routing and supervision
- WhatsApp calls
- CRM sync
- Known issues and case status
- Reporting and API
- Content library
- Website analytics
- Reviews
- Employee advocacy
- Paid ads
- Listening
- Analytics and reports
- Plan and publish
- Links and link in bio
- Ticket processes
- Website surveys
- Customer portal
- Ticket apps
- AI memory
- Configuration sandbox
- Staffing forecasts
- Send a form to a group
- The shared inbox
- Webhooks: Zapier, Make, n8n
Hear from every customer right after it happens
