Skip to content
Chatbots

An AI bot that doesn't just answer customers — it resolves their issues

The bot answers guests and shoppers in Telegram, WhatsApp, Instagram and on your website — around the clock, from your instructions, with nothing made up. A complaint becomes a task for the location manager, a booking becomes a request, and once the issue is fixed, the bot lets the customer know.

How to set it up — help center guide →

Highlights

01

Answers by your rules

The bot knows only what you have opened to customers in your instructions: menu, prices, policies, delivery. No answer? It says so honestly and calls an employee.

02

Does the work, not just forwards it

A complaint becomes a task for the right location's manager with the customer's photo, a booking becomes a request, an order question becomes a query to your CRM.

03

People always close by

Every chat lands in one Conversations inbox. Employees see why the bot answered the way it did and step in with one click.

Why it matters

A customer writes at 11:40 pm — and nobody is there to reply

Messages arrive in three messengers and on the website, front-of-house staff reply in between other tasks, complaints get lost in chats, and the location manager learns about the problem from a review on the map. A typical button bot doesn't help: customers write in their own words.

The usual way

  • A reply an hour later — or the next morning if they wrote in the evening
  • A complaint on Instagram that the location never hears about
  • The same questions about prices and opening hours a hundred times over
  • The customer never finds out whether the problem was fixed

With jeCheck

  • A reply in seconds, 24/7, in the customer's language
  • A complaint instantly becomes a task for the location manager
  • The bot handles frequent questions, people handle the complex ones
  • The bot tells the customer when everything has been fixed
Chatbots

Features

Telegram, WhatsApp, Instagram, website

Your own Telegram bot in a minute, the official WhatsApp Business, Instagram Direct and a website chat window with a single line of code.

Knowledge from instructions

The bot answers from Instructions folders open to customers and from quick replies. It can't see internal procedures.

Scenarios in plain language

"If a customer complains, apologize, ask for the location and time, log the complaint." AI drafts a scenario from your own description.

Actions in the system

A task for a location, a request into an approval process, a notification to staff, a conversation label, a query to your CRM via API.

The Conversations inbox

All channels in one window: "Awaiting reply", "Mine", passing to a colleague or department, notes, quick replies, AI suggestions.

Quality and gaps

Share resolved by the bot, reasons for handoffs to people, customer ratings and a list of questions the bot doesn't know the answer to.

Closed loop

Customer complaint → task for the location → "we fixed it"

The bot apologizes, clarifies the location and details, summarizes the complaint and, with the customer's consent, creates a task for the manager — with photos, phone number and a link to the conversation. When the manager closes the task, the bot writes back to the customer with the outcome. Instead of ending up as a review on the map, the complaint turns into a fix.

  • A task for the right location: the manager, a position or a department
  • Customer photos are attached to the task automatically
  • Deadline and priority come from the action settings
  • The customer gets a request number and a message once it's fixed
  • Requests into Processes with an approval route
  • Queries to your CRM: order status, bookings, loyalty points
Inbox

The bot does the work, people step in when needed

The bot hands a conversation to an employee when it isn't sure, the customer asks for a person or gets angry — and says why. The employee sees the whole chat, the sources behind the bot's answers and a customer card across all channels, then replies or hands the conversation back to the bot.

  • Views: "Awaiting reply", "Mine", "With staff", "Bot handling"
  • "Why this answer" — the bot's instructions and actions
  • AI suggestions and quick replies for staff
  • One customer across all channels — matched by phone
  • Permissions by location: managers see their own conversations
  • A 1-to-5 conversation rating after closing

How it works

  1. 1 Create a bot

    From the "Guest support" or "Requests and bookings" template — with a ready-made complaint scenario.

  2. 2 Open up knowledge

    Customer-facing instruction folders and quick replies to frequent questions.

  3. 3 Test it in the sandbox

    Write as a customer and follow the bot's reasoning — no tasks are created.

  4. 4 Connect channels

    Telegram, WhatsApp, Instagram or website chat — and the bot starts answering.

Frequently asked questions

The bot answers only from the instructions you have opened to customers and from quick replies. If there is no reliable answer, it says so and offers to connect the customer with an employee. Such questions are collected in the "What the bot doesn't know" list — add an answer and the bot will start using it.

Telegram (your company's own bot via @BotFather), the official WhatsApp Business via the Cloud API, Instagram Direct for a professional account, and a chat window on your website. All conversations are collected in one inbox.

Yes. It uses the official WhatsApp Business Platform. Meta's rules only prohibit general-purpose AI assistants, while a company's customer support bot is a permitted use case. Replies to a customer within 24 hours of their message are free.

In the customer's language: Russian, Kazakh, Uzbek, English and others. Your instructions can all be in one language.

The bot hands the conversation to staff with the reason, and the customer is told they'll get a reply right there. Employees get a notification and the conversation appears in "Awaiting reply". Outside working hours, the bot warns that someone will reply in the morning.

Yes — with the "External system request" action: the bot calls your API over https, for example to check an order status or available time slots. Keys are stored encrypted.

Chatbots are included in the Network plan with a monthly allowance of AI conversations. A conversation counts once, no matter how many messages it has. When the allowance runs out, the bot doesn't go silent — new conversations go to employees.

Run your first audit today

Sign up in a minute, start from ready-made checklist templates and use the mobile app right away. No card, no months-long rollout.

Message us on Telegram