Beauty & Salons · Tanning & Spray Tan Studios

AI Agent for Sunbed Eligibility Screening

Collects the age, skin type and medication declarations your regulations require, and hands every one of them to a person.

Start from this template
Edit it — the agent is built from this briefBuild this agent
How it works
1 Step
Collect before arrival
2 Step
Record and flag
3 Step
Escalate every decision
For new clients and at the intervals your rules require, the agent sends your declaration form and collects the answers.

Overview

What an AI agent for sunbed screening is, and why every decision is escalated.

An AI agent for sunbed eligibility screening is a 24/7 digital assistant that collects the age, skin type and medication declarations your regulations require before a session, records them, and escalates every eligibility decision to trained staff. Sunbed use is regulated in most jurisdictions — age restrictions, skin type assessment, restrictions relating to certain medications and conditions, and in many places specific staffing and record-keeping obligations. Getting this wrong is not a customer service failure, it is a legal one, and it is exactly why the agent's role here is deliberately narrow. It collects declarations and records them. Whether a particular person may use a sunbed, at what exposure, is a judgment that belongs to trained staff operating under your local rules, and no configuration should let software make it.


Capabilities

What the Sunbed Eligibility Screening Agent does

Collects and records declarations. Every decision goes to a person.

01

Collects the declarations your local regulations require before a first session

02

Records age confirmation as your rules require, including identity checks you specify

03

Captures skin type self-declaration and medication or condition disclosures

04

Writes the declarations to the client record, dated

05

Escalates every eligibility decision and every disclosure to trained staff

06

Flags clients whose declarations are incomplete before they arrive

Why you should use the Sunbed Eligibility Screening Agent

Sunbed compliance fails operationally rather than deliberately: declarations get taken at the counter, in a hurry, and the records are inconsistent. Collecting them in writing before arrival produces better completion and a dated record, which is what an inspection actually looks for. The reason the decision stays with staff is not caution for its own sake — in most jurisdictions the assessment and the supervision are specifically required to be carried out by a person, and an automated eligibility decision would put the studio outside its own regulatory position.

Before
Declarations are taken at the counter, inconsistently
Records are incomplete and hard to produce if asked for
Skin type assessment happens verbally and is not recorded
Medication disclosures are made to whoever is on the desk
New clients arrive without having declared anything
After
Declarations are collected in writing before arrival
Records are dated, complete and retrievable
Every disclosure reaches trained staff before the session
Incomplete declarations are flagged before the client arrives
The studio's position is documented rather than assumed
Process

How it works

A three-step flow that completes the declarations before any session.

Step 01

Collect before arrival

For new clients and at the intervals your rules require, the agent sends your declaration form and collects the answers.

Step 02

Record and flag

Answers are written to the client record, dated, and anything incomplete is flagged before the appointment.

Step 03

Escalate every decision

Skin type, medication and condition disclosures go to trained staff, who make every eligibility and exposure decision.


Example

Example workflow

A realistic screening where a medication changes the answer.

Scenario: a studio's declarations were taken at the counter and its records were patchy. A new client books online and receives the declaration form before her appointment. She completes it and discloses a medication. The agent does not assess this, does not confirm her session and does not advise her — it records the declaration and escalates to trained staff, who review it before she arrives and speak to her at the counter. Her session is not confirmed until a person has made that decision. The record of the declaration, its date and the staff decision all exist afterwards.

Missed-Call & Booking Automation Twilio SMSFreshaEmailGoogle Drive AI Agent flow

Audience

Who can benefit

Studios where the regulations are met by whoever is on the desk.

✍️ Tanning studio owners

Sunbed compliance is a legal obligation and it currently depends on a counter conversation.

💼 Studio staff

Declarations arrive completed and reviewed rather than taken in a queue.

🧠 Studio managers

Records are dated and retrievable rather than reconstructed for an inspection.

Studios with unstaffed or low-staff periods

This is precisely where the compliance risk concentrates and where an agent must not decide anything.

🎯 Multi-site operators

Declaration practice becomes consistent across sites rather than varying by counter.

📋 Regulators and inspectors

The record exists in the form the rules expect.

Integrations

Collects the declarations your regulations require and files them.

Twilio SMS

Delivers the declaration form and the follow-ups.

Fresha

Stores the declarations against the client record and the booking.

Email

Carries the longer declaration document where that suits your format.

Google Drive

Stores any identity documentation your rules require, under your own retention policy.

Google Sheets

Tracks declaration completion so no session proceeds undeclared.

Applications

Best use cases

The sessions that cannot lawfully proceed without a completed screening.

Collecting first-session declarations before arrival
Recording skin type declarations in a dated, retrievable form
Getting medication disclosures to trained staff in advance
Flagging incomplete declarations before the appointment
Making declaration practice consistent across sites
Producing records in the form an inspection expects

FAQ

FAQ

Questions about screening consistently rather than when busy.

An AI agent for sunbed eligibility screening is a 24/7 digital assistant that collects the age, skin type and medication declarations your regulations require before a session, records them, and escalates every eligibility decision to trained staff. It collects and records; it decides nothing.

No, and no configuration should allow it. In most jurisdictions the assessment and supervision are required to be carried out by a person, so an automated eligibility decision would put the studio outside its regulatory position as well as being unsafe.

It collects the declaration and any documentation your rules specify, and escalates for verification. Where your local rules require a physical identity check by staff, that check still happens at the counter — the agent gathers the paperwork rather than replacing the check.

They vary by jurisdiction and they change, so set the agent up from your own regulatory position and your local authority's requirements rather than from any general description. This page describes a mechanism for collecting declarations, not the content of any particular regulation.

No. It collects the client's self-declaration using your form and passes it to staff. Skin type assessment determines exposure and it is exactly the judgment the regulations expect a trained person to make.

Every one is escalated. Certain medications increase photosensitivity and the interaction is a matter for trained staff, and sometimes for the client's doctor — the agent does not evaluate any of it.

According to your own retention policy, which should be set from your regulatory requirements. Where records are stored and who can access them are questions worth settling before configuring automated collection rather than after.


AI Agent for Sunbed Eligibility Screening

Collects the age, skin type and medication declarations your regulations require, and hands every one of them to a person.

Start from this template
Edit it — the agent is built from this briefBuild this agent