Texting my AI from the car: what a real estate agent's SI assistant looks like once the basics are in place

I changed a listing price with six words from the car.

That's not a trick, and it's not a special app. It's where all the steps in this series lead once the basics are in place. You have one assistant you can text, that knows your business, can make the change, and checks its own work before it tells you it's done.

Today's episode is a bit different. There's no new prompt to copy. Instead, I'm showing you my real text thread with Stirling, my assistant, so you can see what the finished system looks like from the agent's side: a phone, a short message, and a reply.

What "texting my AI" actually means

Most people picture an assistant on their phone as a chatbot. You ask something, it answers, and you still go and do the work.

This is the other half from Day 1: giving it a job instead of asking it a question. The difference now is where you're sending it from. You're not at your desk with a folder open. You're parked outside an appointment, or between opens, and you send a short message.

For that short message to work, three things have to be true.

It knows your business

Six words only work if the assistant already has the context. It needs to know which listings are yours, what "the price" means on each one, and how you like things done. That's what yesterday's episode was about: giving it a brain. Without that, a short text gets you a string of questions back instead of a finished job.

It can actually make the change

Knowing what you want isn't enough. The assistant needs access to the place the change happens, whether that's your CRM, your website or a document. Without that access, the best it can do is tell you what to change. With it, it makes the change for you.

It checks its own work

This is the part I care about most. A reply that says "done" means nothing unless it's true. A good assistant goes back, looks at the result and confirms it before reporting back. If something didn't work, it should say so plainly, not paper over it.

Why it matters for an agent's week

Our week doesn't happen at a desk. It happens in the car, at appraisals, at open homes and on the phone. The small jobs pile up in the gaps: a price change a vendor has just agreed to, a note to add after a call, an update that needs to go out today.

Usually those jobs wait until you're back at the computer, and by then there are ten of them. Being able to hand one over the moment it comes up, and get a checked answer back, means it's handled while it's still fresh.

The point isn't the phone. The point is that the job gets done properly without you stopping what you're doing.

A quick word on driving

"From the car" means parked. Australian road rules on phone use while driving are strict, and no job is worth it. Pull over, send the message, and get back on the road. The reply will be there when you next stop.

The Day 19 prompt

(No prompt today, just show the real thread.)

There's no prompt to copy today, and that's deliberate.

"No prompt today" is the lesson. Once the basics are in place, you stop writing long, careful prompts for everyday jobs. The context, the access and the habits are already set up, so a short, plain message is enough.

"Just show the real thread" is the proof. A finished system is easier to understand by seeing it than by reading about it. Look at how short my messages are, how specific the replies are, and how each reply confirms what was checked, not just that something was done.

Try it yourself

You won't build the whole thing today, and you shouldn't try. But you can take the first step towards it.

1. Install the Claude app on your phone. Sign in with the same account you use on your computer, so your projects and conversations carry over.
2. Use the project from yesterday. Open the project where you gave Claude a brain, with your notes on how you work. That's what lets a short message make sense.
3. Send it a small job that doesn't change anything live. Something like tidying your notes from an appointment you've just left, or drafting a follow-up message for you to check. Keep it to one job.
4. Ask it to check its own work. Finish with "When you're done, check the result and tell me exactly what you checked." Read how it answers.
5. Only connect live systems once you trust it. If you later connect Claude to a tool where it can change real listings, start with one tool and keep approvals on so nothing changes without your yes.

Then look at the gap between that and your usual week. Every small job you currently save for later is a candidate.

Keep the safety habits, even on your phone

Short messages make it easy to forget the habits from earlier in the series. They matter more here, not less, because you're not sitting in front of the screen watching it work.

• One narrow job, one narrow area. Only give it access to what that job needs. Not your whole computer, not every system you use.
• Approvals on for anything that sends, spends or deletes. And for anything that changes a live listing. A price change is a yes you give, not one it gives itself.
• "Show me your plan first." For anything new, have it tell you what it intends to do before it does it. It costs you one extra message.
• Ask what it checked. "Done" isn't an answer. "Done, and here's what the listing says now" is.

You can loosen the reins as you build trust. Start tight, especially with anything clients or buyers will see.

Where to go from here

This is what the system looks like from the outside: a short text and a checked reply. Everything underneath it is what we've been building one day at a time. That means giving it jobs instead of questions, giving it the right folders, giving it a brain, and keeping the approvals on.

Two days to go. If you've followed along, you already have most of the pieces.

Missed yesterday? Day 18: Give it a brain

Every prompt from the series is on my free prompts page, with a new one each day as the episodes go up, ready to copy.