How a lash studio runs daily ops with a Discord bot
A walkthrough of the Discord agent I deployed for a small lash studio — client coordination, appointment reminders, and image handoffs, all running without the owner touching a terminal.
The lash studio owner I deployed for runs her entire business from her phone. Two contractors, a rotating client list, and a nonstop stream of DMs — appointment requests, reference images, rescheduling asks, the occasional “can I come in today?”
Before the Discord bot, her workflow was: text back every message manually, forward photos to her contractors through a different app, and keep a shared Notes document for “what everyone’s doing this week.” The notes document was always a day behind. Contractors would show up to appointments without having seen the reference images the client sent. She was the relay between every piece of information.
Why Discord and not Telegram
She already had Discord on her phone for a separate community she was part of. She’d never thought of it as a business tool.
When I asked her three questions — do you have a team, do you deal with a lot of images, do you want channels to separate different types of conversations — all three answers pointed the same way. The Telegram vs. Discord decision usually comes down to that: if you have contractors or staff and deal with media, Discord’s channel structure handles it better than Telegram’s DM model. She had both conditions.
The server layout
Four channels. That’s it.
- #intake — inbound client requests, routed from her booking form and a link she sends to new clients.
- #schedule — the bot posts daily appointment summaries every morning at 8 AM, and a next-day brief the evening before.
- #inspo — clients forward reference images; the bot organizes them by appointment date and tags the assigned contractor.
- #ops — anything internal: supply requests, notes between contractors, “running 20 minutes late” messages.
The bot reads and writes across all four. She reads all four but only has to type in #ops most of the time.
How client coordination runs
When a client sends a scheduling request through the intake flow, the bot checks the calendar — she’s on GlossGenius — confirms available slots, and sends back a few options. Client picks one, confirmation goes out, appointment lands in GlossGenius, and a summary posts to #schedule.
No manual calendar-checking. No back-and-forth where she remembers to reply three hours later.
The bot also handles the standard FAQ load: how long does a full set take, do you do mega volume, what’s the cancellation policy. She defined those answers once during setup, in her own words. The bot repeats them accurately every time.
Appointment reminders for contractors
GlossGenius handles client-facing reminders. What the Discord bot adds is the contractor brief layer.
Twenty-four hours before each appointment, the bot posts to #schedule: client name, service type, any notes from intake, allergy flags, and the reference images from #inspo — all in one message, contractor tagged. No one checks the wrong notes document. No one starts a set without knowing what the client actually wanted.
The image workflow
This became one of the most-used features after deployment, and it wasn’t the thing I led with in the sales conversation.
Lash clients send reference images constantly. Before the bot, those images buried themselves in SMS threads or got forwarded out of order, and sometimes a contractor would start an appointment without seeing what the client wanted. Now, the booking confirmation flow includes a message to the client: “If you have reference photos, send them here before your appointment.” They drop images directly into the conversation. The bot pulls those and posts them to #inspo with the client name, appointment date, and the assigned contractor tagged.
The contractor sees the images in the channel before the session. The client doesn’t have to remember to pull them up at the start.
What she still does herself
Rescheduling a long-term client who’s going through something. Pricing conversations that need back-and-forth. Anything where the relationship matters more than the efficiency.
The bot doesn’t try to replicate that. It takes the mechanical load off so she has more bandwidth for the parts that actually need her.
If your setup looks like this
If you have at least one contractor or staff member, deal with a steady stream of client images, and want a coordination layer that isn’t a shared document nobody updates — this is the deployment shape that fits.
The specifics are at the Discord AI Agent page. Or run your current workflow through the free audit and I’ll tell you what the build looks like for your setup.
