x
Alumni

Feature requests? Read these best practices!

Got a request for a Square feature? You’ve come to the right place!

 

Before diving in, we suggest you read through the life cycle of a feature request so you have a better understanding of how these requests work.

 

Here are some best practices for posting a clear & easy-to-follow feature request:

 

  1. Title your request in a short, succinct manner with the following convention: “[Insert Product] [Insert Feature]
  2. Clearly share how you envision this feature would work
  3. Articulate why this is needed for your business/use case
  4. Share any pain points this new feature would alleviate

 

Here are a few examples of well written feature requests:

Appointments Feature Request - $$ Projections

Invoice Template Feature Request

Feature Request: Universal payment link

 

What if you come across a feature request that you strongly endorse, but no action has been taken on it recently?

 

  1. Feel free to ask for an update. Our team follows up to see if there is any new information to share with the community.
  2. Add your voice! Please include why this feature request is useful to your business, including any pain points that currently exist, how this feature would resolve them, and how you would like this feature to work. Anything we can share with the responsible team is helpful!

 

We do share these posts with our product teams and many of them read your comments too, so rest assured - your posts are read!

 

If a feature request is implemented, we post in the community once the feature is live with the update.

 

*Note: Comments that don’t add new information (use cases, pain points alleviated, etc.) may be moderated to keep feature requests organized and easy to navigate.

 

Happy Requesting!

1,952 Views
Message 1 of 1
Report
0 REPLIES 0