Bot settings

The "Settings" section (the gear icon in the top bar) covers data, monetization, and access rights — unlike "Messages", where the dialogue logic lives.

Fields

Data the bot stores about a subscriber, which you can reference in message text via @field_name. Created by default: id, first_name, last_name, username, avatar, email, phone_number.

When creating a new field you pick one of 12 data types, plus two toggles — Unique field (the value can't repeat across two subscribers — handy for promo codes/order IDs) and Global field (the value is shared across all subscribers rather than being individual): String (up to 255 chars, extended comparisons in segments), Text (up to 4095 chars), Number, Date, Email, Phone, Attachment, Photo, Photo collection, Audio, Video, File.

Tags

Labels for grouping subscribers — assigned manually or automatically (through the "Add tag" action in messages and buttons). A tag has its own color (for visual distinction in the CRM) and a "Limit duration" toggle — the tag is automatically removed from the subscriber after a set time (handy for labels like "Waiting for reply 24h"). The section also shows tag analytics. "Has tag" can be used as a condition in a segment.

Segments

A segment is a set of conditions; if a subscriber matches all of them, they land in the segment automatically. Segments are used in broadcasts, message-sending conditions (the "Scenarios" topic), and action conditions. There are 20 condition types available: Bot subscription date, Subscribed via a landing page, Received a message, Going through a scenario, Clicked a link, Clicked a button, Field comparison, Has tag, Made a payment, Has an active subscription, Assigned to a manager, Booked an appointment, Opened an article, Answered a survey, Is a group/channel member, Invited referrals, Specific date, Specific time, Specific day of the week, Segment trigger probability, Nested condition.

"Segment trigger probability" is a rare but handy one for A/B tests: you can send 50% of a segment one message and the other 50% a different one, without manually splitting the base.

The "Answered a survey" and "Invited referrals" conditions reference mechanics that don't have their own clearly labeled section in the interface — a "survey" is assembled out of a regular message with a keyboard/list button plus "Data to save", and referral links aren't exposed as a separate builder at the interface level. If you specifically need a referral program, check with TvoyBot support on how it's implemented on your plan.

Landings

Separate pages/links for subscribing to the bot — traffic from different landing pages can later be distributed into segments (the "Subscribed via a landing page" condition) and viewed separately by geography. Every new landing page immediately gets its own pair of links (a short one, i.tvoybot.com/tg/..., and a direct one, t.me/YourBot?start=...), plus an "Open editor" button — a visual builder for the subscription page itself. The bot already has a "Main landing" by default, created when you created the bot.

Inside the editor is a WYSIWYG builder: a "desktop/mobile" toggle to preview responsiveness, and every block on the page (avatar, bot name, the "Open in Telegram" button) has its own mini settings panel via a gear icon. Clicking a text block brings up a formatting toolbar — bold, italic, strikethrough, underline, link, font size and color, background color, emoji, lists, quote.

Content

Tabs for Attachments (files you can attach to messages — with a usage counter, plan limits, a type filter, and a "Cloud storage"/"messenger storage" filter) and Articles (long-form pieces opened via the "Article button").

Shop

Three tabs:

• Products — a product card has four blocks: Product info (name, description, image), Payment settings (integration, currency, price, discount, restricting payment to a segment only), Seller details (a link to the agreement/offer, a terms article, business name, email, phone — the legal minimum required to accept payments) and Post-payment actions (the same action builder: assign a tag, continue a scenario, etc.). Every product immediately gets its own payment page like i.tvoybot.com/product/…, and its button is added to a message via "Buy product"
• Subscriptions — recurring payments; a subscriber can see and cancel access via the "Subscriber's account" button
• Integrations — connecting a payment aggregator. Supported: Prodamus, Tinkoff, Robokassa, YooKassa, YooMoney, Fondy, Fanspay, Stripe, bePaid, Lava, Telegram Stars, CryptoCloud, ClickUz, Payme, CryptoBot, NOWPayments, Tochka, ExpressPay, Ozon, AlfaBank — including cryptocurrency. If the aggregator you need isn't on the list, you can request it from support

Access

This is about managing the bot itself, not its subscribers:

• Change token — if the Telegram bot's token was reissued
• Change language of the bot
• Change domain
• Delete bot (irreversible)
• Add a user — invite team members with a role that restricts which sections they can access (e.g. a manager only sees "Chat", not "Access")