Why we put your CRM in a text thread

We put the CRM in a text thread because that is where agents already are. The best interface for a busy agent is not a better dashboard; it is the conversation they are already having all day, with an assistant that speaks up only when something needs them.

That idea is Flo. This is the thinking behind it, and an honest account of where it stops being the right tool.

Where do agents actually spend their day?

In their messages. Between showings, in the car, at a closing table, an agent’s working surface is a phone, and the app that is always open is the one with their clients in it.

A CRM usually lives somewhere else. It is a place you go to, often at a desk, often at the end of the day, to type in what already happened. That is the gap we kept coming back to when designing Flo: the tool that holds your leads sits apart from the place where your work happens.

Why do agents fall behind on their CRM?

Because most CRMs ask for data entry before they give anything back. Log the call. Tag the lead. Set the task. Move the stage. Each step is small, and together they are a second job that competes with the first one.

I do not think that is a discipline problem. It is a design problem. When a tool asks for more than it returns, people stop feeding it, and a CRM that is not fed stops being useful. Follow-up slips, not because anyone decided to let it slip, but because the reminders lived in a screen nobody opened.

So we flipped the direction. Instead of the agent going to the CRM to find out what needs doing, the CRM comes to the agent and says so.

What does it mean to be interrupted only when something needs you?

It means the default is silence. Flo works the database all day in the background, and it texts you when there is something only you can do.

In practice that looks like a few kinds of messages:

• A morning brief. What happened overnight and what deserves your attention today.
• A lead who is ready. Someone who looks like they want to move this week.
• A booking. An appointment that landed on your calendar.

Everything else, the follow-up that keeps hundreds of leads warm, happens without asking you. Forward Flow writes each lead its own campaign of calls, texts, emails and voicemail and runs it at the hours that lead answers, so the thread stays quiet unless there is a reason for it not to be.

The hardest design decision was not what Flo should say. It was everything Flo should not say. An assistant that pings you about every opened email trains you to ignore it, and then it is just another notification.

Answering in plain words

A text thread only works if you can answer the way you would answer a person. No menus, no field names, no remembering where a setting lives.

So you tell Flo what you want. A few illustrative examples of the kind of thing you can say:

• “Push my 3 o’clock to tomorrow morning.”
• “Stop following up with the buyer on Maple, they bought elsewhere.”
• “Don’t call leads after 7 in the evening.”
• “What’s on my calendar Thursday?”

The last two matter more than they look. Scripts, cadence, calling hours and hand-off rules belong to your team to approve and change, and Flo takes those changes in plain words. You should not need a settings page to decide how your own business follows up.

Why run it from Claude or ChatGPT too?

Because for some agents, the conversation they already have all day is not a text thread. It is an AI assistant.

Claude and ChatGPT can both connect to outside tools. One open standard that both support, the Model Context Protocol, describes itself as “an open-source standard for connecting AI applications to external systems”, letting assistants like Claude or ChatGPT reach data sources and tools and take actions on a user’s behalf.

With the Forward Flow connector, you can run your follow-up, calendar and CRM from Claude or ChatGPT, the same way you would by texting Flo. If you already draft your listing descriptions and market updates there, your leads can live in the same conversation instead of in another tab.

Same principle, different doorway: meet the agent where they already are.

What is a text thread good for, and what still belongs in a dashboard?

A text thread is excellent for small, frequent decisions and for being told what needs you. It is weak at anything that needs you to see a lot at once. I would rather say that plainly than pretend a chat can do everything.

Some work is visual by nature. Comparing twenty leads, spotting a pattern in a month of activity, or reading a script line by line before approving it are all things a larger screen does better. Your CRM stays where it is for that, and Forward Flow connects to it rather than replacing it.

The goal is not to make the dashboard disappear. It is to make it something you visit when you want the big picture, not something you have to check to find out whether you are dropping leads.

Designing for trust

A few principles shaped how Flo behaves, and they are worth naming because they apply to any assistant you let near your clients.

• Quiet by default. Every message should be worth reading. If it is not, Flo should not send it.
• Plain language both ways. You should never need to learn the tool’s vocabulary to use it.
• You set the rules. Scripts, cadence, hours and hand-offs are yours to approve, and changing them should take a sentence.
• Guardrails are not optional. Opt-outs are honored instantly and written to the Do Not Call list, calls respect quiet hours, and wrong-person replies are flagged and not called again.

Those are the things that let you stop checking. And not having to check is the point.

Meet Flo

If the idea of a CRM that texts you, instead of the other way around, sounds right, you can meet Flo and see how it fits your day. The quickest way to feel the other side of it, what your leads receive while Flo works, is to play a buyer or seller yourself. Or book a 20-minute demo on your own leads; setup takes about ten minutes once you connect your CRM or import a list and approve the scripts.