Skip to content
Real Estate Operations

Answer New Agent Questions Once, Not Five Times

Lionmaker SystemsNovember 10, 20268 min read

4:40 on a Tuesday, and it is the same question

A new agent texts you at 4:40 on a Tuesday. "Quick one: seller wants to do a price drop, do I need anything signed or can I just change it in the MLS?"

You know the answer. You know it because you gave it to someone else in March, and to two people before that, and to the agent sitting ten feet from you last fall. You type it out again from your car.

The question is a good question. The agent was right to ask. That is the part that makes this hard to solve by telling anyone to stop asking.

The questions are fine. The repetition is the leak

This is the weekend off leak, and it does not look like a leak while it is happening. It looks like being a good broker. A new agent needs an answer, you have the answer, you give it. Nobody is doing anything wrong.

What it costs shows up somewhere else. It shows up in the listing appointment you took at 6 PM because the day got eaten. It shows up in the recruiting conversation you keep meaning to have. It shows up on Saturday when the group text finds you.

And it costs the new agent something too. They waited forty minutes for your reply because you were on a call. Forty minutes is a long time to sit with a seller on the other end of the line.

A rough number, so you can see the shape of it

Here is an illustrative example, not a finding. Say you have 18 agents and four of them joined in the last year. Say those four send you six routine questions a week each, and say each one takes you four minutes between reading it, thinking, and typing the answer.

That is 96 minutes a week. Call it 80 hours a year of you, typing things you already know, in pieces too small to feel like anything. Run the numbers on your own roster and your own interruption rate. The point is not the figure. The point is that it never arrives as a block you can see and defend.

The other half of the cost is the switch. You were doing something that needed your full head. Now you are not.

Step one: log the questions for two weeks

Before you build anything, find out what you are actually being asked. For the next two weeks, every time an agent asks you something, paste the question into one note. Do not clean it up. Do not answer it differently than you normally would. Just capture the raw wording.

Ask your office manager and your two most senior agents to do the same. They are fielding a share of this and you may not know which share.

At the end of two weeks you will have somewhere between forty and ninety questions, and you will see the pattern immediately. A large block of them will be the same eight or ten things said in different words. Commission disbursement timing. What goes in the file before the listing goes live. Which form for a price change. How to get a lockbox. Who to call about a sign order. What to tell a seller who wants to cancel.

Step two: write each answer once, in your own words

Take the top twenty questions and answer each one in writing. Not a policy manual. The way you would actually say it in the hallway, including the part where you say "and if the seller pushes back on that, tell them this."

Two rules make these answers usable later. First, be specific to your brokerage: name your forms, your deadlines, your office manager, your actual process, not a generic version of it. Second, mark the edge. Every answer should end with the condition that sends it to you. "If the buyer is also a licensee, bring it to me."

On anything touching fair housing, licensing, advertising rules or contract language, write down what you want the agent to do rather than the ruling itself. Usually that is "ask me, and I will take it to our attorney or the state commission." That line belongs in your answers, not a ruling you drafted on a Tuesday afternoon.

This takes a few hours. It is the only part that genuinely requires you, and you only do it once.

A short word on where this goes next

If you want to see what this one leak costs your brokerage in a year, the Leak Report at systems.lionmaker.io/apply walks through the arithmetic with your own roster numbers. No call required to look at it.

Step three: put the answer where the question gets asked

Here is where most attempts at this stall. The answers get written, they go into a shared folder, and the agent still texts you. Not because they are lazy. Because at 4:40 with a seller on hold, texting you is faster than opening a folder and searching it.

So the answer has to arrive the same way the question was sent. The agent texts the question. The answer comes back as a text. No new app, no login, no "it's in the drive."

That is the whole design principle. Meet the question where it lives. If your agents ask in a group text, the answer needs to show up in a group text. If they call the office line, the answer needs to come back on the phone. Anything that asks the agent to go somewhere else to get it will lose to texting you, every time, and it should.

Step four: decide what still comes to you

Nobody wants a brokerage where the broker never hears from the new agents. You are not trying to be unreachable. You are trying to be reachable for the things that are worth you.

So draw the line explicitly. Write the list of what always reaches you: anything with a complaint in it, anything with a licensee on both sides, anything a client has said in anger, anything about money owed, anything where the agent is scared. Those are not interruptions. Those are the job.

Everything below that line gets the brokerage's own answer at once. Everything above it gets you, with the context attached, so you are not starting from "what happened." The difference between a seven-question Tuesday and a one-question Tuesday is not fewer agents asking. It is a line, written down.

What it looks like when this one is sealed

In the fixed version, the new agent texts at 4:40 and has your brokerage's answer in under a minute. Same wording you would have used, because you wrote it. The price change question is handled before the seller gets impatient.

Muse answers the agents' routine questions from your own policies and files, and sends you only what needs you. Every automated message is tagged "Automated by Lionmaker AI", so nobody is confused about what just replied, and you decide how much sends on its own. Plenty of owners start by approving every answer for the first couple of weeks, watch what goes out, then loosen it.

You keep the mentoring. That is the part that actually makes a new agent stay: the twenty-minute conversation about how to handle a seller who is grieving the house, the ride-along, the debrief after a bad appointment. None of that was ever the thing taking your day. The price change question was.

The first leak tends to be live in about two weeks, built inside the phones, files and CRM you already have, using your rules and your voice. There is nothing for your agents to learn. They keep texting the same way they text now.

Start this week, even without us

You can do the first two steps on your own starting tomorrow. Log the questions for two weeks. Write the top twenty answers in your own words. Mark the edge on each one.

That alone will give you something you do not have right now: a clear view of what is actually consuming your attention, and a version of your brokerage's answers that exists outside your head. Hand it to your office manager and some of it starts working immediately.

The part that is hard to build alone is step three, getting the answer to arrive in the text thread in under a minute, every time, in your voice. That is what we build at Lionmaker Systems, one leak at a time, inside what you already run.

If you want to look at where your brokerage is leaking, the 15-minute Private Automation Briefing is at systems.lionmaker.io/apply, along with the Leak Report that shows what each leak costs over a year. Our team replies within 24 hours.

Back to The Playbook