Set up a salon patch test form that records the client, the product tested, where and when it was applied and who applied it, then send reminder texts timed to the 48-hour mark and file the client's reply. AI helps with the form wording and the texts; a stylist, never AI, decides what a reaction means.
The interval isn't yours to choose. Colour manufacturers set it in their instructions: Herbatint, for one, says to test 48 hours before each use. Read your own brand's leaflet, because a form that says 24 hours where the leaflet says 48 would undermine the whole process. A clear patch test also doesn't guarantee that the colour in the chair is safe, so the form needs a line saying so.
Find out three things before you build the form
The patch test rules belong to your colour manufacturer and your insurer, not to a template. Twenty minutes spent collecting three answers saves you rewriting every field and every reminder later.
- The manufacturer's instructions for the product you use. Note the interval, the test site, how to mix the test, what counts as a reaction and what the client should do. Herbatint says 48 hours before each use, and L'Oréal's packaging says the same, even for someone who has coloured their hair before. You may still meet other figures in training notes or older leaflets; where they differ, the leaflet for the product in your hand wins, and if you use several colour lines you may need a record for each.
- Your insurer's expectations. Ask in writing whether they require a test before every colour service, whether they want a signed record, and how long records must be kept. File the reply with your policy. It settles arguments later.
- Your own house rules. Decide in advance what happens when a client refuses a test, has no result by the day, or says "I've had this colour for years". Many manufacturers and training sources say to test before every colour because sensitivity can develop later. Write your rule on the form, so no stylist has to improvise it on a busy Saturday.
The form, field by field
Split the form by who completes it. The client answers a short section online before the test, the stylist completes the test record at the chair, and the result section is filled in 48 hours later. Each field below is there for a reason, and each has a way to check it is working.
| Client section | Why it is there | How to verify |
|---|---|---|
| Full name and mobile number | The record must match one person, and every reminder goes to this number. | Your first text goes out when the form is submitted, so a wrong number shows up at once. |
| Agreement to be texted | Reminders are the core of the process, and consent should be explicit, not assumed. | Required tick box: "I agree to receive texts about this patch test and my appointment." |
| Colour appointment date and stylist | The 48-hour clock only means something against a booking. | Cross-check against the diary when the form arrives. |
| Past reaction to hair colour, black henna or a temporary tattoo | A previous reaction changes what happens next. | Required yes or no, with a box for details. Any "yes" goes to the stylist before a test is applied. |
| Cuts, sores or irritation on the scalp or test area today | Leaflets commonly advise against colouring irritated or broken skin; check yours. | Required yes or no, asked again at the chair. |
| Anything else we should know (optional) | Gives context without collecting a medical history. | Short free-text box; the stylist reads every entry. |
| Client declaration | The client agrees not to wash, cover or scratch the spot, to check at 48 hours, to report redness, itching, swelling, blisters or burning, to seek urgent medical help for severe symptoms, and accepts that a clear test is no guarantee. | Typed name or signature plus date, stored with the form. |
| Staff and result section | Why it is there | How to verify |
|---|---|---|
| Product, shade and how the test was mixed | A test with a different product proves nothing about the one you'll use. | Copy from your mix card; the stylist initials the line. |
| Batch or lot number, if the leaflet or insurer asks for it | Helps trace a problem back to a product. | Copy from the tube, never from memory. |
| Test site | The client and the stylist must look at the same spot. | Pick from a list: behind left ear, behind right ear, inner elbow. |
| Date, time applied and who applied it | Starts the 48-hour clock and names the person responsible. | Use a time stamp from the form tool rather than typing it. |
| Instructions given | Shows you explained what to do and what to watch for. | Tick box with the instruction sheet version. |
| Result, date and how it arrived | No reaction, reaction (described) or no reply, and whether it came by text, phone or in person. | The status can't stay blank: a missing result is its own status. |
| Decision and sign-off | Proceed, do not colour, or stylist review. A person decides every time. | Stylist's initials on the record. |
| Day-of check | Anything changed since the test? Same product and shade as tested? | Both answered at the chair and initialled before mixing. |
Here is how one record builds up over a week (illustrative, with a placeholder client):
- Monday 11:20: test applied behind the left ear, shade 6.0 mixed per mix card 14, instructions given, applied by stylist 2.
- Monday 11:25: first text sent, "your patch test is on".
- Tuesday 11:20: 24-hour check-in text sent.
- Wednesday 11:20: 48-hour text sent. Client replies "1" at 12:05.
- Wednesday 12:10: front desk records "no reaction, client reply by text" and sends the confirmation message.
- Saturday 14:00: stylist asks about changes since Monday. None. Same product and shade confirmed. Initials added, then the colour is mixed.
At the chair, a stylist needs one quick gate. Print these six points on the colour station card, and rebook if any one fails:
- A patch test record exists for this product and shade.
- It was applied at least as long before the appointment as the leaflet requires.
- The result is recorded as no reaction, along with how it was received.
- The client says nothing has changed on the scalp or test area since.
- The stylist has looked at the skin if there is any doubt at all.
- The stylist has initialled the record before mixing.
The reminder sequence, text by text
The 48 hours are a minimum, not a target. If the test goes on exactly two days before the colour, any late reply leaves no room to rebook. Book the test five to seven days ahead, and the reminders then do their work with time to spare. Below is the sequence, with the point at which a person has to act.
| When | Message purpose | If nothing happens |
|---|---|---|
| At application | Confirms the test is on and repeats "don't wash, cover or scratch". | Nothing to chase; this text is a record. |
| 24 hours | An optional check-in: any itching, burning, swelling or blisters, wash off and call. | No reply needed; a reply goes to the stylist. |
| 48 hours | Asks for the result: reply 1 for no reaction or 2 for any reaction. | Chaser four hours later. |
| About 52 hours | Chaser: still need a result, reply or call; no colour without it. | Front desk phones the client the next morning. |
| Day before the colour | Last call if there is still no result. | No result means the appointment is rebooked, not colour "at your own risk". |
Here are the seven texts I would start from (illustrative). Each is under 160 characters even with a first name of up to ten letters and a salon name of about 20 characters, and all use plain characters. That matters: according to Twilio's SMS documentation, a message over 160 characters is split and billed per segment, and a single emoji or curly apostrophe can cut the limit to 70 characters. Check how your own text provider counts.
1 (at application):
Hi [first name], your patch test is on. Please don't wash, cover or scratch the
spot. We'll text at 48 hours to ask how it looks. [Salon name]
2 (24 hours):
Hi [first name], quick check on your patch test spot. If it itches, burns, swells
or blisters, wash it off and call us. Otherwise leave it alone.
3 (48 hours):
Hi [first name], time to check your patch test spot. Reply 1 if you see no
reaction, or 2 if you see redness, itching, swelling or blisters.
4 (reply to 1):
Thanks, we've recorded no reaction. Your stylist will confirm everything at your
appointment on [day].
5 (reply to 2):
Thanks for telling us. Rinse the spot and don't use hair colour. [Name] will call today.
If you struggle to breathe or swallow, get emergency help now.
6 (chaser):
Hi [first name], we haven't heard about your patch test. Please reply 1 (no
reaction) or 2 (reaction), or call us. We can't colour without it.
7 (day before):
Hi [first name], we still need your patch test result before your colour
tomorrow. Please call us this morning or we'll need to rebook.
Send within sensible hours: a text that lands at 2 a.m. annoys the client and gets ignored. Whether your booking system can send a message a set time after an appointment depends on the product and the plan, so check its help pages for "follow-up" or "post-appointment" messages before building a workaround. The tutorial on setting up Vagaro's reminders shows what one system offers, and for reminder timing and wording in general, see cutting salon no-shows with AI reminders and deposits.
Replies the system must never judge
This is the one part of the process where automation stops. A reaction reply is a health decision, and the people who may make it are your stylists, working from the manufacturer's leaflet. Don't set an AI receptionist, a chatbot or an auto-reply to answer questions such as "is this normal?" Make the reminder texts come from a number or inbox that a person reads, and tell clients to call for anything unusual. The tutorial on treatment questions an AI agent must hand to staff goes into that hand-off in more detail.
| Reply or situation | What happens | Who decides |
|---|---|---|
| "1" (no reaction) | Record the result and how it arrived. Send text 4. Don't write "all clear" or "safe": the stylist confirms on the day. | Front desk records; stylist confirms. |
| "2", or any description of redness, itching, swelling, blisters or burning | No colour. Send text 5, phone the client the same day, record exactly what the client reported. | Stylist. |
| Trouble breathing or swallowing, a swollen face, feeling faint or collapse | Emergency medical help first, a call to the salon second. Record it afterwards. | The client and emergency services, then the owner. |
| No reply by the chaser | Treat it as no result. Phone. Don't assume the test is clear. | Front desk; stylist if still unresolved. |
| A vague reply such as "it's fine I think" | Ask the specific question again, or phone. Record the exact words received. | Front desk; stylist if in doubt. |
| A photo of the test spot | Store with the record. The stylist looks at it. Never paste it into an AI tool. | Stylist. |
The safe default is one sentence long: if in doubt, don't colour. It's worth printing on the front-desk card, because the pressure on a busy day always points the other way.
Where the form and the records live
You have four realistic homes for the form. Pick the one you can keep complete, not the cleverest.
- Your booking system's client forms. The best option when it can attach a form to a service, store the completed form on the client card and send a message after a delay. Plans and features differ, so check before assuming.
- Jotform. The free Starter plan allows 5 forms and 100 submissions a month, with 500 stored; paid plans start at $39 a month ($34 billed annually). Fine for a small salon with a handful of tests a week.
- Google Forms. Free, and its "Go to section based on answer" setting works on multiple-choice and dropdown questions, so ask your yes or no questions that way if you want a "yes" to jump to a details box. Upload questions require the client to sign in with a Google account, so don't rely on it for photos.
- Paper. Fine as a backup at the chair, but a paper record can't send a reminder, so it is only half a system.
Whichever you pick, treat the record as health information. Keep to the fields above, restrict who can open the records, switch on two-step sign-in for the account, and keep photos separate from the main record. Ask your insurer how long the records must be kept, write the answer in your policy, and delete them when the period ends. If clients ask to see or delete their records, ask a data-protection adviser rather than guessing.
If your booking system can't send a delayed text, a small sheet does the job for a salon with a few tests a week. One row per test, client code instead of a name, and a status formula that tells the front desk what to do next:
Columns: A client code | B colour appointment | C test applied | D check due | E reply (1, 2 or blank) | F status | G next step
D2: =IF(C2="","",C2+2)
F2: =IF(C2="","No test on file",
IF(E2="",IF(NOW()>D2+4/24,"Reply overdue","Waiting for 48-hour reply"),
IF(E2=1,"No reaction reported","Stylist to review")))
G2: =IF(AND(E2=1,B2>=D2),"Stylist confirms on the day","Do not colour yet")
Columns B and C hold a date and a time, so C2+2 lands exactly 48 hours later, and D2+4/24 waits the same four hours as the chaser text before flagging a reply as overdue. Test it with three fake rows before using it for real: one with no reply, one with a "1" and one with a "2". Note that the formula never says "cleared": it only reports what was recorded, and the stylist still decides at the chair.
Using AI for the drafting, and what to fix
AI earns its place in two jobs: drafting the form from the leaflet and drafting the texts. Neither involves a client's details, so neither needs any. For the form, paste the patch test section of the manufacturer's leaflet exactly as printed:
I run a hair salon. Below is the patch test section of our colour
manufacturer's leaflet, pasted exactly as printed. It contains no client data.
[paste leaflet text]
Draft a patch test form in four parts: client questions, staff test record,
48-hour result record and day-of-colour check.
- Take the interval, test site, mixing instructions and signs of reaction only
from the leaflet text. Where the leaflet is silent, write CHECK WITH SUPPLIER
OR INSURER instead of guessing.
- Do not ask for a full medical history.
- Include a declaration that a clear test does not guarantee a later colour
will be safe.
- Plain English, short questions, tick boxes wherever possible.
Expect a good structure and a few errors. A first draft might include, for example, a result line reading "If there is no reaction after 24 hours you are safe to colour", an unrequested question about pregnancy, and a mixing line that correctly says CHECK WITH SUPPLIER OR INSURER. Here is what I would fix:
- The 24-hour line. It contradicts a leaflet that says 48 hours. Change it to the leaflet's interval, and read every time reference against the leaflet, because models drift towards common numbers.
- "You are safe to colour". Replace it with "No reaction recorded. Your stylist will confirm on the day." A form shouldn't clear anyone.
- The pregnancy question. Keep it only if the leaflet or your insurer asks for it. Otherwise delete it, since every extra health question is extra health data.
- Anything vague in the mixing line. The flagged placeholder is the model behaving well. Fill it in from the leaflet yourself.
For the texts, give the model the constraints that decide whether a message is safe to send:
Write seven SMS messages for a salon's patch test process, each under 160
characters, plain characters only (no emoji, no curly apostrophes), friendly,
signed [Salon name]. Messages: (1) when the test is applied, (2) a 24-hour
check-in, (3) the 48-hour check asking for reply 1 (no reaction) or 2
(reaction), (4) the reply to 1, (5) the reply to 2, (6) a chaser at 52 hours,
(7) a last call the day before the colour.
Never say a client is safe, clear or fine. Never explain a reaction or tell a
client what their symptoms mean. Any reaction goes to a person.
The first draft of message 4 is often something like "Great news, you're all clear to colour!", which breaks your own rule in one line. Replace it with "we've recorded no reaction" wording as in the set above. Count characters in a plain text editor (or ask the model to count, then check one yourself), and read all seven aloud as a client would hear them.
A quick sum for a four-chair salon
Take a salon that books 30 colour services a week and tests every one. Each test produces four outbound texts (at application, at 24 hours, at 48 hours, and the reply to a "1"), so about 120 texts a week, plus chasers for clients who don't reply; allow six or so. That is roughly 126 texts a week, or about 550 a month, and each should fit a single segment. Multiply that by your provider's price per text, or by the credits it charges, before you commit, because prices differ by system and plan.
Staff time is smaller than most owners expect. Recording 30 replies at about a minute each is half an hour, six phone chases at about three minutes each is 18 minutes, and the Monday audit is five minutes: just under an hour a week. Those are planning figures from the steps above, not measurements. Time yourself for a fortnight. If the total is far higher, the usual cause is a form that asks too much or a reply route that isn't simple enough for clients to use first time.
Checking the process before real clients rely on it
A process that has never been run end to end will fail on its first real client. Run it once with a team member as the dummy client, and give it the same awkward cases you will meet:
- The happy path. Submit the form, apply a pretend test, and confirm every text arrives at the right moment and the record fills in.
- The reaction reply. Reply "2" from the dummy phone. Does a person see it within the hour, and does the record show the exact words?
- The silent client. Don't reply. Does the chaser go out, and does the front desk get a prompt to phone?
- The late booking. Book a colour appointment for the day after the test. Does anything stop it?
After launch, spend five minutes each Monday on the week's colour appointments: every one should have a test on file that is old enough, a recorded result and a stylist's initials. Count the exceptions. A rising number of no-replies usually means the texts are too late in the day or sent from a number clients don't recognise. Fix the sending, not the clients. Re-read the manufacturer's leaflet whenever you change colour line, and update the form first, then the texts, then re-run the dummy client.
If the same visit includes a colour consultation, the tutorial on a hair salon consultation form with colour history and consent covers that form, and it pays to keep the two aligned so the client isn't asked the same question twice. The one on a beauty salon risk assessment covers what a written risk assessment must not skip.
Patch test questions salons ask
Does a regular client still need a patch test?
Most manufacturers' instructions and training material say to test before every colour service, because sensitivity can develop over time, so loyalty isn't an exemption. Read your own colour brand's leaflet, then confirm your insurer's wording in writing, and put the rule on the form so stylists never improvise it on the day.
Can a client do the patch test at home?
Some salons allow it, but applying it in the salon means you control the product, the mix, the site and the time, and the record is complete. If you do allow home tests, give written instructions, log what was used and when, and treat an unconfirmed result as no result.
What if the client sends a photo of the test spot?
A photo can help the stylist, but it is health information, so keep it with the client's record and restrict who can see it. Never paste it into an AI tool, and don't let anyone at the front desk judge it. The stylist reads the photo, and a doubtful one means no colour.
How often should I review the form itself?
Review it whenever you change colour brand, product line or insurer, and at least once a year. Re-read the manufacturer's current leaflet each time, because instructions and ingredients can change. Update the form first, then the reminder texts, then re-run a dummy client through the whole sequence.
Further reads
- Can AI Draft a Tattoo Consent Form? Age, Health and Aftercare Fields — Another consent form where health fields and wording matter.
- AI Voice Agent for Salons: Booking Rules to Set Before It Answers — Rules to set before any AI answers your salon's phone.
- Nail Salon Cleaning Checklist: Daily Logs and Station Resets With AI — Turn another daily record into a checklist that gets completed.
- Should a Hair Salon Use an AI Receptionist? — Decide whether an AI receptionist belongs in your salon at all.
- Fresha AI Concierge: Is It Worth It for a Small Salon? — See what one booking system's AI assistant does and doesn't handle.
- Can AI Manage Salon Inventory? Colour Stock and Reorder Points — Keep colour stock and batch records in step with your tests.
- Chatbot for Hairdresser Customer Service: What to Let It Answer — Sort salon messages into three piles: answer outright, answer with a condition, or hand to a stylist, with fact-sheet wording and a 20-message test.
- Chatbot for Hairdresser Training: Onboard New Stylists With AI — A training bot that answers new stylists only from your manual: standard cards, tool choice, a 25-question test, a four-week plan and a Friday spot-check.
- Gift Voucher Terms and Conditions for a Salon: Draft Them With AI — Gift voucher terms for a salon: nine decisions, clauses to adapt, an AI drafting prompt and the checks a local professional should make.
- How Much to Charge for Hair Extensions: Fitting, Hair and Aftercare — A worked price table for tape-in, beaded and keratin extensions: hair cost, fitting time, maintenance visits and aftercare, modelled with AI.
- Salon Retail Sales: Write Aftercare Product Recommendations With AI — Product cards, a service-to-product map, a safe prompt and a claims check, so aftercare texts sell honestly without health claims.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Herbatint patch test instructions and L'Oréal colourant packaging instructions (48-hour test before each use, signs of reaction); Jotform and Google Forms help pages (plan limits, branching and upload rules); Twilio SMS documentation on segment length. Check your own manufacturer's leaflet and insurer.