Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a redirect option for success state in Webhook Form #3530

Open
kof opened this issue Jun 10, 2024 · 1 comment
Open

Add a redirect option for success state in Webhook Form #3530

kof opened this issue Jun 10, 2024 · 1 comment
Labels
area:components Parametrized code components complexity:medium Up to 1 week of work prio:2 Always look for prio:1 issues first before working on prio:2 type:feat Features and enhancements

Comments

@kof
Copy link
Member

kof commented Jun 10, 2024

As a designer, sometimes I want to show user a completely different page after submitting a Webhook Form instead of displaying an inline success message.

User case studiy:
https://discord.com/channels/955905230107738152/1249714434570453073/1249742312745996340

A little more about this specific case:

So the first page is a landing page for people to learn about our wedding venue. It is designed for New Users that dont know about our brand. It has content designed to help them learn about our wedding venue. It has a ton of information with the goal being - get the user to request a brochure by filling out a form. 

The second page is the page that has the form and more content focused on the user at this stage in the customer journey. Once you have read about the brand and decided that you want to download a brochure, your needs change. Thus the information on the second page is less about our brand and more general tips about wedding planning - things you would need to know once you start touring wedding venues. The goal of the redirect is to be able to provide 2X the value for users. But making the process streamlined so that it takes you less clicks to get the information you requested.

@kof
Copy link
Member Author

kof commented Jun 10, 2024

Maybe even form success/erorr should be events, just like many other events e.g. scroll or click and based on these events user could do a redirect or many other thigs, then its a future interaction story and not a form feature.

@kof kof added type:feat Features and enhancements prio:2 Always look for prio:1 issues first before working on prio:2 complexity:medium Up to 1 week of work area:components Parametrized code components labels Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:components Parametrized code components complexity:medium Up to 1 week of work prio:2 Always look for prio:1 issues first before working on prio:2 type:feat Features and enhancements
Projects
None yet
Development

No branches or pull requests

1 participant