Feedback

Discussion

Discussion for Mobile Apps.

Showing planned postsClear filters

We are working around it with a spreadsheet, which is not sustainable. A rough first version would already be a big improvement.

Feature0

This blocks the quarterly report we send to the exec team. It would remove the last manual step before we can automate this.

FeatureOnboarding17

Not urgent, but it would save everyone about an hour a week. The workaround breaks as soon as a second person is involved. This is table stakes in every competing product we…

FeaturePerformance0

We have a Zapier hack doing this today and it breaks weekly. Screenshots are attached in the thread below. This blocks the quarterly report we send to the exec team.

FeatureAccessibility10

It would let us retire an internal tool nobody wants to maintain. It is the single biggest reason our team still keeps a second tool open.

FeatureUI & Design14

Our response times would improve without adding headcount. Our support volume would drop noticeably if this shipped. This is the difference between a nice-to-have and a daily…

Feature0

Our response times would improve without adding headcount. Our ops team has a runbook step purely to work around it. Customers ask about this on nearly every onboarding call. What…

Feature7

It would pay for itself in the first month. Two people on the team have independently asked for this. We hit this every Monday during the weekly review.

Feature2

The current flow takes six clicks; it should take one. Right now this costs us roughly two hours a week. Our ops team has a runbook step purely to work around it. What we would…

Feature2