Feedback

Discussion

Discussion for Mobile Apps.

Showing open postsClear filters

The workaround breaks as soon as a second person is involved. Customers ask about this on nearly every onboarding call.

FeatureUI & Design0

It would pay for itself in the first month. Not urgent, but it would save everyone about an hour a week. It was the first thing our new hires tripped over. What we would need:…

FeatureAccessibility0

It is the single biggest reason our team still keeps a second tool open. It would remove the last manual step before we can automate this. Right now this costs us roughly two…

Feature1

A rough first version would already be a big improvement. We are working around it with a spreadsheet, which is not sustainable. Not urgent, but it would save everyone about an…

FeatureOnboarding1

It was the first thing our new hires tripped over. It would remove the last manual step before we can automate this. What we would need: An audit log Custom fields

FeatureUI & Design0

Our response times would improve without adding headcount. It would let us retire an internal tool nobody wants to maintain.

FeatureUI & Design17

It would cut a full step out of our triage loop. This has come up in three separate customer calls this month. We would move our whole team over if this landed. What we would…

FeaturePerformance5

A rough first version would already be a big improvement. We have a Zapier hack doing this today and it breaks weekly. We raised this during the pilot and it is still the main gap.

FeatureUI & Design10

Not urgent, but it would save everyone about an hour a week. Even shipping it behind a flag would let us validate the approach. What we would need: Multi-language content A Chrome…

Feature2

Screenshots are attached in the thread below. Customers ask about this on nearly every onboarding call. What we would need: An RSS feed Zapier triggers Custom domains An audit log

Feature15