The notification falls back to the default admin recipient. Set that address to an inbox your team monitors.
The right inquiry.
The right inbox.
Send submissions to the people who can act on them. Route by a visitor’s answers, with a default recipient for everything else.
WHY IT MATTERS
One contact form. A clear destination.
A shared inbox works until every inquiry needs forwarding. Roolify lets you define who receives a submission based on the information in that form.
01
Route by the answer
Build notification rules around submitted field values, so sales inquiries and support requests can reach different recipients.
02
Include the right people
Set notification recipients with optional CC and BCC addresses. Customize the subject and HTML email body.
03
Give unmatched inquiries a home
When no routing rule matches, Roolify uses the default admin recipient. With no custom routing defined, submissions default to the account owner’s email.
Before you build.
Don't see yours?
Ask usBUILT FOR YOUR NEXT FORM
Give it a real
problem to solve.
Try your rules on a webflow.io site with the free plan. Move to a paid plan when you’re ready for a custom domain.
Try Roolify
Built for Webflow · Absolute control · Zero code.