Client guide

Store.tg Client Documentation

This guide explains how to manage a Telegram sales or booking bot after the initial setup. It is written for owners and operators, not developers.

Login and workspace

Example screen

Login and workspace

Email
Password
Log in
Demo owner
What the customer or operator should see at this step.

Open the builder login page, enter the email and password provided by the Store.tg team, then choose the bot you want to manage.

The workspace shows project status, token status, runtime publication state, and quick access to project creation.

Demo buttons fill the login form for test accounts only. Production accounts should use their own credentials.

Builder sections

Example screen

Builder sections

Overview
Screens
Modules
Catalog
Booking
Support
What the customer or operator should see at this step.

The builder is split into focused sections: Overview, Screens, Settings, Modules, Catalog, Orders, Booking, Support, Activity, and Team.

Disabled modules are hidden from the working menu so the interface stays compact for the current project.

Screens, text, and navigation

Example screen

Screens, text, and navigation

Start page
Message text
Media
Keyboard rows
Inline buttons
What the customer or operator should see at this step.

Screens are the messages the customer sees in Telegram. Each screen can have a title, trigger command, message text, media, reply keyboard buttons, and inline buttons.

Buttons can open another screen, start catalog, start booking, or open support depending on enabled modules.

  1. 1Open Screens.
  2. 2Select the page in the left tree.
  3. 3Edit the title, command, message, media, and buttons.
  4. 4Wait for autosave.
  5. 5Publish runtime.

Photos and videos

Example screen

Photos and videos

Media type
Upload file
Public URL
Publish runtime
What the customer or operator should see at this step.

A page can include a photo or video. The easiest option is Upload file. Store.tg saves it on the server and generates a public media URL for Telegram.

You can also paste an external HTTPS URL or Telegram file_id if you already have one.

Images up to 10 MB are supported. Videos up to 50 MB are supported. Use clear product or service visuals, not abstract backgrounds.

Button layout

Example screen

Button layout

Rows: 2,1
Book
Services
Ask a question
What the customer or operator should see at this step.

Reply keyboard and inline buttons support row layout. Use the Rows field to control how many buttons appear on each row.

Examples: 1 means one button per row, 2 means two per row, 3 means three per row, and 2,1 means two buttons on the first row and one on the next row.

After changing button layout, publish runtime and test with a new /start message. Old Telegram messages are not automatically redrawn.

Catalog and orders

Example screen

Catalog and orders

Product title
Price
Payment instruction
Orders
What the customer or operator should see at this step.

The catalog stores products, prices, descriptions, payment instructions, delivery type, stock mode, and fulfillment settings.

Orders are created from Telegram and appear in the Orders section where operators can confirm payment, fulfill, cancel, and review customer history.

Booking and calendar

Example screen

Booking and calendar

Service
Date
Time slot
Requests
Confirm
What the customer or operator should see at this step.

Booking lets customers select a service, date, and time slot directly in Telegram. Operators receive booking requests in the builder.

You can configure services, staff, working days, day start/end time, slot step, and reminders.

Support and operators

Example screen

Support and operators

Ticket
Customer message
Internal note
Operator reply
What the customer or operator should see at this step.

Customers can open support from the bot. Operators see tickets, files, messages, priority, status, and assignment in the builder.

Use internal notes for team context and operator replies for customer-facing messages.

Saving and publishing

Example screen

Saving and publishing

Saved to backend
Can publish
Publish runtime
Test /start
What the customer or operator should see at this step.

Autosave stores the draft in backend. Telegram uses the published runtime, so draft changes are not live until you publish runtime.

If the bot does not reflect a change, check that landing was redeployed, the draft says Saved to backend, and runtime was published.

Need help launching?

Send the Store.tg team your offer, payment flow, and desired launch date. We will suggest the fastest setup.

Message on Telegram