Contact
Partnerships, integration ideas, product feedback, or "how do I do X in the cabinet" — drop us a line. Already a customer? The fastest path is /support in our Telegram bot — it routes your message straight to the team with your account context attached.
Already a customer? Open @fastwebcontactbot in Telegram and send /support — your message lands in our ops chat tagged with your account, the site you were working on, and any deploy context. From the cabinet, the Contact support buttons in Deploy console / locked-target panels do the same in one click.
Not yet? The form below works too — same inbox, just without the auto-attached account context.
What's a good fit
- Partnership ideas — agencies, affiliates, brand-catalog additions.
- Feature requests — wizard tweaks, locale support, template work.
- Cabinet questions that the docs don't cover yet.
- Bug reports — include the site id + a short repro.
What we'll reply with
- Same-day reply on Telegram during EU business hours.
- Email turnaround within one business day.
- If there's something concrete to ship, we'll link the commit or roadmap line.
- If it's "out of scope today", we'll say so — and tell you what'd unblock it.
Start the conversation
A short note is enough. Email is required so we can reply; Telegram is optional — include it if you'd rather chat there than over email.
FAQ
Do I need a polished proposal?
No. A short note is enough — who you are, what you're building, what overlap you see. We're happy to start from a rough idea.
Can I just ping the bot directly?
Yes — open @fastwebcontactbot and send /support. The bot prompts you for a one-message description, then routes it to our ops channel tagged with your Telegram identity (and your account context if you've linked Telegram to your generator.ink login). We reply in the same bot thread.
Bug report — what should I include?
Your site id (the slug in the cabinet URL), a short repro ("clicked X on page Y, expected Z, saw W"), and a timestamp if it was a one-off. We'll grep logs from that.