OĞUZ EROL · MarkdownTR
Open MarkdownClose
Source: https://oguzerol.com/en/ai-for-real-estate-agents/

[![Example scenario: a WhatsApp question about size and floor arrives, the listing record supplies the details, and a reply draft waits to be checked before sending.](https://oguzerol.com/gorseller/senaryo/ai-for-real-estate-agents-senaryo-en.webp) View full size](https://oguzerol.com/gorseller/senaryo/ai-for-real-estate-agents-senaryo-en.webp)

# Custom Real Estate Office CRM and Team App

[Oğuz Erol](https://oguzerol.com/en/about-me/)  |  12 min read  |  Published: 29 July 2026  |  Updated: 30 October 2026

## Key takeaways

- Client needs, properties, agent assignments and viewings remain separate records.
- Property information retains its source and latest confirmation date.
- AI drafts from approved information without deciding valuations or legal suitability.

If client enquiries, property details and viewing notes sit across different phones and spreadsheets in your multi-agent office, I can bring that work into a custom web application. I separate the office owner’s permissions from agents’ daily screens and connect client CRM, property records, viewing plans, offers and follow-up tasks. These are capabilities that could be developed for your office, not existing product features or a completed client case.

We choose the first version around the handover causing the most difficulty. Agents asking the same client the same questions, forgotten follow-up after a viewing or an owner’s changed price remaining in an old presentation are possible starting points. Replacing every existing CRM or listing tool is not essential. I first establish which system owns each field and who updates it.

## Why does the office owner’s list differ from the agent’s?

One agent may be speaking with a client while another holds a different price note for the same property. The manager sees viewing counts in the weekly meeting but cannot find which terms were presented to each client. An active property record does not establish that it is still available on the same terms.

I do not build the application around names and phone numbers alone. Client requirements, properties, agent assignments and latest confirmations are separate records. Their relationships explain who owns the next action. The owner sees overdue work and exceptions needing a decision; agents complete missing information for their clients. A recorded conversation is not a completed sale. We agree what evidence advances each stage, rather than assuming reports become accurate without team use.

## Example workflow: from first enquiry to post-viewing follow-up

This scenario uses entirely fictional data. A client sends their search area and property requirements through WhatsApp. The office coordinator assigns the enquiry to an agent. The agent considers current properties suitable for sharing and confirms a viewing time with the client, property owner and any current occupant where needed.

| Event | Record created | Owner | Condition for progress |
| --- | --- | --- | --- |
| Enquiry received | Client requirement and source | Office coordinator | Contact and missing fields checked |
| Agent assigned | Assignment and follow-up time | Office manager | Authorised user takes ownership |
| Property suggested | Shared property and information version | Agent | Freshness and sharing eligibility verified |
| Viewing planned | Appointment and participants | Agent | Necessary parties confirm the time |
| Viewing completed | Attendance and client feedback | Agent | Outcome recorded |
| Offer communicated | Price, terms and version | Authorised agent | Authority to communicate and other party’s confirmation |

When the client changes the time, the earlier appointment does not silently disappear. A completed viewing does not automatically mean continued interest; the next action is recorded separately. Communicating an offer, accepting it and completing a transaction remain distinct statuses.

## Screens I can develop around the office

I select screens around how agents work. A short post-viewing entry suits a phone, while the owner may need broader task and record controls.

- **Client enquiry inbox:** source, requirements, area, owner and follow-up date.
- **Client CRM profile:** conversations, shared properties, offers and communication permissions.
- **Property owner profile:** related properties, contacts and open information requests.
- **Property record:** features, document status, latest confirmation and sharing limits.
- **Information change control:** previous price or terms and approval history.
- **Agent assignment:** ownership, internal handover and conflicting assignments.
- **Viewing calendar:** participant confirmations, time changes and attendance status.
- **Offer tracking:** terms, versions, responses and next action.
- **Shared WhatsApp inbox:** assigned conversations, internal notes and human takeover.
- **Document checklist:** outstanding files, document owners and authorised review.
- **Office reporting:** open enquiries, overdue follow-up, viewing outcomes and record quality.
- **Commission tracking:** agreed calculation basis, receipts and any allocation approval.

The first delivery does not require every function. It may cover enquiries, agent assignment and follow-up after viewings alone.

## Client CRM and property records remain separate

CRM explains what a client wants and their relationship history with the office. Someone may own one property and be a prospective buyer in another transaction; these relationships are not compressed into a single label. Property records describe physical characteristics, current terms and information available for sharing. A client can relate to several properties, and a property to several enquiries.

I do not automatically merge people sharing a phone number. The application may suggest similarities for authorised review. Data is limited to what the stated requirement needs. Identity documents, title deed images, full addresses and personal financial circumstances are not casually added to general conversation notes. Necessary documents receive separate access, retention and sharing rules. A client record is not campaign consent; relationship history and marketing permission remain separate.

## Property freshness and permission to share

Prices, availability and owner conditions can change. Records can show the source contact, latest confirmation date and who updated each field. I can prevent a property without current confirmation from being automatically suggested as suitable. Uncertainty creates a task for the agent.

Listing text or presentations can be prepared from approved property fields. Missing views, planning status, usable area or usage rights are not invented. Software does not automatically guarantee legal document accuracy, ownership, representation authority or eligibility to transact. Authorised review and official processes remain separate. Rather than assume those processes are complete, an application checkbox records which review was entered and by whom.

## Agents and external parties have different access

Each employee uses an individual account. Reading records, opening files, making changes, exporting and querying AI follow the same permission boundaries. Assignment, external sharing and commercial term changes can require additional approval.

| Role | Visible information | Permitted action | Boundary |
| --- | --- | --- | --- |
| Office owner/broker in charge | Authorised office records | Assignments, exceptions and sharing approval | Undefined authority is not assumed |
| Office coordinator | Enquiry and appointment fields | Assignment preparation and scheduling | No confidential documents or unrestricted finance access |
| Agent | Assigned clients and suitable properties | Conversations, viewings and draft offers | No unauthorised price changes |
| Finance owner | Authorised transactions and receipts | Recording and comparison | Does not replace technical/legal acceptance |
| Property owner | Their own shared records | Information and term confirmation | No other client history |
| External client | Presentations/appointments shared with them | Responses and confirmation | No internal office notes |

Departing agents lose access; open work is transferred and history retained. Other branches’ records are available only to explicitly authorised roles. Knowing a document link does not grant access.

## Moving from Excel and controlling repeat uploads

I first identify the owners of client, property and viewing files. Free-text areas and property types can map to shared lists. Internal property references and listing portal references are separate identifiers; a phone number is not the universal record key. Formulas and manually marked inactive records are reviewed in sample files.

Re-uploading a report must not create duplicate clients or properties. Matching source identifiers, changed rows and rows requiring review are shown separately. Similar addresses may represent genuinely different properties, so suspected duplicates are not automatically deleted. Import checks compare record counts, active/inactive breakdowns, agent assignments and any outstanding receipt totals. Faulty uploads can be reversed. The data owner performs the final check while the file timestamp and import history remain visible.

## What can AI prepare, and what does it not decide?

AI can extract requirement fields from a long client message, summarise conversations and prepare a presentation draft from approved property information. It can suggest another-language reply or a missing-information checklist. Suggestions show their source record and freshness; missing features are not guessed.

Financial totals and commission allocation follow defined rules. AI is not offered as a definitive property valuation, investment adviser, legal document validator or predictor of certain sales. Clients are not automatically excluded using hidden criteria. Commercial offers, document acceptance and outbound messages can require appropriate human review. The model provider, shared data, retention and usage costs are agreed initially. Prices or documents inaccessible to staff remain inaccessible through AI chat. Automatic replies can stop when staff take over.

## WhatsApp and SMS triggers

Checked 30 October 2026: outside the 24-hour service window following the latest user message, WhatsApp Business Platform requires approved message templates. [WhatsApp policy](https://business.whatsapp.com/policy).

WhatsApp connections require official API access, account eligibility, relevant permissions and templates. The [WhatsApp messaging policy](https://business.whatsapp.com/policy) informs implementation. SMS uses an authorised provider, appropriate message classification and consent/opt-out/İYS checks. The [İYS FAQ](https://iys.org.tr/iys/sss) is one source for distinguishing service notifications from marketing.

| Trigger | Recipient | Before sending |
| --- | --- | --- |
| Enquiry assigned | Relevant agent | Assignment record complete |
| Property information missing | Authorised owner contact | Agent approves sharing scope |
| Viewing time proposed | Relevant parties | Proposal only; final appointment confirmation separate |
| Appointment confirmed/changed | Approved participants | Current time and party confirmations checked |
| Post-viewing follow-up due | Assigned agent | Attendance record and follow-up date available |
| New property announcement ready | Client with appropriate consent | Marketing permission and opt-out checked |

Event and send identifiers prevent a second notification when an event is reprocessed. Opt-outs stop subsequent marketing workflows. Provider acceptance does not establish recipient delivery; delivery failures remain visible. A phone number in an old list does not replace consent. Critical documents or firm commercial terms are not changed solely through a chat reply; the authorised source record is preserved.

## Listing portals and existing CRM connections

Authorised CSV/Excel exports can be the starting point. Portal or CRM APIs require checks of the actual account, subscription, available fields and provider-permitted actions. Reading property records does not authorise publishing listings or changing prices. A write integration does not report publication before receiving a successful source result and reference.

I do not promise ready-made connections to every portal, unlimited listing collection or automated access to restricted data. Usage and sharing conditions are verified. A failed connection does not present an old price as current; the last successful transfer and error are visible. Configuring your existing CRM may be more appropriate if it already meets the need. Full replacement is not an automatic consequence of the control screens described here.

## Reports for the office owner

New enquiries, first responses due, assigned open work, completed viewings and conversations progressing to offers can be reported separately. A planned appointment and a completed viewing are distinct. Lost or postponed enquiries retain their reasons; the system does not automatically penalise employees through scoring.

If commission tracking is required, calculation bases, entitlement events, receipts and allocation approval follow written rules. This is not legal interpretation of entitlement or statutory accounting. Website and advertising sources can link to enquiries where technical measurement and consent allow; a click is not a sale. Unmatched sources, estimates and missing records remain visible. Managers can open the event behind a number and see its period and freshness. Unrecorded historical results are not invented.

## Initial scope, training and delivery checks

The initial process and data review is paid. Sample enquiries, property records and viewings help define fields, roles and approval order. The first delivery could cover assignment and follow-up, or property freshness and viewing plans. Screens, integrations, exclusions and acceptance criteria are documented.

Agents train using sample data representing their actual tasks. Data owners, support hours, incident priorities, backups and restore tests are defined. Development, hosting, maintenance, AI and messaging costs are explained separately. A controlled transition and rollback plan are prepared. Manual fallback during an internet outage is agreed; unbuilt and untested offline operation is not promised.

1. Re-uploading a file must not duplicate clients or properties.
2. Different properties must not merge because their addresses are similar.
3. An unassigned agent must not open confidential client documents.
4. Price changes must trigger freshness warnings for older presentations.
5. Appointment changes must require relevant party confirmations to be checked again.
6. An opt-out must stop the next marketing message.
7. AI must not invent property features absent from the source.
8. A backup must restore with assignments, documents and consent records compared.

## Frequently Asked Questions

### Is this advertising to find home buyers?

This offer is custom software for the office’s own operations. Client acquisition or listing advertising, if requested, requires a separate scope and measurement setup.

### Is it necessary for a single agent?

A simple list and existing CRM may be enough. Custom development becomes relevant when shared records and specific approval/access relationships create a clear need.

### Can every listing portal receive automatic uploads?

Each provider’s access is verified separately. Read and write permissions differ; unsupported connections are not existing features.

### Does AI establish the true value or legal suitability of a property?

This scope does not promise definitive valuation or legal accuracy. AI can draft from approved data while preserving expert review and official processes.

### Can owners and clients use the same system?

If required, verified access can expose only the fields shared with each person. Internal office notes and other people’s records remain restricted.

### Does the system guarantee more sales?

I can commit to delivering agreed screens and rules. Commercial outcomes also depend on prices, demand, properties and team usage; I do not promise unmeasured gains.

## Define your office’s first shared workflow

You can request a scope by saying, **I want to bring client, property and agent tracking into connected records for my office**. The first paid engagement produces a written plan of the screens to develop and delivery checks. You do not need to send actual client documents in the first message; a field list without personal data and an example problem are enough.

Client matching uses the stated property requirement. Buyer classification or automatic exclusion based on sensitive personal characteristics is outside this scope.

[Describe your workflow for a scoping engagement](https://oguzerol.com/en/contact/).

[Back to top ↑](https://oguzerol.com/en/ai-for-real-estate-agents/#icerik)