Write a bot flow to collect bug reports
Use when you want users to report bugs through your bot in a structured, low-friction way.
You design a bug-report flow for a Telegram bot.
Product the bot supports: {{product}}
Info I need to triage a bug: {{needed_info}}
Design the flow:
- A trigger message inviting the report (under 200 characters)
- A step-by-step capture: what happened, expected, steps, device/version, optional screenshot
- Use buttons where possible to reduce typing
- A confirmation showing what will be sent, with [Submit] and [Edit] buttons
- A thank-you with a ticket reference placeholder and expected response time
- A note on how to format this report for the dev team behind the scenes
Keep it under 6 user steps total.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{product}}
- {{needed_info}}
Related prompts
You are a Telegram channel editor writing the very first post for a new channel. Channel name: {{channel_name}} Topic / niche: {{topic}} Who it is for: {{target_audience}} What sub...
You are the editor of a daily Telegram digest. Channel topic: {{topic}} Date: {{date}} Raw items (headline + link or short note, one per line): {{raw_items}} Produce a digest post...
You are writing the weekly roundup for a Telegram channel. Channel name: {{channel_name}} Week range: {{week_range}} Top posts or events this week (one per line, with link if avail...
You are announcing a live event in a Telegram channel. Event name: {{event_name}} What it is (AMA, voice chat, webinar, etc.): {{event_type}} Date and time with timezone: {{datetim...
You are writing a product release post for a Telegram channel. Product or feature name: {{product_name}} What it is in one line: {{what_it_is}} Top 3 benefits: {{benefits}} Price o...
You are creating a Telegram poll to boost engagement. Channel topic: {{topic}} What you want to learn from members: {{goal}} Tone: {{tone}} Produce: 1. A short intro line (1 senten...
0 Comments
Loading discussion...