fullhelp

That's a great idea! Thanks for sharing!

The app looks good! I didn't liked the fact that I have to create an account to use the app on my device. Are you planning on adding a web version or something to support multiple devices? That's the only reason/benefit I can think of for the account registration.

Reading the article and the comments here makes me consider raising the price of a self-hosted help desk software I recently released. Or at least, adding a new premium price package.

The site looks good and the idea is great!

Hey! You are right, I'll be adding that. Thanks!

Hey! That's something really practical, something that I would use myself in many cases. I took note, thanks!

Thanks! :-)

1. The purple circle has two question marks (the left one is used in Spanish). Customer support is about answering lots of questions, so this is one of the reasons I used those symbols. For the name itself, I made a list of possible candidates, and really liked the simplicity of "Full Help". Also, it's close to some popular apps like Full Story and Full Contact.

2. For the web sockets, I was initially using Laravel Echo Server (https://github.com/tlaverdure/laravel-echo-server) (powered by Socket.io) and then switched to Laravel Websockets package (https://github.com/beyondcode/laravel-websockets) which is an implementation using PHP itself, making the requirements and installation even easier.

Thank you!

Yes, Docker Image will be something I will be working on. Anything that makes it easy for people to install the software is always welcome. I'm also looking to add a DigitalOcean 1-Click install option.

Hi! Thank you! :-D

The license is based on DuetApp's (https://duetapp.com/) version. I liked its simplicity and asked the creator if it would be OK with him to use his license as a starting point.

Shared drafts sound like an interesting feature and one that seems easy to implement on Full Help. I've added it to my Trello board. Thanks!

Hey! Thanks for your suggestions! I will definitively keep that in mind.

Hey! Thanks for checking it out and the feedback! I will make sure that future versions have the autosuggestion behavior on search fields and any input field on the admin side that requires it.

Hi!

Not at the moment but both are planned. Webhooks will come first as this facilitates, even more, the integration between other systems.

Thanks!

Thank you!

Those are all great suggestions! Some of them are already present, like the live chat, leave a message (the same as live chat which fallbacks to email if the user gets disconnected) and article suggestions from a knowledge base (manually configured with JavaScript).

All the other suggestions are great and will definitively consider them.

Edit: I suggest to sign up to the newsletter at fullhelp.com to keep up to date on releases. :-D

Thanks!

Hey!

It's always a concern for me. I'm looking for ways to detect such cases and that way terminate the licenses, which will prevent the user from downloading any release. Another approach that may work (just an idea), is to secure the documentation and allow access to it to logged in users with one valid license at least, but this has some disadvantages like the affected user experience.

A legal notice is always an option.

Thank you!

The software is focused on web-based businesses at the moment, mainly because it makes it simpler. However, I'm always open to suggestions. I'm not familiar with the asset management part, but I will definitively check it out and see if this is something that can be added, either built-in or as separate add-on or application. Just like you, there are other people that may benefit from it, especially when you say there aren't many options with a good integration.

Thank you! Feel free to reach out to gerardo[at]fullhelp or support[at]fullhelp.com anytime you want.

Hi!

Thanks for checking it out. The demo domain is missing a SSL certificate for the knowledge base sites. That's something that needs to be fixed.

Hey!

I will be considering it, you are right. Some people just don't want to bother with the technical stuff that comes with managing servers and/or installing the software. I'll definitively consider a SaaS version.

Thanks!

Thank you! :-D

In that case, the knowledge base dashboard has several statistics (https://imgur.com/5Z60SWl). Help desk reports are not present at the moment but is something that will be added definitively.

Thank you! :-D

Hi!

Thanks for taking the time to check it out and the feedback!

For the theming feature, I was thinking of adding a way to export the installed themes, that way the user can download the theme being used and apply any customization and re-upload as a new custom theme.

A blank template for new designs is an excellent idea.

I've also created a small node based command-line program that syncs local development changes to the live knowledge base portals. This helps a lot with testing and previewing the themes. I've not released it just yet, I plan to do so with an MIT license on GitHub. It is similar to Shopify's Themekit (https://shopify.github.io/themekit). This is what I use to work on theme designs.

For knowledgebase language strings, you are right, that's possible at the moment through the theme locale files.

Thank you!! :-D

Hey!

I don't think that word is present on the few docs created. Try "requirements" which should show two results: https://docs.fullhelp.com/en/search?query=requirements

Sure! Use "hackernews" for a 23% off :-D

Thank you!

There are role-based permissions implemented, but they are only for team members on the help desk.

ACL/permission for knowledge base sites is not present at the moment but may be a good addition for a future release. I have added it to the Trello board.

Thank you! The help widget isn't working that great on small viewports, you are right. On iOS, there's also the issue of autozoom when text fields are focused. This is something that will be addressed for the next release which is planned for this week.

Thank you! That's one of the goals and I'm glad that I've done it right! :-D

Feel free to get in touch anytime you need something or have a question about the system or anything else. Always happy to help!

I will take your suggestion into consideration when working on the landing page and the documentation. Right now, the user gets access to the full app source code and the instruction currently available at docs.fullhelp.com (docs are not included in the download files). Documentation is still a work in progress, and because if this, I'll be installing the software myself when possible. If not, I'll be happy to guide and help in the process of installation through live chat or email.

Thanks again for checking it out, sharing it with your boss and the feedback!

Hey!

Price was a bit of a struggle. Initially, my plan was to sell it for $249 (or around that range), but since this software is also for freelancers and small businesses, some of them don't have that kind of budget and stick with $129 which is good.

The software was released recently (a week ago more or less), so no customers have purchased just yet. However, I've already presented it to several customers (freelancing business) and are considering grabbing a copy.

No, the software hasn't been released to the public up until recently. :-D

No marketing/advertising has been done yet. HN is the first public post made!

Yes, it is my full-time job at the moment. I have an old freelance project that I'm working on, but besides that, Full Help is my new full-time project and hope it stays that way for a long time. This is also one of the reasons for the pricing model (optional license renewals). I want it to be viable in the long term for me and the customers using it.

That's a good idea! Will be working on a blog post explaining the backstory and several things that people have asked here. :-)

Thanks!

Thanks! :-D

I think it will work on any team size, not 100% sure as it hasn't been tested in this context. I'm always open for suggestions, and will be happy to apply the necessary fixes and enhancements if something isn't working as expected in cases like this.

I'm confident that it will serve well on teams of any size.