Waitlist
Clean, white, no fluff
Minimal — email only
A single title, subtitle, and email field on a white card. Use when you want zero visual distraction and the brand to come from your own marketing site around it.
minimalminimal
Example flows you can actually use.
Pick a flow type, preview a working example, then copy the config or open it in your dashboard. No maze of filters, just the useful starting points.
Showing 40 of 40 templates.
Waitlist
Hero + 3 bullets + form
Feature tease
Big hero copy with three short value props underneath. Best when you have specific things to brag about and want to convert curious visitors into signups.
gradientlaunch
Waitlist
Dated eyebrow + dark hero
Launching soon
Big bold launch announcement with a date. Good for product reveals where the date itself is the story.
darklaunch
Waitlist
Founder rate + premium bullets
Pro upsell
A waitlist for your paid tier. Highlight what's locked behind it and offer the people on the list a permanent founder discount.
side-by_sideupsell
Waitlist
Invite-only with use-case ask
Private beta
Positions access as a privilege, not a freebie. Use the legal/subtitle area to ask people what they'd build with it — the highest-signal ones get invited first.
minimalbeta
Waitlist
Editorial dark hero with inline form
Beta invite — dark + serif
A product-reveal vibe — dark hero, serif display headline, accent-tinted eyebrow, and a single-pill email+button on desktop that stacks on phone. Best when you want the page itself to feel premium.
darkbetalaunch
Waitlist
Skip the line by inviting friends
Early access — referral
Shows your spot in line on the success screen and prompts the user to share. (The renderer reads the current waitlist size from the public counter so the social-proof line stays honest.)
gradientreferrallaunch
Waitlist
Email + custom fields
Beta — with qualifying fields
Collect more than an email at signup: a handle, a yes/no qualifier, and a use-case dropdown — so you can prioritise who gets in. Every extra field is optional or required as you choose, and the answers land with each signup and in the CSV export. Embeds the same way.
darkbeta
Wishlist
Categories + moderated lifecycle
Public roadmap
The full board: visitors suggest features and upvote, tagged into feature / improvement / integration. New ideas wait in a pending queue until you approve them, then move through Open → Planned → In progress → Shipped. The default when you want a transparent, public roadmap.
roadmap
Wishlist
Email-gated, for a known cohort
Private beta board
For a closed beta where every voice should be attributable. An email is required to submit, vote, and comment — so duplicate votes are deduped on the person, not the browser. Fewer, sharper categories and a dark hero that reads like an insider channel.
beta-board
Wishlist
No categories, posts instantly
Open suggestion wall
The lowest-friction board: no categories, no approval queue — ideas post straight to the wall and start collecting votes immediately. Best for small apps that want momentum and visible activity over tight moderation.
open-wall
Feedback
Stars required, text optional
Quick rate
The lowest-friction loop: a 1–5 star widget the user MUST pick, plus an optional textarea for context. Best after one-shot experiences — a tutorial, an export, an AI generation — where you want trend data first and qualitative second.
quick-rate
Feedback
Anonymous, text-only
Suggestion box
No stars, no email field. Just a single textarea that says "what's on your mind?" — the right shape when you want unfiltered raw thoughts and don't want users worrying about identification. Good fit for an in-app "Send feedback" link.
suggestion-box
Feedback
Recommend score + why
NPS pulse
Classic NPS shape: a required star rating (used as a 1–5 proxy for the 0–10 NPS scale — keeps the UI tap-friendly on mobile) followed by an open "why" textarea, plus an optional reply-to email so you can chase the promoters who left specifics.
nps
Feedback
Required rating + email
Beta-channel pulse
For private beta cohorts you can identify. Star rating required, email required, longer textarea prompt asking what's broken vs what's working. Pair with a TestFlight build so every signal carries a contactable identity.
beta-pulse
Report
5 buckets, broad coverage
General report
The default "report a problem" shape — bug / abuse / spam / privacy / other. Five categories is small enough that triage is fast but wide enough that almost nothing gets shoved into "other". Best as the universal entry point linked from a settings menu or help screen.
general
Report
App-Store-style abuse buckets
Content moderation
Designed for surfaces with user-generated content — comments, posts, profiles. Categories mirror App Store Connect's report taxonomy so what you collect lines up with what review boards expect. Email is OPTIONAL by default — reporters often want anonymity.
content-moderation
Report
Engineering-grade reproduction
Bug triage
For technical apps where reporters can describe what they tried. Categories split by impact (crash / wrong-result / slow / visual-glitch) so engineering can route by severity. Email is REQUIRED — bug triage almost always needs a follow-up question.
bug-triage
Report
Buyer/seller, fraud-aware
Marketplace safety
For apps with transactions between users. Categories cover the marketplace failure modes — fraud, scam listings, no-show sellers, payment issues — plus a counterparty contact info ask in the prompt. Email required; we'll need it to investigate either side.
marketplace
Contact
Email-first, message optional
App Store contact
The shape we recommend for the App Store "Contact Developer" link. Email required (it's how you'll respond), name optional, message optional — a lot of users only want to flag "can you reply about X?" without explaining yet. Friction at a minimum.
app-store
Contact
Lead capture, message optional
Sales inquiry
Use on a marketing page's "Talk to sales" CTA. Required name + email so the rep can address the lead and follow up; message is encouraged but not required (some leads just want a callback). Pair with a CTA URL in the success state pointing at a Calendly to convert the eager ones.
sales
Contact
All three required
Press & media
For a press@yourapp.com inbox where every inquiry needs context to be actionable. All three fields required — name (so the response can be addressed properly), email (the reply channel), message (the actual ask: interview, quote, asset, etc.). Dark theme for visual gravitas; pair with a Calendly-style press kit link.
press
Contact
Informal, all three fields
Talk to founder
The "reach me directly" CTA you put on the about page or in a launch post. Name required ("hi <name>" is a better reply), email required (only channel), message required (no point pinging the founder with nothing to say). Tone is warm and personal, not corporate.
founder
Onboarding
Personalize, then capture
Quiz funnel
The Cal-AI / Noom shape: a few tap-to-answer questions that make the user feel seen, an info screen that reflects their answers back, then an email capture and the App Store handoff. Best when personalization is the hook.
quiz
Onboarding
One question + email
Lean capture
The fastest path from a paid ad to an install. A single qualifying question, an email field, done. Minimizes drop-off when traffic is cold and you just want the email + the App Store tap.
lean
Onboarding
Build the pitch, then capture
Story sell
Three info screens that walk through the problem → the promise → the proof, then a soft email capture (skippable) and the handoff. Best for higher-consideration apps where the value needs explaining before the ask.
story
Referral
Symmetric reward
Give a week, get a week
The classic loop: the friend gets a free week for installing, and the referrer earns a free week for every friend who joins. Capped at 10 to prevent farming.
give-get
Referral
Referrer-only bonus
Reward the sharer
Only the person who shares earns a reward; the new user just gets the normal first-run experience. Simplest to message when you don't want to discount every new install.
sharer-only
Referral
Bigger rewards, higher cap
Generous
Two free weeks per side and a high cap — for high-LTV apps where an extra fortnight of access is cheap relative to a new paying user.
generous
Referral
Reward a custom unit
In-app currency
Grant your own in-app currency instead of free weeks — e.g. 100 drops to the friend and 100 to the referrer for every install. Your app reads the reward's amount + unit and credits the balance.
currencygive-get
Link page
App Store + socials in one link
App launch hub
The link you drop in an Instagram / TikTok bio: app logo + tagline, a row of icon buttons (App Store, website, X, Instagram), then a labeled list — what's new, support, and your waitlist. One short /p/{slug} URL that routes everywhere.
launch-hub
Link page
A tidy list of everything you ship
Creator links
A clean, minimal link list for a maker: newsletter, blog, the app, and a way to say hello. No icon row — just well-labeled rows with sublabels so each destination is obvious at a glance.
creator
Cancel
Discount + feedback + tutorial
Indie SaaS — save flow
Three top reasons get distinct responses: a discount for price, a feedback ack for missing-feature, an in-app tutorial deep-link for under-use.
open_offeropen_supportopen_featuremanage_subscription
Cancel
Collect a reason, nothing else
Feedback-only
Every reason ends on a thanks screen. No offers, no deep links — useful when you just want the data.
open_supportreturn_to_appmanage_subscriptionauto-advance
Cancel
One screen, one offer, done
Simple deflect
Skip the reason picker entirely — anyone who taps Cancel sees the same save offer. Fastest path; lowest signal.
open_offeropen_supportmanage_subscriptionauto-advance
Cancel
Several reasons at once
Multi-select signal
Lets the user pick *all* reasons that apply, not just one. No response screen — the click itself is the signal. Useful when you want the full picture rather than the top-of-mind answer.
return_to_appmanage_subscriptionmulti-select
Cancel
Different paywalls for different reasons
Paywall variant routing
Each reason opens a specific in-app paywall via open_premium + paywallId — 'too expensive' → save-monthly, 'annual too long' → quarterly, 'no team' → solo. The iOS app picks the right offer screen by id.
open_premiummanage_subscription
Cancel
Each reason opens a different inbox
Support routing with topics
Bug → bug-report support topic. Billing → billing inbox. Account → account team. Each open_support carries supportTopic + a prefilled message so the iOS support handler knows where to route.
open_supportmanage_subscription
Cancel
Send to a public web page
Win-back — external offer
Use external_url to point at a hosted save page (Notion, your blog, a Stripe Checkout link). The iOS app opens the URL in Safari — no in-app paywall to maintain.
external_urlmanage_subscriptionauto-advance
Cancel
Two offers, same reason
A/B save offer variants
Author two flows with different save offers (50% off vs 1 free month) and publish them under different secondary slugs (e.g. /cancel-a, /cancel-b). Point half your iOS app at each. Compare conversion in analytics.
open_offermanage_subscription