Recent Posts



How To Roll-Out STOMT In Large-Scale Projects

Philipp ZentnerPhilipp Zentner

Especially as we talk to businesses with established product, we acknowledge that it’s hard to change a running system, or to introduce new products into the existing toolchain. When it comes to customer dialog or feedback, it becomes even more troubling. But that’s why we’ve built STOMT in the first place. Introducing new customer facing products or touchpoints, no matter of which kind always comes with new risks and concerns. In order to mitigate these, we want to explore some options to roll out STOMT in your large scale project or enterprise.

1. Channel traffic to your STOMT page

STOMT allows to integrate their simple feedback/wish form into almost any digital touchpoint. However, a real integration in the first place is optional. Instead, use the URL of your STOMT page and start placing it where it might matter and only appears to certain amount of people.


Simple ways to start channeling feedback:

There are many more simple, fun and creative ways to slowly start educating your customers regarding your new dedicated feedback channel. A great advantage hereby is that this requires basically no implementation effort.

1.1. Mitigate risk of being found by someone else: STOMT “secret” pages

Your normal STOMT page is public. However, enterprise customers are able to set their page to “secret”. That means only people that exactly know the URL of your STOMT page are able to find it. Since your page is secret, it won’t show up in the STOMT search, nor will it be indexed by search engines. Once you have set your page to secret, you can and should switch back to a public page at any time. However, this setting should only be used within the beginning of your STOMT journey.

2. Channel traffic to existing single stomts

It’s absolutely okay and welcomed to also use STOMT for your own ideas. We’ve collected almost all our ideas for STOMT on our page. Instead of prompting users to leave feedback, you can also start by asking people to discuss and vote a certain idea. You would just address a stomt to your own page and start sharing that specific wish via newsletter or on social media. We recommend to use an idea that is already on your roadmap though. Another idea is to encourage people of a small user group that already left feedback to share their ideas on social media in order to get more votes. That way you could easily create a competition.

Tip! Each stomt has an own Short URL. They help to share stomts in limited environments like Twitter. For enterprise customers, we also offer custom campaign Short-URLs. Just get in touch with us! As all Stomts get rendered as image, they play nicely as shared on social media channels.

3. Crowdsource & Poll via “Label-Links”

Each label has its own human-readable URL to share with the team and customers

Start collecting wishes for a specific topic. Labels have their own links, you can share a specific label feed with others. While your labels are non-public, your label-links are public by default. Label links can have a title and description which do not only help to give it a clear purpose within your company but also allow you to use it to communicate to the outside. That way you can start crowdsourcing wishes for a specific topic.

Adding title and description to a label and optionally display a STOMT form within the label-feed.

Wishes that are collected within your label feed, automatically get the label attached. After having collected massive amounts of feedback, you can then remove the label from worthless feedback and remove the creation form from the label. You can do that by unchecking the Stomt Form box.

Display STOMT form in label feed to collect specific feedback

You can use label feeds as backlog or polling or you can just add a STOMT form to it and collect wishes for a specific topic

After that you can send out the same link and just ask for comments and votes in oder to collect more data, numbers and engagement and make better and more community driven decisions. That is another way to get things started. Some people just create a contest out of their game or app by linking to a label-feed.

4. Passive touchpoint integrations

You can see a passive way to collect feedback on the right side of this blog. There is a feedback button to your right. People are not really prompted to give feedback. The engagement rate here is low as there is no real call-to-action used. However, with hundred thousands or millions of users, those low engagement rates may already result in an impressive amount of feedback. Please always make sure to comply with our branding guidelines. They help your users to recognize us and the implicated benefits in terms of simplicity and transparency. All of our integrations have customization options to better fit your corporate identity.

5. Use user-segment based and event-based integrations

All our touchpoint integrations provide opening and closing call-backs. The form can be trigged based on any logic you have in mind. An example logic would be: Only display the widget to people that spend more than 10 hours in the game, in the last week and spend at least $50 and are soon to finish the end game.

While in general we strongly recommend to collect feedback from anybody, always and at any time, this technique allows a slow roll out in large scale projects.

Tip! If you do this kind of user-segment triggering, make sure to also use the ability to attach labels and key-value data to the feedback. That way you collect feedback in context and can filter after it at a later point of time.

6. Embedded touchpoint integrations

We’ll keep it simple:

This is how an embedded version of a storm form looks like. You can do that with all of our integrations and reflects the most prominent way to collect feedback. We’ve an outstanding conversion rate of about 30% here!

Founder & Developer