Check the acquisition promise
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗Incident IQ, LLC · iOS
Explore the ad evidence, study the storefront, and build your next acquisition hypothesis.
01 / Creative research
Read the store headline, screenshots and description. What problem is the app promising to solve?
Study the storefront ↗Explore apps with direct store-link matches. Compare their hooks and formats without assuming the same approach works here.
Browse observed advertisers ↗Store rankings and revenue estimates describe market context. They do not establish ad spend, conversions or ROAS.
Review the market context ↗02 / Storefront & product
Study the product story and store experience behind the acquisition funnel.
03 / Market context
Keep revenue, downloads and store rankings separate from advertising performance.
This is the worse ticketing app I’ve ever worked it. App crashes just about weekly and I have uninstall and reinstalled. Other team members have same experience. Lots of functions are not available on app as they are when you login to their portal. Only reason I use it is because our org purchased it. When the app doesn’t work we begin to use Google and that at times has issues with the SSO and throws us into a login loop. Safari won’t let you take photos or attach files. Duck duck go seems to work better at times. We submit tickets to them and responses take a while.
Honestly? Pretty barebones compared to the web version. Resolving tickets and making comments work most of the time, which, granted, are the most necessary features. But a) it consistently has issues showing *just* my tickets, when my district always has at least 2-300 at any given time, b) it’s virtually impossible to find information on a particular user (oh, the teacher didn’t put her class number so you want to look it up? That’s too bad; we can show you literally everyone that has ever been in the system instead, and change it to their ticket if you accidentally tap on one), and c) most damningly, as an iPhone user who doesn’t have the ability to force stop the app (which would already be frustrating), I have to delete and reinstall this at least once a month just to make it functional again - which includes the joy of having to go through two-factor authentication. If I didn’t have to use this for work, I’d happily uninstall it and never look back.
We use iiQ at our school and for the most part we like it. However, this mobile app is horrendous and barely usable. It glitches out, it stops loading or reloading the pages; I constantly have to force quit the app. It’s not tailored towards agents’ workflow at all, and I would also never recommend to one of our users to use it. I think an app that allowed agents to easily work tickets could be game changing, but this is not it. There’s just many things you can’t do in the app that you can easily do in the web interface.
Incident IQ users can manage help tickets and work orders with Incident IQ Mobile. Empower teachers and building staff to submit help requests in seco...