What people mean by a bot that finds people
Anyone searching for this usually wants one of three things. The first is to find an employee: a courier, shop assistant, technician or call-centre operator. The second is to find customers or service providers and connect them. The third is to learn about a specific person: who owns a number, who called, where an acquaintance lives.
The first two are ordinary business automation, and that is where companies actually earn or save money. The third is a risk zone, so it deserves a direct answer.
Why lookup bots are a bad bet for a company
Telegram is full of bots promising to trace someone by phone number or photo. Where their data comes from is rarely clear; often it is leaked or home-made databases. If a bot like that runs under your company name, the reputational damage lands on you.
Uzbekistan has a personal data law: collecting and processing information about a person needs a lawful basis and, as a rule, their consent. A bot that hands out someone's details without their knowledge exposes both the person being searched and whoever launched it. Telegram can also block such bots, and your investment disappears with them. For your specific case, ask a lawyer; this article describes practice, not legal advice.
A Telegram bot for finding people: legitimate use cases
From a business owner's point of view, a bot helps you reach people who want to be found: candidates, customers and partners. These scenarios work well in practice:
- Recruiting: the bot collects candidate profiles (city, experience, schedule, contact) and passes them to a recruiter.
- Finding technicians or freelancers: a customer submits a request and the bot lists suitable providers by district and service type.
- Looking up a customer in your own database: a manager enters a number and the bot shows order history from your CRM, available to staff only.
- Referral programme: customers invite friends through a personal link, and the bot counts invitations and awards bonuses.
- A job board for a city or regional Telegram channel, with “looking for work” and “hiring” posts.
- One inbox for leads coming from Instagram, OLX and an Uzum store, so managers stop losing messages in private chats.
How a candidate-matching bot works
The user taps /start, picks a role (“looking for work” or “hiring”) and answers five to seven short questions. Most answers are buttons rather than free text, which is faster and produces fewer mistakes. The phone number is shared by the person themselves through a “Share contact” button.
The finished profile lands in a private chat or an admin panel. A recruiter sets a status: new, contacted, invited, declined. The candidate gets a notification, and the employer receives a shortlist of matching profiles.
In Uzbekistan it pays to plan for Uzbek and Russian from day one, and to filter by city and district. Tashkent, Samarkand, Fergana and other regions search differently, and a single unfiltered feed stops being useful quickly.
What to settle before development starts
Problems rarely come from code; they come from a poorly thought-out process. Decide these points first:
- Consent to data processing, shown in the very first message before any profile is collected.
- Storage: profiles live in your system, not in the private chat of an employee who may leave next month.
- Access rights: who can see contacts and who can export them.
- Protection from spam and fake profiles: limits, moderation, a report button.
- Integrations: CRM, Google Sheets, alerts to a work chat.
- Payments for paid listings or subscriptions through Click or Payme.
- Analytics: how many people started, how many finished the profile, how many responses each employer received.
What drives the price
Cost does not depend on the word “search”. It depends on the scope: the number of scenarios, languages, whether there is an admin panel, filters and a catalogue, CRM and payment integrations, the amount of moderation and the support after launch. A simple profile-collection bot and a small marketplace with ratings and payments are very different projects, so an honest estimate only comes after the scenario is mapped out.
Where to start
Begin with metrics: how many profiles you need per month, what share reaches an interview, and what one filled vacancy or lead costs you. Without those numbers you cannot tell whether the bot pays off. Launch a minimal version, see which question makes people abandon the form, and improve from there.
At markdev we build Telegram bots for businesses in Uzbekistan, from profile forms and catalogues to CRM and payment integrations. If you want to talk through hiring, customer matching or provider search, send us a request and we will review the scenario and suggest a suitable format.
FAQ
Can a bot find a person by phone number?
Not for third parties. That means processing personal data without a lawful basis or consent. Searching inside your own customer database is fine when access is limited to staff.
Which people-finding tasks suit a bot best?
Collecting candidate profiles, matching providers by district and category, referral invitations, and gathering leads from several channels in one place.
Does the bot need an Uzbek-language version?
Yes, if your audience goes beyond Tashkent. A bilingual flow reduces abandoned forms, especially in the regions.
Can the bot accept payments?
Yes. Paid listings and subscriptions can be connected through Click or Payme, subject to the terms of the chosen payment provider.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.