Listings went stale.
Rental listings kept going stale: owners had to be called by hand to confirm a unit was still available.
We built an outbound voice agent that calls property owners every two days and, in natural Georgian, confirms whether the rental is still available. The outcome of every call is written to amoCRM immediately, and the public listings channel updates automatically, with no operator involved: outdated listings are removed as soon as an owner says the unit is gone.
The stack is Twilio for telephony, ElevenLabs for the voice and amoCRM as the system of record. Before, owners were called manually, the channel filled with stale listings and call outcomes were not recorded anywhere; now the agent calls on its own on a two-day cycle, every call becomes a CRM record, and the channel stays credible because what it shows is actually available.
What was in the way
- ✗Rental listings went stale
- ✗Owners had to be called manually to confirm availability
- ✗Outdated listings hurt the public channel and its credibility
What the system does
Calling the owner
The agent calls and, in natural Georgian, confirms whether the rental is still available.
CRM updates
The outcome of every call is written to amoCRM immediately.
Channel updates
The public listings channel updates automatically — no operator involved.
How we roll it out.
Requests and access analysis
We study historical requests, verify CRM and API access, and score the automation potential.
A slice of real traffic
The agent runs on part of the live requests with weekly syncs — real dialogues, not a demo.
Metrics and scale-up
We evaluate volume, response speed and escalation share — then expand the agent to full traffic.