fullhelp

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.

Comment · 7 years ago

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.

Comment · 7 years ago

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!

Comment · 7 years ago

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

Comment · 7 years ago

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.

Comment · 7 years ago

Hi!

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

Thanks!

Comment · 7 years ago

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!

Comment · 7 years ago

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.

Comment · 7 years ago

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.