Anyone who sells a private event space knows the message. One line, asking about a date. No event type, no guest count, no budget, no phone number.
So the salesperson writes back and asks. The customer answers a day later with half of it. Somebody asks again. By the time your team knows whether this is a 40-person dinner or a 200-person wedding, days have gone by, and the customer may have booked the venue that answered faster.
The expensive part isn't the typing. It's that your best salesperson spends the morning collecting facts instead of selling.
I run Stepthrough, free hands-on AI and software training for white-collar workers, and I built a lesson on this using Mixdesk, a shared inbox for customer messages with an AI agent feature. (Disclosure: Mixdesk contacted me about listing in our free AI tools directory and asked about a lesson. No payment was involved.)
The example is Cedar Hall, a made-up event venue. The same setup works for a caterer, a law firm's intake desk or anyone whose first message never contains enough.
The goal: a first reply, not a salesperson
The agent's job here is small on purpose. It collects five details, repeats them back, and tells the customer a person will follow up. It doesn't sell, quote or promise. That narrow job is what makes it reasonable to put in front of customers in the first place.
Part 1: build the agent
- In Mixdesk, open AI, then AI agents, and click Create AI agent. AI agents are on the trial and paid plans. The free inbox plan doesn't include them.
- Add an Avatar (it's required, so use your logo) and a Name.
- Write the Persona. This is the job description, in plain language.
Here's the one from the lesson:
You are the first reply for Cedar Hall, a private event venue. Most people
ask about a date and leave out what our sales team needs. Before a person
follows up, politely collect these five details, asking one question at a
time: event type, preferred date, guest count, budget range, and the best
email or phone number. Skip anything they already told you. Do not quote
prices, confirm availability, or promise a date. When you have all five,
repeat them back as a short list and say a member of our team will follow
up within one business day.
The line to protect is the one in the middle: do not quote prices, confirm availability, or promise a date. The agent answers in your name. If it tells someone the Saturday is free and it isn't, that's your problem, not the software's.
Part 2: test it the way customers actually behave
Test preview on the right lets you chat with the agent before it talks to anyone. Don't test it politely. Real customers don't answer the question you asked.
Here's what happened in my run:
- I sent a one-liner about a date. It didn't confirm the date, which is what the persona told it to do, and it asked one question: the event type. Good.
- It then asked which year. I ignored that and gave it the guest count and budget instead, the way a real customer might.
- It moved on to contact details and never asked for the year again.
That's the reason to test. On a clean run you'd never see it: a detail can get skipped when someone answers out of order. In my run, once I sent the email and the date together, the agent produced all five details in a list, plus the one-business-day line. So read each summary for gaps, rather than assuming the agent will circle back.
The summary is what your team reads, so read it the way they will. The stars around the labels were raw formatting in Test preview. Check how it looks on your live channel before you trust that it's tidy.
Click Confirm to save. Linked knowledge bases, Tools, Reply delay and Combine replies are there for later. You don't need them for this job.
Part 3: the step people miss
The agent is saved, and it answers nobody. Something has to send conversations to it.
- Click Automation. Default Automation decides who gets each new message. Click Edit.
- Add an Assign AI agent node to the canvas and click it.
- Choose your agent under Select an AI agent.
- Tick Show a "Talk to an agent" button, so a customer can always reach a person.
- Click Save, connect the trigger to the node, and Save the automation.
To be straight about what I tested: I stopped before saving the automation, so my own inbox stayed as it was. Test it on a live channel with your own phone before you rely on it.
Three rules I'd keep
- Always leave a door to a person. The "Talk to an agent" button isn't optional for anyone planning a wedding.
- Keep prices out of the agent's job. Its job is collecting details. Pricing is your salesperson's conversation.
- Have someone read the first week of conversations. You'll find the skipped-detail cases faster than any test will.
What this saves
Not the sale. The sale still needs your person. It saves the back-and-forth before the first real conversation, and it means your salesperson opens each lead already knowing the type, date, guest count, budget and how to reach them.
Practice it step by step
The free lesson has 15 steps in 3 parts. You click through a practice copy of Mixdesk with a made-up venue, it checks your work as you go, and nothing touches a real account.
Top comments (1)
The repeat back step is the safeguard I would keep. Have the agent restate the five details in one short message before it hands off, so a skipped year or a wrong guest count surfaces while the customer is still in the chat. Would you rather have it ask the missing detail first or repeat what it already has first?