Playbooks · 6 min read
Makeup Artist DMs: Never Automate a Skin Question
Read a month of a makeup artist's DMs and they sort into three piles that behave completely differently.
The first is logistics: dates, travel, how long a bridal look takes, do you do hair as well. The second is the portfolio question, which usually arrives as a screenshot with no words attached. The third is skin — allergies, reactions, what a client can use, whether something will suit a condition they are describing.
Only the first pile belongs to an automation. The second one cannot be seen by an automation. The third must never touch one, and that is where this post starts.
The skin pile, and the rule around it
Somebody sends you a close-up of their face with redness on the jaw and asks whether your bridal package will be alright. Somebody else mentions a treatment they had last week. Somebody else says a product they used last time made their eyes swell.
An automated reply to any of those is wrong even when it is cautious, and it is wrong for a reason that has nothing to do with any rule this post could quote. A question about somebody's skin is a question about a body the system has never seen, asked by a person who is trusting you specifically. A keyword match cannot do that, and a generated reply will sound confident because confidence is what generation produces.
Put the vocabulary on the negative keyword list before you build a single automation. allergy, allergic, reaction, rash, sensitive skin, acne, eczema, psoriasis, laser, peel, botox, filler, pregnant, patch test, breakout, pimple, dermat, skin problem. Add the ones your own inbox uses, in the languages your clients write in.
A negative keyword stops the reply from being sent at all, which is the outcome you want. The message sits in the inbox and a person reads it.
A four-second reply to somebody describing their skin does not read as good service. It reads as: nobody looked at this.
The portfolio pile, which your triggers cannot see
The highest-intent message a makeup artist receives is an image. A screenshot from a Pinterest board, a still from a film, a photo of a cousin at a wedding last November. "Aisa look kar sakte ho?"
A trigger matches words. An image has none. If the picture arrives with no caption, nothing fires, nothing is captured, and it exists only in the inbox. There is no image recognition here and nothing to switch on — the jewellery version of this problem describes the same limitation, because the two businesses share it exactly.
The consequence is a workflow one and it is worth being blunt about. Automation will make your reply count go up while covering none of your most valuable enquiries. So it must not become the reason you check the inbox less often.
The one useful move: put "send me the picture" in your bio and in your public replies. It is genuinely good advice for the client, and it moves the expensive conversation to the surface where a human is looking.
The logistics pile, which is a real chunk of volume
Everything here is fixed, identical for everyone, and safe:
- What a booking involves. Whether a trial is part of it, how long a bridal look takes, how early you arrive before a muhurat, how many people you can do in a morning.
- Travel. Which cities you work in, whether you travel outside, what the travel and stay arrangement is in structure rather than in rupees. "Travel and stay is on the client for anything outside the city" is a mechanism. A number is a quote.
- What you bring. Whether you use your own kit, whether false lashes and drape are included, whether you do hair or bring a hairstylist.
- How to enquire properly. The three things you need from anyone asking about a date: the date, the venue, and the ready-by time. Ask for those in the reply and half your back-and-forth disappears.
Note what is not in that list: the date itself. Nothing here can see, hold or confirm your calendar. There is no booking, no diary access, no reminders and no deposit collection. A reply saying "yes 14 December is free" is a guess, and in a business where a bride has told her family she has an artist, being wrong about it is not a small correction. The salon version of that argument is the fuller one and it applies here without changes.
Pricing, in structure rather than in numbers
Bridal pricing depends on the day, the number of people, the travel and the season. A number in a template is a number you will be held to by somebody who screenshots it in April.
Say the mechanism instead. What a package covers, what changes the figure, and that you will quote once you have the date and the venue. Then put discount, budget mein, kam kar dijiye, package deal on the negative list, because a generated reply will negotiate on your behalf with real enthusiasm.
The public reply is louder than you think
A comment automation replies in public, under a wedding reel, using the commenter's handle.
A woman asking about bridal makeup is announcing her wedding to everyone who follows her, and not all of them have been told yet. It sounds like a small thing until it is not. Keep the public reply completely generic — "DM check kar lijiye" — with no service, no date and nothing specific to her.
Two settings that fit this business
Quiet hours, narrow. Brides message at midnight and decide at midnight. A reply at 8am often arrives after somebody else answered.
The review queue. Anything the system is not confident about waits for you instead of going out. On a high-value, low-volume inbox that trade is obvious: a reply delayed by an hour is a mild annoyance and a confidently wrong one is the booking.
The edges
Takeover means the moment you reply by hand — from a chair, between two faces — the automation is out of that thread permanently. No CRM sync; leads leave as a CSV, which is worth reading before wedding season to see which looks people actually asked about. No WhatsApp. It cannot message anybody who has not messaged you first.
Official Graph API only: seven days to reply to a comment, twenty-four hours inside a DM thread, restarted only by their message. On a day when you are working from six in the morning, both of those matter.
Templated replies are free and unlimited; a credit is spent only when the AI writes a new reply. Free tier is 100 credits with no card, packs from ₹499. Built the way this post describes — logistics templated, skin refused, images routed to you — most artists barely touch the paid half.
Build the refusal list first. Then one logistics automation on one reel, and read what the checks stopped after a week.
