Registration closes in 4 d 10 h 44 minAfter that, subscriptions and Stars can't be bought — only renewed by those already inside. 30% off all plans right now.Join now

Practical guide · August 4, 2026

A Telegram bot for requests, sales and bookings: how to set it up

A Telegram bot for requests, sales and bookings: how to set it up

A good AI auto-reply does not simply hand over information. It helps the person take the next step: describe their job, pick a service, send their details, book a meeting or get passed to a specialist.

Short answer. Set up a profile with topics like “Services”, “Price”, “Request” and “Booking”, add a system prompt that offers one clear next step after every answer, and connect Google Calendar if you need bookings. Hard decisions — discounts, refunds, changes to terms — go to the owner.

This is part of the guide “A free Telegram auto-reply: how to connect it without Premium”. This page is only about requests, sales and bookings.

What an auto-reply is really for

Compare two replies.

An ordinary one:

Yes, we offer that.

One with an action:

Yes, we offer that. To find the right option for you, tell me what you need and by when.

In the second version the person knows what to do next. That matters most in sales, bookings and support.

One answer, one next step

Do not offer a person several actions at once. Pick the one step that follows naturally from the conversation so far. For example:

A consultation lasts 45 minutes. To book, pick a time in the calendar.

To look into this, send me the order number and a screenshot of the error.

The price depends on the job. Describe briefly what you need.

This one needs a personal answer from the owner. They will get back to you.

That keeps the conversation clear and does not overload the person.

What the bot can lead to

The assistant can:

  • suggest a service and send its description;
  • help pick a plan;
  • compare several options;
  • clarify what the client needs;
  • send a payment link;
  • suggest filling in a form;
  • collect a request;
  • book a consultation;
  • offer a time through Google Calendar;
  • book a call, a meeting or an interview;
  • send a catalogue, a deck or a price list;
  • ask for a name and contact details;
  • clarify budget and deadline;
  • ask for documents to be uploaded;
  • ask for an order number;
  • ask for a screenshot and the error text;
  • send an instruction;
  • pass the conversation to a manager or specialist;
  • pass a proposal to the owner;
  • point to the right page;
  • help place an order;
  • close an irrelevant conversation politely.

There is no fixed list. The behaviour you want is set in the system prompt, the FAQ, the facts and the profile's material.

Setting up a profile for requests

Topics and roles

Services

Price

Request

Budget

Deadline

Booking

System prompt

You are the company's assistant. Answer questions about our services and collect the information needed for a request. Use only confirmed details from the knowledge base. If the job is unclear, ask one clarifying question. Never promise a price or a deadline that is not in the material. After answering, offer one next step: describe the job, give a deadline, or move on to booking.

FAQ

How much does the work cost? The price depends on the job. Describe briefly what you need.

What do you need for a quote? Describe the job, the result you want and your deadline.

How do I book? Pick a time that suits you in the calendar.

Selling a service: an example

The client asks about the price
The assistant clarifies the job
It uses details from the knowledge base
It offers a fitting next step
It helps move to booking or payment

If the price depends on the job, the assistant must not pick a number at random. A good answer: “The price is confirmed once we know what the job involves. Describe briefly what you need.”

Collecting a request: an example

The person describes the job
The assistant asks for the missing detail
It collects the deadline or the format
It explains what happens next
It passes the prepared request to the owner

Instead of a long form in one message, the assistant can collect the details one question at a time:

Describe the job briefly.

After the answer:

What result are you after?

Then:

Do you have a deadline in mind?

There is no need to ask everything at once if that makes the message too heavy.

Technical support: an example

The person reports an error
The assistant clarifies the problem
It asks for the order number and a screenshot
It finds the instruction in the documents
It offers a solution
If needed, it passes the case to a specialist

Here the target action is not a sale but collecting what is needed to solve the problem.

Booking a consultation: an example

The person wants a consultation
The assistant clarifies the topic
It states the confirmed terms
It offers a free slot or a calendar link

A profile can be connected to Google Calendar. Before going live, check:

  • the time zone;
  • which hours are available;
  • the schedule;
  • the booking link.

A partner enquiry: an example

A partner proposes working together
The assistant clarifies the format
It collects the key information
It explains what happens next
It passes the proposal to the owner

The assistant must not decide on a partnership by itself unless the system prompt allows it.

Handing the conversation to a manager or the owner

A handover is needed when:

  • a personal decision is required;
  • the knowledge base has no exact answer;
  • the person asks to change the terms;
  • a discount or refund needs confirming;
  • the problem is not solved by the instructions;
  • a partnership proposal needs judgement.

An example rule:

Never confirm discounts, refunds or changes to terms. Say that the owner will decide.

An example reply:

This one needs the owner's decision. I will pass the details on and they will answer personally.

How to test a scenario

Try:

  • a question about price;
  • an overly vague request;
  • someone ready to book;
  • a request for a discount;
  • a technical error;
  • a partnership proposal;
  • a question with no answer available;
  • someone declining to continue.

Check that the assistant:

  1. picked the right profile;
  2. does not offer unnecessary actions;
  3. asks only one clarifying question;
  4. promises nothing unconfirmed;
  5. uses the right document or FAQ entry;
  6. hands the conversation over when it should.

The full checklist before switching a profile on is in the article “Testing an AI auto-reply before launch”.

Ready to try it on your own scenarios? Open @Head_Hack_bot and set up a profile for requests, sales or bookings.

In short

Setting up sales, requests and bookings comes down to one principle: every answer should help the person take a clear next step. Fix that step in the system prompt, the FAQ and the profile's scenarios, and send the hard decisions to the owner or a specialist.