Telegram Bot Conversation Designer

Designs complete Telegram bot conversations: onboarding, scenario flows built on inline keyboards, real message copy, error recovery paths, and a command menu.

// prompt
You are a conversation designer specializing in Telegram bots: you turn business goals into dialogue flows that feel effortless and lean on Telegram's native UI instead of walls of text. Design the full conversation for a bot whose purpose is {{bot_purpose}}. **Parameters** - Bot purpose: {{bot_purpose}} - Target audience: {{target_audience}} - Key user scenarios: {{key_user_scenarios}} - Bot personality: {{bot_personality}} - Constraints: {{constraints}} **How to proceed** 1. Clarify what the user must accomplish in each scenario and what a successful outcome looks like — for the user and for the business behind the bot. 2. Design the onboarding: a /start message that explains the bot's value in two sentences, sets expectations, and leads to the first useful action within one tap. 3. Map each key scenario as a flow: user intent → bot steps → decision points → confirmation. Prefer inline keyboards and buttons over free-text input wherever the set of choices is finite. 4. Write the actual message copy for every step — no placeholders. Keep messages under 3–4 lines, one idea per message, with the personality applied consistently. 5. Design the unhappy paths: unrecognized input, a user changing their mind mid-flow, a payment or API failure. Every dead end needs a recovery message and a way back to the menu. 6. Define the command menu (/help, /settings plus scenario commands) and specify when the bot may message users proactively — sparingly, and always with an opt-out. 7. Flag every point where the flow depends on data or integrations the bot may not have, and list them as open questions for the developer. **What to deliver** For each scenario: a numbered flow outline with branches, then the complete message copy with button labels in quotes. Finish with a command summary table and a shortlist of edge cases the developer must handle before launch.
Fill in the variables
Example response

Scenario 1: Booking a table — conversation flow

Flow outline

  • User taps "Book a table" → bot asks for a date via inline calendar
  • Date chosen → bot shows available time slots as buttons
  • Time chosen → bot asks for party size (buttons 1–6, "More")
  • Confirmation card → user confirms, edits, or cancels

Message copy

Bot: Great choice! 🍝 When would you like to come in?
Inline calendar: next 14 days

Bot: Friday, March 12. Here is what we have:
Buttons: "18:00" · "19:30" · "21:00"

Bot: A table for how many?
Buttons: "1"–"6" · "More"

Bot: Confirming: Friday, March 12, 19:30, 2 guests. All correct?
Buttons: "✅ Confirm" · "✏️ Change" · "❌ Cancel"

Unhappy path: no slots available

Bot: Friday is fully booked — sorry! The nearest free evening is Saturday, March 13. Want to see those times?
Buttons: "Show Saturday" · "Pick another day" · "Back to menu"

Open question for the developer

Does the booking API expose table location (window/terrace)? If yes, add one optional step after party size.

Related prompts

Social Media & Communication

Telegram Channel Content Plan Builder

Builds a 30-day Telegram channel content plan with pillars, post formats, opening hooks, interactive posts, and CTAs designed around forwards and notifications.

Social Media & Communication

YouTube Video Title & Description Optimizer

Generates click-worthy, keyword-optimized YouTube titles, descriptions, tags, and thumbnail ideas to maximize search reach and CTR.

Social Media & Communication

Instagram Content Calendar Creator

Builds a strategic 30-day Instagram content calendar with post types, hooks, hashtags, and CTAs.

Social Media & Communication

Instagram Story Engagement Booster

Generates five interactive Instagram Story concepts engineered to maximize taps, replies, and shares.