Write us on Telegram@Odilient

TELEGRAM BOT

Bronjoy Staff Bot

Telegram bot for salon and clinic owners in Uzbekistan to run their business from chat: confirm bookings, claim a listing, receive quiet daily digests and ask an AI assistant.

In-house product
Client
Local Services
Industry
Ongoing
Duration
2026
Year
Where it started

The Challenge

Owners of small salons and clinics spend the day with clients, not in a web dashboard, and Telegram is how Bronjoy notifies providers today. A bot for them has to do real work, not just forward alerts: confirm bookings, reply to reviews, onboard a business and handle listing claims. It also has to stay quiet enough that owners do not mute it.

What we did

The Solution

We turned the staff bot into a full control surface built with Nutgram: inline screens for appointments, clients, services, team, reviews, schedule, waitlist and stats, plus an AI assistant with tools for the same data. Owners can onboard, create or join a business and upload claim documents in chat. A notification dispatcher applies quiet hours, coalescing, rate caps and digests before anything is sent.

Built with
NutgramTelegram Bot APITelegram Mini AppsLaravel 12Laravel AIGeminiPostgreSQLLaravel Horizon
Inside the build

How It Came Together

A Telegram bot for business owners and their staff

The Bronjoy staff bot turns Telegram into a control surface for a business on Bronjoy. Owners and staff at salons, barbershops and clinics see today's appointments, confirm or decline new bookings, reply to reviews, check stats and ask an AI assistant to make changes, all in chat. There is no native provider app, so this bot is also how Bronjoy delivers provider notifications.

Key features

  • Connect and onboard in chat — after choosing a language, a new user shares their phone number through Telegram's contact button, then creates a business by typing its name or joins one with an invite code.
  • A home screen — business, role, today's appointment count, bookings awaiting confirmation and the next client, with a button for every section.
  • Inline navigation — paged screens for today's, upcoming and pending appointments, clients and their history, services, team, reviews, schedule, waitlist and stats for today, 7 or 30 days.
  • One-tap status changes — confirm, cancel, complete or mark a no-show, including straight from a new-booking notification.
  • Several businesses — a switcher for people who work at more than one organization, and a menu button that opens the full dashboard as a Mini App.
  • Business claims — a "Connect Telegram" link on the claim page binds the chat to the claim; status updates arrive in the bot, and photos or PDFs sent to it attach to the open claim.

The AI assistant in chat

Free text outside a flow goes to OrganizationAssistant, the same agent behind the dashboard chat. Built on Laravel AI, it has tools for appointments, availability, clients, services, staff, schedules, branches, reviews, business stats and a knowledge base, so "move my 2pm to 4pm" or "who are my top clients?" become real tool calls. Model providers are tried in a configured failover order, so an overloaded provider hands over instead of failing the request.

Usage has three limits: a per-minute throttle per Telegram user, a daily token budget per organization and a personal cap inside it. Replayed history is windowed to bound cost, off-topic requests get a fixed reply, and answers go out as Telegram rich messages with HTML and plain-text fallbacks so they always arrive.

Claims with an AI first look

Most Bronjoy listings start as directory data from our business directory pipeline, so owners prove ownership with documents rather than a phone code. The bot accepts PDF, JPEG, PNG or WebP files up to 10 MB, and each document gets an automatic first read by a ClaimDocumentInspector agent that knows Uzbek and Russian registration and tax certificates. It exists because the first real claim arrived with a vehicle power of attorney labeled as a tax certificate. The check is advisory: a person decides, and an AI outage never blocks a claim.

Notifications that stay quiet

Every provider notification passes one dispatcher that applies fixed rules in order: organization policy, audience, recipient de-duplication, mutes, throttles, a burst guard, an hourly cap, quiet hours and coalescing. Nothing is sent inline; each decision writes a delivery row with a unique key, which gives idempotency and an answer to "why didn't I get a message?".

New organizations start with quiet hours from 22:00 to 08:00 in their own timezone, a daily digest at 08:30, at most 12 instant messages per person per hour with the rest folded into a "+N more" summary, and a 60-second window that merges repeat events. Critical events, such as a cancellation within 24 hours of the visit, skip quiet hours and the cap. Scheduled jobs flush held messages every minute, reclaim sends abandoned by a crashed worker and build digests in each organization's local time.

Our role

Staff notifications with Confirm and Decline buttons shipped with our first Telegram integration in January 2026. In June 2026 we rebuilt the bot into the full control surface described on this page.

See our Telegram bot development and AI integration and automation services. Customers book through the Bronjoy Telegram booking bot, and the Bronjoy AI receptionist hands calls to people through the same notification layer.

Let's Build

Want something like Bronjoy Staff Bot?

Tell us what your product needs to do. We'll shape the scope, map a timeline and send a fixed price — free, and with no obligation to proceed.

Free consultation No commitment Fast reply