Steady reviews, not in waves
The process does not depend on enthusiasm.
- Automatic triggering
- A steady volume
- No periodic campaigns
- No administrative work
Marketing and automation package
Review automation, requests sent at the right moment
Review invitations go out automatically after a delivery, after a completed job or after a request is closed, to the real customers in your database. The customer is directed to the public platform you use, and the record shows who was asked, when and with what result. No incentives and no text written in the customer’s name.
From $2,900 excl. VATone-time payment, no monthly subscription- Requests at the right moment
- Directed to the platforms
- Automatic exclusions
- No incentives
- A complete record
Requests at the right moment
Directed to the platforms
Automatic exclusions
In short
Review automation: requests sent at the right moment. Review invitations go out automatically after a delivery, after a completed job or after a request is closed, to the real customers in your database. Part of the Marketing and automation package. Permanent licence, installed on the company server and unlimited users.
Works together with: Satisfaction surveys, WhatsApp Business, Events and registrations.
The problem
The current situation, when reviews appear by chance
An online reputation is built from satisfied customers who get a request at the right moment. That moment passes quickly.
- Nobody asks for reviews consistently You ask for two weeks, after a marketing course, then you forget. The reputation is left to chance.
- The right moment is missed The customer is in the best mood right after a successful delivery, not three months later.
- Negative reviews are the only spontaneous ones Unhappy customers write of their own accord. The happy ones have to be asked.
- Nobody knows who was asked With no record, some customers get three requests and others none.
- The requests reach the wrong customers too A request sent to a customer with an open complaint produces exactly the opposite effect.
- The effort cannot be assessed With no data, you do not know how many requests produced how many reviews, and on which platform.
What the module does
What the review automation module contains
The module administers the review requests and their record, linked to the customers in the CRM.
01 / 06
Event triggers
The request goes out when it makes sense.
- After an order is delivered
- After a job is completed
- After a request is closed
- Configurable interval
02 / 06
Directed to the platforms
The customer lands where it matters to you.
- The public platforms you use
- Your own intermediate page
- Several options, for the customer to choose
- Configurable links
03 / 06
The record of the requests
Every invitation stays recorded.
- Who it was sent to and when
- The channel used
- Status: sent, opened
- History on the customer record
04 / 06
Exclusion rules
The request does not go out to just anyone.
- Customers with open requests
- Customers who refused communications
- A minimum interval between requests
- Your own exclusion lists
05 / 06
Your own texts
The message is the company’s.
- Templates per channel
- Personalised with customer data
- In the configured languages
- Revisable at any time
06 / 06
Reporting
The effort becomes measurable.
- Requests sent per period
- Open rate
- Comparison between periods
- Export for analysis
What changes
What changes in the first months after the reviews module is activated
Direct effects of the requests going out automatically, to the right customers.
The right customers, asked in time
The moment makes the difference.
- Right after the positive experience
- No cold requests
- No repeated requests
- No customers with open problems
A reputation that brings customers
Reviews influence the buying decision.
- A volume of recent reviews
- Presence on the relevant platforms
- An argument when quoting
- A long-term effect
A complete record
You know exactly what was asked.
- A history on the client
- Channel and date
- No overlaps
- Verifiable at any time
Marketing effort justified
The result can be reported.
- Requests and opens
- Comparison across periods
- By platform
- Export for analysis
Protecting the relationship
The requests do not annoy.
- A minimum interval between requests
- Automatic exclusions
- Unsubscribes respected
- Texts in the company tone
In the application
The path of a review request
The same flow for a product delivery and for a completed job.
- 1
The triggering event happens
An order delivered, a job completed or a request closed marks the moment when the customer has a fresh experience.
- 2
The exclusion rules are checked
Customers who refused communications, those with open requests and those contacted recently are skipped automatically.
- 3
The request goes out on the configured channel
The message is sent by e-mail or, if that module is active, on a messaging channel, respecting the platform rules.
- 4
The customer lands on the chosen platform
The link leads either straight to the public platform or to an intermediate page of your own, where the customer chooses where to write.
- 5
The request stays recorded
The customer record shows what was sent and when, so it is not repeated and does not overlap with other communications.
- 6
The result is tracked
The record shows how many requests went out and how many were opened. The review itself belongs to the customer and to the platform.
Video tour
Review automation, in short, inside the application
Coming soonThe video presentation of the module is being prepared.
Ethics
Rules we do not break
A reputation built through dubious methods collapses once, and for good.
01 / 04
We do not write reviews in customers’ names
The text is the customer’s.
- No texts prepared by us
- No reviews published automatically
- No artificially created accounts
- Only the invitation goes out from the system
02 / 04
No incentives for reviews
The platforms forbid the practice.
- No conditional reward
- No discounts for reviews
- In line with the platforms’ rules
- The risk of a penalty avoided
03 / 04
We do not filter out unhappy customers by blocking them
The difference matters.
- We do not stop anyone from reaching the platform
- The exclusions are about the customer relationship
- Complaints are handled in support
- Transparency towards the platforms
04 / 04
Unsubscribes are respected
Whoever does not want communications does not receive them.
- An option in every message
- Respected by every module
- Recorded on the record
- Verifiable
Exclusions
Who does not get a review request
This list protects the customer relationship more than any well-written text.
- Customers with open requests A customer waiting for a problem to be solved does not receive a review invitation. It would be counterproductive.
- Those who refused communications The unsubscribe option is respected in every module, this one included.
- Those contacted recently A minimum interval between requests is configured, so that the same customer is not asked twice in the same month.
- Customers anonymised on request People who asked for their data to be deleted are excluded automatically from any communication.
- Your own exclusion lists You can define customers or categories that never receive such requests, for commercial reasons.
- No valid address A request sent to a wrong address eats into the domain reputation. The check is made before sending.
Automations
What works without daily intervention in the reviews module
The process is configured once and produces results steadily.
Triggering on events
Nothing depends on memory.
- On a delivery, a job or a closed ticket
- Configurable interval
- Activated per customer type
- Stopped at any time
Checking the exclusions
The rules apply by themselves.
- Unsubscribes respected
- Open requests checked
- The minimum interval applied
- A log of the decisions
A single reminder
The rate rises without annoying anyone.
- Only to those who did not open
- Configurable interval
- Stopped on action
- Optional
Automatic records
The history fills itself in.
- The request recorded on the record
- Channel and date
- The status updated
- No manual register
Scheduled reports
The result reaches management.
- Requests per period
- Opens
- Comparison between periods
- Export attached
The link with satisfaction
The requests go to the right customers.
- Using the results from the surveys
- Directing the satisfied ones to the platforms
- The decision stays the company’s
- Through the surveys module
Who sees what
Customer data and communications
Review requests are commercial communications, so they follow the same rules.
- Consent is respected Customers who refused commercial communications receive no requests, whatever the trigger.
- A record of the sendings Every message stays recorded, with recipient, channel and date.
- Role-based access Configuring the triggers and the texts is granted to marketing and administration roles.
- No external lists The requests go out only to the customers in your own database, not to lists bought or imported without consent.
- Requests about personal data The communication history is included in the search, export and anonymisation on request.
- Data on the company server The record of the requests stays in your own installation.
What you need
What needs to be prepared to put the reviews module into operation
We handle the configuration at implementation, on the platforms that matter to you.
01
The public platforms you use
They decide where the customer lands.
- The platforms relevant to your field
- Direct links to the company page
- The order they are presented in
- Agreed together
02
The sending moments
The right triggers.
- After delivery
- After the job
- After a closed request
- A waiting interval
03
The message texts
The company tone.
- A short, clear message
- No wording that suggests rewards
- In the configured languages
- Reviewable later
04
The exclusion rules
They protect the relationship.
- A minimum interval
- Excluded categories
- Customers with open problems
- Agreed internally
05
An email server configured
The messages go out through it.
- An active sending account
- A domain with its reputation configured
- A log of what was sent
- Checked at implementation
06
Clean e-mail addresses
The domain reputation depends on them.
- Verified addresses
- No wrong generic addresses
- Cleaned up at implementation
- Monitored periodically
What it does not do
The limits of the reviews module, stated explicitly
The module sends invitations. It does not produce reviews and it does not influence the platforms.
- It does not publish reviews The review is written and published by the customer, on the platform they choose. We only send the invitation.
- It does not guarantee a number of reviews The rate depends on the relationship with your customers and on the platform. We can optimise the moment and the text, not promise results.
- It does not read reviews from the platforms in every case Pulling public reviews in automatically depends on what each platform allows and is analysed separately.
- We do not use incentives Conditional rewards break the platforms’ rules and put the company page at risk. We do not implement them.
- It does not block access for unhappy customers The exclusions protect the relationship, they do not stop anyone from writing a review.
- It depends on the e-mail server If your e-mail server is unavailable, the invitations wait.
Who it is for
When this module makes sense and when it does not
We prefer to say from the start in which situations the module is not worth its cost, so the sales conversation does not begin with the wrong expectations.
It makes sense if
The situations in which the module pays for itself quickly.
- You have satisfied customers who leave no reviews
- The online reputation directly influences new enquiries
- Review requests are made sporadically now, by whoever remembers
- You want the right moment: right after delivery
It does not make sense if
The situations in which we recommend not buying it now.
- You do not work with end customers and public reputation does not matter
- You already have a review flow that works
- You deliver a few times a month
- Your customers cannot leave public reviews, for confidentiality reasons
How to buy
How the reviews module is licensed
The module is activated through the licence, together with the marketing tools.
Marketing and automation package
It contains the triggers, the routing to the platforms and the record of the requests.
What the core includes
Users and roles, clients and contacts, leads and the sales pipeline, custom fields and 15 interface languages.
Together with the surveys
To ask satisfied customers for reviews, the surveys module is recommended.
Pricing and configurations
Package composition and prices by edition are on the pricing page.
CRM implementations
Companies that have trusted Zarina CRM
Price, warranties and implementation
Review automation: what it costs and what you get
You pay once. Everything that follows is written here, not in hidden conditions.
The price
It is part of the Marketing and automation package: $690 + VAT, on top of the core ($2,320). Bought separately, together with the core: $3,010.
Cheaper in a bundle. The tiers group several packages at a price lower than their sum:
- Pro5 packages + core$3,480−34%
$5,280 - Business8 packages + core$4,640−38%
$7,460 - Enterprise13 packages + core$6,970−31%
$10,080
List prices, excl. VAT, one-time payment, unlimited users. The struck-through price is the sum of the packages bought individually. Current offers apply on the pricing page.
Subscription or licence
What you pay over time for a subscription CRM
Over 3 years, the subscription costs $10,480; the Zarina Pro licence costs $3,480, once.
An indicative comparison: enter the subscription price you pay now. The licence does not grow with the number of users.
What you get
- A lifetime licence, with no subscription and no per-user charge
- Unlimited users, on the same licence
- 6 months of warranty on correct operation: fixing errors and inconsistencies
- Implementation, configuration and team training, included in the price
- The licence is verified locally, on your own server: the application does not depend on our servers to work
How long it takes and what is needed
- 48 hours in the standard configuration; up to 14 working days with customisation around the company’s workflow
- Your own server or web hosting with cPanel, with an SSL certificate
- PHP 7.4 or newer (8.x recommended) and MySQL / MariaDB
- The PHP extensions mysqli, json, mbstring; curl, gd and zip for integrations, PDF and exports
- One cron task, for reminders and automations
Where data lives
- The data stays on your server and does not pass through ours
- Roles and rights per user, two-factor authentication
- An audit trail and limits on login attempts
- Consents and data subject requests, managed in the application
- Digitally signed updates and backups from the application
Frequently asked questions
Questions about review automation
Do you write reviews in customers’ names?
No, under no circumstances. The module sends the invitation, and the review is written and published by the customer, on the platform they choose.
Can I offer a discount for a review?
We do not recommend and do not implement that mechanism. Conditional rewards break the platforms’ rules and can lead to the company page being penalised.
When does the request go out?
At the moment configured after a relevant event: an order delivered, a job completed or a request closed, with a waiting interval you set.
How do you avoid asking unhappy customers for reviews?
Through exclusion rules: customers with open requests, those who refused communications and those contacted recently are skipped automatically.
Do you block unhappy customers from reaching the platforms?
No. The exclusions are a matter of the customer relationship, not a filter. Nobody is stopped from writing a review.
Which platforms do you direct the customer to?
The ones you use. We configure the direct links to the company page, and the customer can choose between several options.
Can the request be sent on WhatsApp?
Yes, if that module is active, respecting the platform rules on business-initiated messages. Otherwise the requests go out by e-mail.
Can a customer receive several requests?
No, if a minimum interval between requests is configured. We recommend a generous interval, so the relationship is not strained.
Do you pull published reviews in automatically?
It depends on what each platform allows. It is analysed separately; it is not included in the module by default.
How is the result measured?
Through the number of requests sent, the opens and the comparison between periods. The number of published reviews is checked on the platforms, because that is where they appear.
Product sheet
Get the complete product sheet by email
A six-page document with everything you need to know before a sales conversation. No obligation and no sales call.
- The platform core and the 13 module packages, with what each one contains
- The features and modules of the edition you choose, plus available integrations
- Full pricing and what it includes: installation, training, data import, warranty
- The native integrations available and the situations where the platform is not a good fit
No monthly subscription
Take control of your operations, once
We install Zarina CRM on your hosting, configure it around your own workflow and train your team. From that moment on, the application is an asset of your company, not a recurring expense.