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 4 of 39 templates.
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.
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.
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.
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.