Art collage: a marble Athena wearing a headset beside an architectural model and laptop

A solution for real estate

JediDesk for real estate agencies

Getting to know your customer begins before the first conversation with an agent.

Try for freeExplore the scenarios

Welcome · property database · agent

A customer submits an enquiry while your agent is at a viewing. JediDesk helps start the conversation: configure a Welcome message, clarify the customer's needs and suggest properties from a connected database. With an integration configured, the prepared lead reaches your CRM. Your agent joins the conversation already understanding what the person is looking for.

The wisdom of choice meets modern technology. An AI interpretation of the classical figure of Athena.

For real estate agencies, agents and property industry servicesUpdated

Day-to-day work in real estate

A brief enquiry holds many details

“I'm looking for a flat” does not yet give an agent enough information to make a selection. The neighbourhood, budget, type of home and urgency all matter. Part of getting to know the customer can happen in chat while your team is in meetings.

Enquiries during viewings

New enquiries arrive while an agent is showing a property or speaking with an owner. The first contact needs its own attention.

An unclear initial request

The customer may not yet have decided between neighbourhoods or types of housing. A sequence of clarifying questions helps establish selection criteria.

Changes in the property database

Prices, descriptions and availability change. Answers must rely on a source the agency keeps up to date.

Several people in the process

One person may receive the enquiry and another conduct the viewing. Your team needs the enquiry details and conversation history.

Before automation

What slows down lead handling

Contact is delayed

After submitting a website form, the customer does not know when they will receive an answer or what happens next. Your team returns to the enquiry when someone is free.

Clarification starts again

Buying or renting, budget, location — the agent gathers basic details again instead of continuing the property search.

Options are found manually

Preferences have to be matched to the database, and the information checked for a recommendation. Simply sending every listing is not enough.

Information does not reach the CRM

Details remain in the conversation. The next person responsible spends time reconstructing the context before contacting the customer.

Automation use cases

From the first message to a meaningful conversation

Build the route you need using Welcome, AI guidance, your database and CRM. Channels, sources and handover rules are configured around your agency's process.

  1. 01Customer criteria
  2. 02Properties from your database
  3. 03Continuation with the agent
Art collage: Athena comparing architectural models of different types of housing
Selection from your own database rather than random options. An artistic AI illustration.
01

Welcome after an enquiry

Someone has just completed a form on your website.

JediDesk Welcome triggers a configured first message in Telegram or WhatsApp if the connection and channel rules allow a conversation to be started. The message can explain the next step.

Connecting channels and systems

The customer receives the opening message and can clarify their enquiry.

02

Initial qualification

The enquiry includes contact details, but it is not yet clear which property to look for.

AI asks the questions you have agreed. For example: buying or renting, preferred location, budget, property type and search timeline. The sequence depends on the customer's answers.

JediDesk AI capabilities

The agent receives a clearly expressed need rather than a brief “call me back”.

03

Matching from your database

The customer has specified their criteria and wants to see options.

The assistant consults the connected feed or property database. It suggests suitable options using available fields. If data or matches are missing, it clarifies the enquiry or brings in an agent.

JediDesk AI capabilities

Matching is based on the agency's properties and the customer's criteria.

04

Context in the CRM

The responsible agent needs to join the enquiry.

With an integration configured, the collected details and conversation context are passed on. Fields, the responsible person and available actions are defined for your CRM.

CRM integrations

Your team starts with a prepared lead.

05

A viewing request

The customer is interested in a property and wants to arrange a meeting.

AI collects the property link and preferred times, then passes them to the agent. A person checks availability and confirms the arrangement.

JediDesk AI capabilities

The agent arranges the viewing with the details they need.

How the solution works

Enquiry → conversation → matching → agent

One example of a configured route. Welcome depends on channel capabilities, matching on database information, and the CRM handover on an agreed integration.

  1. 01

    Starting the contact

    After an enquiry, Welcome sends the first message according to the connected channel's rules. The customer can also initiate the chat themselves.

  2. 02

    Clarifying the need

    The assistant gathers the agreed criteria, such as budget, neighbourhood and property type. It preserves context for the next stages.

  3. 03

    Options from the database

    AI uses connected properties and their specifications. It checks missing data or unusual preferences with your team.

  4. 04

    A prepared lead

    The agent receives details to continue the conversation; with an integration, they are passed to the CRM. A person confirms the viewing.

Form and connected channelQualification questionsFeed or property databaseCRM and team

Capability map

What the agency's assistant brings together

Six parts of the process around one conversation. Each has its own source and configuration requirements.

A website enquiry or customer message

Athena wearing a headset — an artistic depiction of a real estate assistant
JediDesk AIAn assistant for the customer and agent

  • Welcome

    Starts contact after an enquiry where the connected channel supports it.

    Source: Enquiry event + channel rules

  • Search criteria

    Clarifies the need using questions defined by the agency.

    Source: Customer answers + scenario

  • Property options

    Matches using available specifications and the currency of the database.

    Source: Feed / property database

  • Agency rules

    Explains the consultation process and next steps.

    Source: Agency knowledge base

  • A lead in the CRM

    Passes on agreed fields with an integration configured.

    Source: Connection to a specific CRM

  • Agent involvement

    Passes on context for a viewing, clarification or complex enquiry.

    Source: Handover rules + team

The customer receives a next step, and the agent receives prepared context to work with.

An AI depiction of Athena and an illustrative map of configurable capabilities.

Channels and integrations

Your properties and communication channels in one process

Start with the enquiry source and a channel your customers find convenient. The database and CRM connections are designed around available data and actions.

Website chat

Questions alongside a listing or enquiry form.

About the channel

Telegram

Guidance through a connected bot and a Welcome scenario subject to channel requirements.

About the channel

WhatsApp

Conversations and first messages where supported by the configured connection.

About the channel

Viber

Enquiries to your team in a familiar messaging app; this channel appears in the EasyBase case study.

About the channel

Feed, database or WordPress website

Your website can be a source of properties. Data retrieval, available fields and updates are configured separately around the structure of your site or database.

How to connect

CRM and consultation rules

Agree the lead structure, responsible people, reasons for handing over to a person, and actions available through the integration.

How to connect

Example conversations

How AI prepares a conversation for the agent

Illustrative conversations, not real correspondence or listings. They show clarification and handover logic; specific properties and prices come from your database.

Clarify a housing enquiry

Telegram · after a configured Welcome
  1. Customer

    I submitted an enquiry on your website. I'm looking for a flat to rent.

  2. JediDesk AI

    I can see the budget and preferred move-in date from your enquiry. Which neighbourhood are you considering, and how many rooms do you need?

  3. Customer

    Two rooms near the city centre. A separate bedroom is important.

  4. JediDesk AI

    I'll check properties matching these criteria in the agency's database. If there are no suitable options, I'll pass your enquiry to an agent for clarification.

If the database has no suitable options, the agent receives the enquiry with its criteria.

The customer explains their needs before the personal consultation.

Prepare a viewing request

Website chat
  1. Customer

    I'm interested in the flat in this listing. Could I view it tomorrow?

  2. JediDesk AI

    Please send the property link and a convenient time window. I'll pass your preferences to the agent to arrange it.

  3. Customer

    Here's the link. The afternoon would work well.

  4. JediDesk AI

    I'll gather these details for the agent. They will check the property's availability and confirm the viewing time.

The prepared context is passed to your team and, with an integration, to the CRM.

The arrangement is confirmed by the agent who has current information.

Results and benefits

More substance in every enquiry

Assess changes using your own leads: are the required criteria present, are the suggestions appropriate, and does the agent have enough context? The quality of the result depends on your data and process rules.

The contact has a next step

Welcome explains the next step, and the customer can start clarifying details in a convenient channel.

The need becomes clear sooner

Basic details are gathered before the agent conversation, leaving more room for advice.

Matching is grounded in your database

Customer criteria are matched against connected properties and their specifications.

Your team receives the context

The agent sees what has already been discussed and which questions remain open.

Customer experience

How businesses use JediDesk

About EasyBase

A prepared enquiry helps your team continue the work.

An official EasyBase visual from the case study materials. An example of clarifying enquiries and handing them to the team.

EasyBase is a professional property database for agents. In the case study, the service brought together enquiries from Telegram and Viber: AI answers basic questions, clarifies the enquiry and gathers the materials needed by the team.

  • Property links, details and photographs are collected in the conversation.
  • The team receives a prepared enquiry and checks the property.

Built around your process

Why JediDesk suits real estate work

A conversation shaped by your process

Your agency defines questions, consultation rules and situations requiring an agent. AI then prepares the context your team actually needs.

AI capabilities

Your agency's own data

The scenario can be connected to your database and CRM. Sources, fields and update methods are agreed for the task.

Connecting data

A handover to a person with details

Property checks, viewing arrangements and complex questions remain your team's responsibility.

The EasyBase example

Launching the solution

Start with one lead journey

Involve an agent who understands customer work and a specialist responsible for your website or CRM. First test one complete journey, then expand your scenarios.

  1. 1

    Describe the lead you need

    Define customer questions, the enquiry source, the responsible person and criteria for readiness to speak with an agent.

  2. 2

    Prepare properties and channels

    Check your database information, its update method and first-message capabilities in your chosen channel.

  3. 3

    Configure the handover

    Agree CRM fields, available actions and rules for involving a person. Describe situations with missing information separately.

  4. 4

    Walk through the journey as a customer

    Submit a test enquiry, clarify the criteria, and check matching and the handover. Make sure your team can see the context it needs.

JediDesk AI setup guide

Before you start

Frequently asked questions

About Welcome, the property database, CRM and the agent's role.

How does Welcome work after a website enquiry?

JediDesk Welcome is configured as a first message after an event, such as a website form submission. This requires linking the enquiry to an available channel and defining the message and next conversation step. The ability to start a conversation in Telegram or WhatsApp depends on channel rules and the specific connection. Before launch, test the full route from a test form to the customer receiving the message.

Which questions does AI ask to qualify a customer?

Your agency defines the questions according to its process. For example, you can clarify buying or renting, neighbourhood, budget, room count and preferred timeline. This is a configuration example, not a mandatory set for every business. Use information already received and avoid unnecessary repeat questions. Qualification should produce a clear description of the need for property matching and the next conversation with an agent.

Can we match properties from our database or WordPress?

The matching scenario is built on a connected feed or property database. A WordPress website can be the data source, but the connection method needs to be defined separately. Agree fields, filters, updates and behaviour when a suitable property is unavailable. Current prices and availability depend on your source. If there is not enough information, the assistant clarifies the enquiry or passes it to a person.

Is the prepared lead passed to the CRM?

This handover is configured through an integration with a specific CRM. Decide in advance which customer details, property links and conversation details to pass on, and who continues the work. Available actions depend on the system and connection capabilities. Test repeat enquiries, missing fields and handover errors separately so your team knows where to find a lead and how to handle it.

What exactly does the EasyBase case study show?

EasyBase is a service with a professional property database for agents. Its case study shows shared handling of enquiries from Telegram and Viber, basic AI answers, and the collection of links, details and photographs for the team. The team checks properties and performs the final processing. This is an example of context preparation; Welcome, feed-based matching and CRM handovers on this page are described as separate configurable scenarios.

Can AI confirm a viewing or transaction terms on its own?

This page describes preparing an enquiry for an agent: the assistant gathers property information and viewing preferences, then a person confirms the arrangement. Additional actions require separately configured sources, rules and authority. Property checks and agreement of terms remain with the responsible specialists. Define these boundaries before launch and test them with complex sample enquiries.

Other industries

Find your next use case

The next step — your agency

Turn a brief enquiry into a meaningful conversation

Start with Welcome, a few important questions and a handover to the agent. Add database matching and CRM when your data sources are ready.

Try for freeSign up

The free trial lasts 14 days. Channels and integrations are configured around your process.

  • Your properties and criteria
  • Context for your agent
  • AI and your team in one process
Top