MILabs
Integrations

Review request automation with SumUp for beauty and hair salons

Set up review request automation with SumUp so salons ask clients for feedback after each visit, with opt-outs checked and staff in control.

Updated 2026-09-08

Review request automation with SumUp

A salon that takes payments through SumUp already has a record of every sale. That record shows that a client paid, but on its own it does not ask for feedback, so the request usually depends on someone remembering to send it. The build adds a step that runs when a booking closes in the scheduling system the salon already uses. The workflow prepares a message in the salon's own voice, checks that the client has not opted out, and sends it by the channel the client expects. SumUp remains the system of record for takings, so the workflow needs only the visit status and the contact details on file, not card data. MILabs is a Sydney agency and delivers this work remotely to businesses outside Sydney. Zapier, Make or n8n can handle the connection. The owner or team lead keeps control of the wording, the timing rules and the review sites that are linked.

How it works

  1. Confirm which field in the booking system marks a visit as complete, and where the client's contact details and opt-out status are held.

  2. Read the completed-visit event with Zapier, Make or n8n, so the workflow starts only for appointments that have actually closed.

  3. Check the opt-out flag before anything is prepared, and end the run for any client who has asked not to be contacted.

  4. Prepare a short message from an approved template with the salon's chosen review link, and hold it for staff approval if the owner wants a check.

  5. Send the request by email or SMS, then write the outcome to a log the owner can read.

  6. Use SumUp only as the record of takings, and keep card data out of every step.

good questions, straight answers

Frequently asked questions

How does a review request automation connect to SumUp?
The workflow starts from the booking or job record in the system the salon already uses, when a visit is marked complete. SumUp keeps the takings, and the workflow reads only the visit status and contact details on file. A tool such as Zapier, Make or n8n passes those fields into the message step. Card numbers and other payment data stay out of the workflow altogether, so the connection never needs them.
Do I need a developer to connect a review request automation to SumUp?
The answer depends on the booking system. Connecting the booking tool to a workflow tool such as Zapier, Make or n8n is a configuration task that a confident team member can handle. A developer is more useful when a custom tool reads SumUp records through its API, since the current scopes must be confirmed first. MILabs can scope that work, and the owner approves the message wording before anything is sent.
How does a review request automation stay in step with SumUp?
The workflow follows the booking record, so it stays current as long as visits are closed in that system on the day they finish. Any SumUp export used alongside it is only as current as the moment it was downloaded, and a live link depends on a connection someone has built and maintains. Reviewing the message log and the opt-out list at regular intervals keeps both in step.
How do I know a review request automation works with SumUp?
Test it with one closed visit before switching it on for every booking. Check that the message arrives in the right form, that the contact details are correct, that an opted-out client receives nothing, and that the log records the send. Because the workflow touches only the booking record and contact details, a test does not need live card data. Confirm the SumUp side against the dashboard export for the same day.
Can I start with a part of a review request automation on SumUp?
Yes. A salon can begin with the message step alone, using an approved template and manual sends, and add the automatic trigger once the wording is settled. Opt-out checks stay in place from the first send. Starting smaller keeps the scope clear and lets the team see how clients respond. Later items such as replies to feedback can wait until the basic requests are running reliably.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.