Українська ❤️ 
Русский 
PropTech · support and property requests
AI support for real estate agents. The EasyBase case.
A link in one chat. Photos in another. JediDesk helps EasyBase turn an agent’s messages into a clear request, with the details, clarifications and context the team needs.
Official EasyBase visualSolution scope
About the company
Properties in the database. Agents on the move.
EasyBase is a professional database of verified properties for real estate agents. It helps users find listings, work with client requests and collaborate with colleagues.
According to EasyBase, the value is not simply the number of listings. Its team verifies information and keeps properties up to date. Support therefore needs enough detail from an agent, not just a brief “please add this apartment.”
About EasyBase on its official website- Who it serves
- Real estate agents and property professionals
- What matters
- Verified property information
- JediDesk’s role
- Support and request preparation
Official EasyBase visualThe original photos show the Ukrainian interface. They demonstrate EasyBase, not the JediDesk interface or currently available property listings.
The business challenge
Bring the conversation together. Keep the details.
An agent sends a link, then a new price, then photos. Meanwhile, someone else asks where to find their listing. The team has to explain the service while manually gathering materials.
Recurring questions
Explain basic EasyBase tasks: finding, adding or updating a property. Leave questions that require specialist involvement with the team.
Separate messengers
Bring Telegram and Viber requests together so the team can see the conversation history instead of piecing it together.
Scattered information
Collect the link, property details and photos into one prepared request. Ask for missing information before handing it over.
The team explains the service and gathers information from the chat at the same time.
AI handles initial guidance and clarification. The team receives the request with its context.
How the solution works
From a message to a prepared request.
JediDesk combines guidance and information gathering in a single conversation. Simple questions get a knowledge-base answer. Property requests get clarification and a handoff to the team.
The agent writes
Sends a request and materials in their usual messenger.
- A link to the property
- Details in text
- Photographs
AI clarifies
Explains basic tasks, asks for missing details and structures the information.
The team receives
Gets the gathered information and conversation history for further verification and action.
EasyBase
- What needs to be done
- A property link or ID
- Details and attached photos
People remain responsible for property verification.
The assistant prepares a request. It does not verify the property’s accuracy or promise to change a database entry on its own. Account-specific questions go to the EasyBase team.
AI assistant visual map
How the EasyBase AI assistant structures an agent request
An agent sends a link, text details or photos through Telegram or Viber. The assistant clarifies missing information, keeps one shared context and hands a structured request to the team for verification and processing.
Four practical scenarios
One conversation. A clear next step.
Typical requests from the case, from a quick explanation to handing materials to a specialist.
“Where is my listing?”
AI explains how to look for a property and clarifies what the user sees. If the issue requires checking inside the account, the team takes over.
Guidance or a contextual handoff
I cannot find my listing in EasyBase.
I can help you navigate. Do you have a property link or ID? Please also tell me how you are searching.
I have the ID, but search does not find it.
Add the ID to this conversation. I’ll pass the details to the team so they can check.
Illustrative reconstruction based on the case brief. Not a real customer conversation.
A link starts the request.
An agent can send an OLX or DIM.RIA link. The assistant gathers the necessary details and prepares materials for the team. Sending a link does not mean automatic publication.
Materials ready for processing
I want to add a property. Can I send a DIM.RIA link?
Yes. Send the link and explain what you want to add. I’ll ask you for any missing information.
An apartment. I’ll send the photos separately.
Add the photos to this conversation. I’ll gather the materials for EasyBase’s team. The property will still need their verification.
Illustrative reconstruction based on the case brief. Not a real customer conversation.
New price. New photos. The same context.
Instead of several scattered messages, the team receives a clear task: which property needs updating and exactly what has changed.
Changes collected, not published
I need to change the price and add new photos of an apartment.
Please send the property link or ID, the new price with its currency, and the photos.
I’ll send the photos here. They should replace the old ones.
I’ll note that the photos should be replaced, not added. Once the materials arrive, I’ll pass the request to the team.
Illustrative reconstruction based on the case brief. Not a real customer conversation.
When the answer is not in the knowledge base.
Personal information, access and questions requiring a system check should not be resolved through AI guesswork. A specialist receives the request with its history.
A person continues from the handoff
My question is about my account. Someone needs to check the system.
The EasyBase team should check that. Briefly describe the issue and I’ll pass the request on with its context.
I cannot see the expected changes in my profile.
I’m passing the description to the team. Do not send passwords or other secrets in the chat.
Illustrative reconstruction based on the case brief. Not a real customer conversation.
What changed
Less piecing things together. More context to work with.
According to the case brief, the solution changed how support is organized. These are process changes, not measured efficiency percentages.
A shared history
Requests from both messengers come into a shared JediDesk workspace.
Prepared materials
Links, property details and photos are collected within one request.
A clear handoff
The team receives a clarified request and can see what was discussed earlier.
Measurement plan
The next step is to measure the effect.
The source materials do not provide verified time savings or an AI resolution rate. Evaluating the impact requires a separate set of measurements.
| Metric | What to check |
|---|---|
| First response | Time from the request to the first meaningful answer. |
| Request completeness | Whether the link, details and photos are sufficient for the next step. |
| AI and team involvement | Which requests end with guidance and which need a specialist. |
| Handoff preparation | Time from receiving materials to passing on a prepared request. |
Questions about the solution
What should you know about this case?
What does the AI assistant do for EasyBase?
It answers basic service questions, clarifies the agent’s request and collects property information. When a person or an internal system check is needed, it hands the request to the team with the conversation history.
Which channels were connected to JediDesk?
The case describes Telegram and Viber. Requests from both channels were brought into a shared workspace for the support team.
Can AI add or change properties in the database on its own?
The case supports gathering and preparing information for EasyBase’s team, not autonomous database changes. Final processing and verification should not be confused with an AI reply in a chat.
Is this an OLX or DIM.RIA API integration?
No. These sites are mentioned as examples of links an agent can send. An official API integration, partnership or guaranteed automatic parsing is not substantiated by the case materials.
How do we start a similar rollout?
Prepare a knowledge base, common questions, required information for each request and human-handoff rules. After creating an account, agree on channel connections and test the scenarios with sample requests.
JediDesk for your team
Turn messages into clear requests.
Start with a knowledge base and rules for involving a person. Let AI help with recurring questions while your team gets the context for the next step.
Channels, data sources and setup time depend on your process. This case does not imply an out-of-the-box integration with every property database.