A real estate CRM for the texts your agents already get.
Showing requests, sign-call texts and “is this still available?” messages land on whichever phone was on the listing. inChat is designed to put them in one team inbox, with an owner, a next step and the buyer’s details attached.
inChat is in early access. Features shown are in development.
The lead belongs to whichever phone it hit
Most real estate teams already have somewhere to keep contacts. The gap is the conversation. A buyer texts the number on a sign rider at 7:50 PM, the listing agent is at a closing dinner, and by morning the buyer has booked a showing with someone else. When leads are shared across a team, nobody is sure who already replied, and the details that matter (pre-approval, timeline, the other two houses they liked) stay in one agent’s text history.
- 01
Showing requests after hours
Buyers browse in the evening and text when they see something. If the request sits on one agent’s phone until the next day, the weekend showing slots are gone.
- 02
Shared leads with no owner
Team leads hand off overflow and open-house sign-ins, but nobody can see who picked up which buyer. Two agents text the same lead, or none do.
- 03
Qualification lives in someone’s head
Pre-approval status, price range, buyer vs seller, “we need to sell first” — it gets said in a text and never written down where the next agent can find it.
From sign call to showing, on one record
Here’s how a team would run listing and buyer inquiries in inChat as it’s designed. The product is in development; nothing below is generally available yet.
The inquiry lands in the team inbox
Texts to your listing or team number, and WhatsApp messages from relocating buyers, arrive in one shared inbox instead of on one agent’s phone.
A rule assigns it
Route by lead type and area: listing inquiries to the listing agent, buyer leads by neighborhood or round robin, seller inquiries to whoever runs listing appointments.
The agent qualifies in the thread
Buyer or seller, pre-approved or not, price range, timeline, and whether they have a home to sell. Each answer goes into a field on the contact, not just the chat.
Book the showing and loop in the team
Internal notes and @mentions handle the behind-the-scenes part: lockbox access, seller notice requirements, a second agent covering the weekend.
Follow up after the showing
A reminder fires if the buyer hasn’t heard from anyone within the window you set. Long-timeline buyers stay in the pipeline with a next date instead of falling out of it.
A sign-call text at 7:52 PM. The text came in after hours on the listing number, went to the agent covering that area, and the showing, the pre-approval and the second property are on the shared record. If Priya is out Saturday, whoever covers can read the whole thread.
The parts of inChat that matter here.
Assignment by lead type and area
Rules send listing inquiries to the listing agent and spread buyer leads across the team, so every thread has one named owner from the first message.
See conversation assignmentNotes for the behind-the-scenes part
Lockbox questions, seller notice, “can you cover my Saturday?” — internal notes and @mentions sit next to the thread and are never sent to the buyer.
See team collaborationBuyer details as fields, not texts
Pre-approval, price range, buyer or seller, and target move date are fields on the contact, so the next agent doesn’t have to scroll back through the thread to find them.
See custom fieldsA pipeline that follows the conversation
Move a buyer from inquiry to showing to offer from the same screen where you’re texting them. Each deal shows the last message and who owes the next reply.
See the sales pipeline- Dedicated real estate CRMs exist, with MLS and IDX listing feeds, property alerts, transaction checklists and listing marketing. inChat doesn’t do those things and isn’t planned to. It focuses on the conversation layer: who owns each message, how fast it’s answered and what was agreed.
- There are no integrations today, including with listing portals, your website or other CRMs. Leads from those sources reach inChat only if the buyer texts or messages your business number.
- inChat records who owns a lead. It doesn’t calculate splits, referral fees or commissions.
- Business texting in the US requires A2P 10DLC registration, and marketing texts need prior consent. Check with your provider or counsel; rules change.
- Your brokerage may have record-keeping rules for client communications. Confirm what they require before moving conversations to any new tool.
Real estate: your questions.
What inChat is designed to do for real estate, and what’s still being decided.
Ask us something elseProbably not, and we wouldn’t suggest it. If you depend on MLS feeds, property alerts or transaction management, keep the tool that does that. inChat is built for the messaging side: getting each text and WhatsApp conversation assigned, answered and tied to a contact and deal.
That’s the idea. inChat is designed around shared business numbers, so the conversation stays with the team when an agent is off or leaves. SMS and WhatsApp are both launch channels and are in development now.
Yes, that’s how assignment rules are designed: by lead type, area, source number or round robin. You can reassign by hand at any time, and the thread history moves with the lead.
No. inChat has no integrations today and none are scheduled. If a portal integration matters to you, tell us when you request early access. We track what teams ask for.
Not yet. inChat is pre-launch and in early access, and pricing isn’t published. You can request early access and we’ll be in touch as launch scope firms up.
Other ways teams use inChat.
Education
Enrollment inquiries, trial classes and intake deadlines, with parent and student linked.
ExploreProfessional services
Client intake, consult booking and document requests for firms that start by message.
ExploreAgencies
New-business inquiries, discovery calls, retainer proposals and the client threads after.
ExploreEcommerce
Pre-purchase questions, order status and returns over DM, handled by a real person.
ExploreMake every conversation count.
Join the early-access list to see inChat in action, help shape what we build next, and be first to know when your team can start.
- A walkthrough built around your channels
- Early look at pricing and plans
- A direct line to the product team