You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a potential user, I see the locked features, they sound appealing, but I have no idea how they work, would be great if I can get individual sales docs.
When is very clear for the user what he gets ( for e.g google spreadsheet sync every hour)
When is a new feature that the user didn't experience ( Database query e.g)
In 1) case we can use direct CTA, like BUY NOW
In 2) case we can use something like Learn More / View Details
Both would direct users to the landing page where we should make sure those features are explained(major ones), just that the suggested approach, won't scare people like the current one: "BUY NOW" where I have no idea about what I am buying.
The text was updated successfully, but these errors were encountered:
For dev changes, we could simply add a "learn more" button on the left of the buy button, like this:
You can make it a standard grey button (not red). This will be contain a target=_blank link to the relevant documentation that I've created above for the three related features.
Description:
As a potential user, I see the locked features, they sound appealing, but I have no idea how they work, would be great if I can get individual sales docs.
https://www.dropbox.com/s/uhyck95yl5p489x/Screenshot%202020-06-12%2019.49.14.png?dl=0 here the message can be: Upgrade to PRO to get this feature, learn more about how it works. They can be super minimal, text/gif, or 30sec video.
Alternatives:
I see 2 upsell scenarios 👍
In 1) case we can use direct CTA, like BUY NOW
In 2) case we can use something like Learn More / View Details
Both would direct users to the landing page where we should make sure those features are explained(major ones), just that the suggested approach, won't scare people like the current one: "BUY NOW" where I have no idea about what I am buying.
The text was updated successfully, but these errors were encountered: