The lead sits unassigned
The website form or the Facebook lead lands in a shared inbox. Who picks it up? When? Meanwhile the client is calling another agency.
Custom CRM · Real estate agencies
The agent sells: talks to clients, shows properties, negotiates, closes. The CRM keeps things organised — the lead lands in Telegram, the client card is updated with a few taps, and the manager sees everything in Web Admin. Built around your agency's process, not the other way round.
Custom CRM by Bsmart, Chișinău · Telegram + Web Admin interface · Meta, telephony and website integrations
Almost every agency has tried a CRM. Most gave up on it for the same reason: the agent is out in the field, at viewings, on the phone — and the CRM expects them to open a laptop, click through menus and fill in ten fields. The result: data gets entered in the evening, from memory, or not at all. The manager is looking at a pipeline that doesn't reflect reality.
The website form or the Facebook lead lands in a shared inbox. Who picks it up? When? Meanwhile the client is calling another agency.
Budget, area, number of rooms, what they've already seen, what they liked — the agent knows all of it but writes it down nowhere.
Who, when, which property, what feedback. Without a record, a second viewing of the same property is a waste of everyone's time.
How many leads came in this week, how many were called within the first hour, how many are stuck in negotiation — the answer comes at the Monday meeting, from memory.
We build CRMs for real estate agencies where Telegram is the agent's fast working interface and Web Admin is the manager's environment. It isn't a "Telegram chatbot": it's a complete CRM — leads, client cards, pipeline, tasks, documents, reports — where the agent's daily actions are done from messages with buttons, and analysis and configuration are done in the browser.
Receive the lead, take it, call, update the card, change the stage, see your tasks — from your phone, in seconds.
Full pipeline, unanswered leads, workload per agent, sources, conversion, scheduled reports, rule configuration.
Website, Meta, telephony and Telegram all feed the same database. The client history stays with the agency.
An example flow, the way we usually set it up. Every step can change to match the agency's process.
The screens below are schematic illustrations of the flow, with fictional data. We show screenshots from real implementations, with anonymised data, during the demo.
The lead reaches the agent as a message with buttons. One tap means "I'll take it"; the CRM records the time and creates the first-contact task.
After the first call, the agent fills in the card with buttons and short replies: budget, area, rooms, timeline, financing. No long forms.
The stage changes with one button. Each stage can automatically trigger something: a task, a message to the client, a notification to the manager.
Tasks appear where the agent is: in the morning they get the day's list, and overdue ones come back as reminders. The manager sees overdue tasks per agent.
In Web Admin, the manager sees what is happening now, not what the team remembers at the meeting: new and unanswered leads, pipeline by stage, workload per agent, sources and conversion, overdue tasks.
The modules below are configured per agency. Not all of them are needed from day one — we start with what gets used daily.
From the website, Meta, telephony, Telegram; automatic distribution by rules; escalation when leads aren't taken.
Your agency's fields: budget, area, type, rooms, timeline, financing, properties viewed, feedback, documents.
Your own stages for sales, rentals, purchases; automatic actions on every change; loss reasons.
Created automatically or manually, with due dates; the day's list in Telegram; escalation to the manager.
Contract, preliminary agreement, title documents, attached to the client or the deal; generated from templates where it makes sense.
New lead, overdue task, stage changed, feedback after a viewing — to the agent or the manager, in Telegram.
Agent, team lead, manager, administrator: each sees what they need to. An agent doesn't see another agent's leads unless the agency decides otherwise.
Leads by source, response time, conversion by stage, viewings per agent, deals per month — by email or in Telegram, at a fixed interval.
Summarising the client conversation, extracting criteria from a long message, flagging stalled leads. An assistant, not a decision-maker.
The CRM is the hub; the agency's sources and tools connect to it. We implement only what makes sense for your agency.
We don't promise integrations with portals or services that don't offer an API. We check them together in the first conversation.
Two agencies can have completely different processes and both can be right. We don't force a "universal" pipeline; we design the stages, buttons, fields and rules around how your team works.
Few stages, focus on response speed.
More granular stages, focus on matching the property.
The AI doesn't make decisions for the agent and doesn't talk to clients without someone knowing. We use it as an assistant for repetitive tasks, with the result checked by a person.
The agent sends a voice note after the call; the CRM transcribes it and suggests an update to the card. The agent confirms.
From a long message ("we're looking for something in Ciocana or Râșcani, up to 55k, with a balcony") the AI fills in the fields; the agent checks.
A summary for the manager: leads with no movement for more than 7 days, with the last interaction and a suggested next step.
For frequent questions ("is it still available?", "documents needed for a mortgage"), a suggested reply the agent sends or edits.
Both models make sense. The difference is where the adaptation effort goes: into the team or into the system.
If the agency already has Bitrix24 and uses it, we can configure it and integrate it with Telegram — we don't insist on replacing what works.
A standard customised real-estate CRM can be implemented in roughly 14 days, depending on integrations and process complexity. This is what the two weeks usually look like:
How leads come in, who takes them, which stages really exist, where leads get lost. Output: a draft of the pipeline and the client card.
Stages, fields, roles, Telegram buttons, distribution rules and notifications.
Website, Meta, telephony, data import; automatic tasks and reports.
Training by role (agent, manager), a run with real leads, adjustments, launch.
Projects with multiple integrations, migration from another CRM or specific logic take longer — and we tell you that in the first conversation, not at the end.
Short answers to what agencies ask us most often.
A complete CRM (leads, clients, pipeline, tasks, reports) in which the agent works from Telegram — receives the lead, updates the card, changes the stage, sees their tasks — while the data and management live in Web Admin. It isn't a simple chatbot: Telegram is the interface, the CRM is behind it.
No. They use Telegram, which they already have. The manager uses Web Admin in the browser.
Yes. Leads from Lead Ads and messages can go straight into the CRM with the campaign preserved and be distributed automatically to an agent.
Yes. We connect the phone system (PBX) or IP telephony so that calls appear on the client card and a new number automatically creates a lead.
Yes. Contact forms, viewing requests and property pages can create leads in the CRM, with the source preserved.
Yes, from Excel, from an old CRM or via API, with verification after import.
Yes — the stages, names, fields, buttons, notifications and automatic actions are configured to the agency's process. Two agencies can have completely different pipelines.
The real-time pipeline, unanswered leads, workload and performance per agent, sources and conversion, overdue tasks and scheduled reports.
Conversation summaries, criteria extraction from messages, flagging stalled leads, suggested replies. Always with human review.
A standard customised CRM can be implemented in roughly 14 days, depending on integrations and process complexity.
It depends on the number of agents, the integrations (Meta, telephony, website, databases), automations, AI and any migration. We don't publish a fixed price; after a conversation you get a personalised quote, with what it includes and what it doesn't.
Yes. We migrate contacts, deals and documents, with validation after import.
We'll show you, on an example close to your agency, how a lead comes in, how the agent takes it in Telegram and what the manager sees in Web Admin. No commitment — and you get a personalised quote after the conversation.