FULL FABRIC prides itself in being a customer-centric company, and thus we put the focus on customer feedback. Feature requests are the main impetus for new developments, and for good reason – what better way to learn the needs of our clients than straight from the horse's mouth? 🐎 Moreover, there's always room for improvement! Read along to find out how to share your needs and suggestions with us!

In this article

(click to jump to topic)

➜ What defines a feature request?

➜ How do I request a new feature?

➜ What can I expect after submitting a feature request?

➜ How can I keep up with the status of a request that I've made?

What defines a feature request?

To avoid confusion, we thought it useful to clearly distinguish a feature request from a bug complaint. A bug is an unforeseen coding flaw that hampers the expected behaviour of an existing feature, causing the later to stop working or respond in a way other than the supposed; reporting a bug is essentially a bid to have the defected feature restored to its former state – no more, no less. 🐞 A feature request, though, involves innovation: it's the identification of a need for which no proper solution has ever been offered, calling for new development, which can be the enhancement of a current functionality to optimize and/or expand its capabilities or the creation of an entirely new tool. πŸ’‘

How do I request a new feature?

Spotted an opportunity for improvement? Then contact us through the Messenger app at the bottom right-hand corner of the portal or email us at support@fullfabric.com. Response times typically vary from a few minutes to a few hours, depending on the volume of incoming queries. πŸ™‚

When making your idea known, please include the following information:

  • A description of what are you looking to do that you apparently can't

  • Why is it necessary or why would it be beneficial

  • An estimate of how often would you need to perform said action

  • Examples of such a solution in other platforms that you'd like to reference (if applicable)

In short, we need to understand your core problem. Hence, instead of telling us, for instance: "I want the ability to embed YouTube videos on applications", please communicate the root cause: "I need a way for applicants to easily add video interviews to their applications". Based on that, we'll confirm whether we already have that functionality or even a crafty workaround without your knowledge; if not, assess

if your request aligns with FULL FABRIC's platform and roadmap; and, if the conclusion is in the affirmative, decide how to implement it to most people's advantage. That's not to say you cannot give specific suggestions for a possible solution as well, but since there are many ways to bake a cake, we reserve the right to devise the best recipe. πŸ°πŸ˜‰

In case there's an unavailable feature that we couldn't prioritise but that you hold in high regard nonetheless, a sprint proposal may be solicited. A sprint is a paid, time-boxed, fixed-scope project that's structured to deliver the capabilities that are most important to you in a predictable and cost-effective manner. Once you ask for a sprint, we'll draft a proposal with a suitable budget, timeframe and whatnot and present it to you with the aim of arriving at an agreement. 🀝 Sprints are always subject to consideration and approval by FULL FABRIC.

What can I expect after submitting a feature request?

If the feature already exists without you knowing or is not currently part of your subscription plan, we'll inform you and go from there. But if it's something we don't possess, we'll proceed to discuss it internally.

On a regular basis, our Client Success and Product Development teams convene to review the latest requests. Not all of them will come to fruition, and the ones that do may turn out different from what you'd imagined. As Henry Ford is famously (although perhaps apocryphally) quoted as saying, β€œIf I asked people what they wanted, they would have said a faster horse.” Consequently, we have to carefully analyse each and every request, evaluate it against our roadmap (as only so many things can fit in), prioritise work, plan it, and then think outside the box in a comprehensive manner to ensure that the execution is as efficacious and efficient as possible to as many as we can. Our roadmap is driven by a mix of industry insight and customer feedback, meaning that we generally have a vision of where we want to go and account for that, in conjunction with other criteria such as impact, reach, effort, complexity, time and so on.

If your request is green-lighted and written into our roadmap, we'll notify you, give you a rough deadline and stay in touch until delivery. Along the way, we may ask you to test one or more beta versions and provide us with your opinion of them. However, if your request is not viable, we'll also notify you and explain why. Most likely, it will still be added to our backlog. We periodically revisit past ideas to reassess if the circumstances have grown favourable in the meantime; if yes, we'll pick them up for development.

How can I keep up with the status of a request that I've made?

You're welcome to write to us anytime you're looking for news by the same means indicated above, but you can also stay up to date with our releases through our changelog, updated monthly. Still, it's our custom to write back to the original clients who requested a feature to inform them of its deploy. 😊


You have reached the end of this article. Thanks for reading! πŸ€“ If you have any questions or comments on the topic at hand, or if you enjoy reads like this and have article requests, feel free to start a chat or email us at support@fullfabric.com. Also, please leave a rating below. Your feedback is highly appreciated! πŸ’–

PUBLISHED: August 12, 2020
LAST UPDATED: August 13, 2020 at 11:05 a.m.

Did this answer your question?