Lead capture template: name, phone and a request email

Three blocks and a request email

The flow is short on purpose: a “Message” explaining why to leave a contact → a name “Data collection” → a phone “Data collection” with format validation → a “Message” “Thank you, {{name}}!”. The trigger is /start; for a VK community or a website add an “Any message” trigger so the flow starts with the client’s first phrase.

The request appears in “Contacts” (a card with the phone), in “Conversations” and in the owner’s mailbox — an email about a new request goes out on the first saved phone or email. The format error text and the number of attempts are set in the “Data collection” block; two attempts are enough. How the whole flow works and which fields to ask for in what order — in the article a bot for collecting requests.

How to strengthen it: source tag, deal, operator

Three additions that turn the form into a working request channel.

• Source tag. The deep link https://t.me/ваш_бот?start=site_footer → the “Deep link” trigger → “Action → add tag” src:site_footer. A month later “Contacts” shows where requests come from.
• “Action → Deal in CRM” after the phone: title “Request: {{name}}”, stage “new” — a card on the kanban board in the “CRM” section. For amoCRM or Bitrix24 — an “HTTP request” to Make or n8n; a comparison of options is in the article leads from a bot to CRM.
• An “Operator” block at the end, if a manager should reply in the same chat: the conversation gets the “operator” status and the team gets a Web Push.

One flow for all channels — Telegram, MAX, VK and the website widget. If the request needs qualifying rather than just collecting, take the “Quiz bot”. Open the template in your account.