Telegram bots and automatic posting for car dealers

A dealer importing from Korea answers the same four questions fifty times a week: what have you got, how much is it landed, what year, and can I see photos. A website answers them only for the people who find the website. A Telegram bot answers them inside the app the customer was already in, at two in the morning, in their own language, without anyone being awake.

It is also where the buyers already are. Across the Balkans, Russia and Central Asia the car trade runs on Telegram channels and groups rather than on search, which means a bot is a distribution channel and not merely a convenience. The website is how you get found; the bot is how the conversation actually happens.

Five patterns cover almost every request. They combine freely — most dealers end up with the search bot and the alert bot behind one account, which is one build rather than two.

A car arriving in your filters is an event. Once something is watching for that event, it can become several things at once: a message in your channel, a post on your feed, an email to the customer who asked for exactly that car last month, and a row in your CRM.

The posts are rendered onto your own template rather than dumped as a screenshot — your logo, your colours, a watermark and the price overlaid where you want it, so a channel scrolled quickly looks art-directed rather than automated. Three events are worth posting and all three are supported: new arrival, price drop, and just sold. The third one does more work than people expect, because a feed of cars that visibly sell is the only proof a new importer has.

There is no magic in it and it is worth seeing, because it is also the answer to “can I build this myself” — which, if you have a developer, is yes.

A saved search is a stored set of query parameters. A worker replays it on a timer, compares the result against what it saw last time, and anything new or newly cheaper becomes an event. The count endpoint is what makes this affordable: asking how many matches exist is one request, so a watcher only pages through results when the number has actually moved.

Bots are quoted per job, because the distance between a one-command search bot and a full sales pipeline is too wide to put one number on. Describe what you want and a figure comes back, not a questionnaire.

If you want the whole catalogue on this page as part of a site, it is already packaged: the Autopilot build is a custom marketplace plus the alert engine, the Telegram channel poster and the Instagram scheduler, at a published price.

Nothing here is gated. The API that the bots run on is the same one a free key opens, the count-first pattern above is the whole trick, and the endpoint reference is published. A competent developer with a weekend can have a search bot answering in a Telegram group.

What tends to be underestimated is the second half: handling sold cars, keeping the request count sane, rendering a post that looks deliberate, and surviving the week Encar changes a payload. Those are the reasons people hand it over rather than the bot itself.