Discord Bot for a Lash Studio: Booking, Briefs, Images

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?”

Short answer: I built a Discord bot for a lash studio that books appointments through GlossGenius, posts a 24-hour contractor brief before every session, and organizes the reference photos clients send. Discord’s free tier carries no member cap and no monthly fee (Discord pricing, checked June 2026), so the only recurring software cost is her existing booking tool. The bot itself is a one-time build she owns — not another monthly SaaS subscription stacked on the pile.

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.

What this actually costs to run#

The bot runs on tools she mostly already had. Discord is free for a team this size, GlossGenius is the booking software she was already paying for, and the agent is a one-time build she owns rather than a subscription. Here’s the whole stack:

Layer	Tool	Cost (as of June 2026)
Booking + payments	GlossGenius (already in use)	$24–$148/mo
Team coordination	Discord	Free tier — no member cap, no monthly fee
The agent	Discord AI Agent (one-time build)	$2,000–$5,000 once, owned

That last row is the difference that matters. Competitors in this space sell a monthly bot subscription; I deploy it once and she owns the setup. The Discord and the agent don’t add a recurring line item — the only software bill is the GlossGenius plan she’d be paying either way. GlossGenius lists three tiers — Standard $24/mo, Gold $48/mo, Platinum $148/mo — with a flat 2.6% processing rate, per GlossGenius’s pricing page (checked June 2026).

Why Discord and not Telegram#

Discord won because she has contractors and a constant flow of client images — and channels keep those organized in a way Telegram’s DM model can’t. She already had the app on her phone for a community she was part of; she’d just 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, each with one job — that’s the entire structure. The bot reads and writes across all of them; she reads all four but only types in #ops most of the time.

• #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.

How client coordination runs#

A scheduling request comes in, the bot checks her GlossGenius calendar, offers open slots, and writes the confirmed appointment back — no manual calendar-checking, no three-hours-later reply. When a client picks a slot, the confirmation goes out, the appointment lands in GlossGenius, and a summary posts to #schedule.

She’s on GlossGenius for booking and payments, which as of June 2026 runs $24–$148/month depending on tier (GlossGenius pricing). The bot doesn’t replace that — it drives it, so she never opens the calendar herself.

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 sends the client-facing reminders; the Discord bot adds the contractor brief layer on top. 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 the most-used feature 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#

The bot takes the mechanical load; the relationship stays with her. 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. It’s the same pattern I use across AI for small businesses: wire the agent into the tools the owner already runs, deploy it once, and hand over something they own.

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.