What is included

  • A written dialogue: questions, branches, and the stop conditions
  • Delivery to a staff chat, with enough context to answer
  • Storage for the fields you actually need later
  • Deploy on a server you control, plus the bot token handover
  • A narrow first version, with a named place to grow after real use

How the work goes

  1. Write one happy path as a chat, in plain messages
  2. Add the exceptions: cancel, reschedule, unknown question
  3. Build that path and run it with your own staff
  4. Only then add payments, CRM, or extra roles

When another format fits better

A constructor bot you will keep editing in a visual builder, or an “AI employee” that is supposed to replace a process you have not written down. If the screen is the product — a catalog, a calendar, a board — that is a Mini App, and the bot is only the door.