Feature Suggestions and Improvement Feedback for voce.chat (Docker Installation)

[Gaetner84]

Dear voce.chat Team,

I am currently using your system via the Docker installation, which is working quite well in general. However, I've noticed a few areas with potential for improvement. I am providing this as constructive feedback because I find your project very exciting, but I'm currently not fully satisfied with the compromises required for the chat widget's integration.

Here are my suggestions for improvements:

Chat Button Design and Integration:
The floating, ever-present chat icon on the website is poorly implemented and, in my opinion, outdated. I use it because it seems you don't offer an easy way to use a custom, existing button instead.

Request:
Please add a feature to open the chat window when a user clicks on a self-created button (e.g., via a simple code snippet or function call). This would greatly simplify the integration.

The permanent floating icon feels "old school." Modern web design suggests a button that, when clicked, opens the chat popup, rather than a symbol that constantly occupies screen space.

Incomplete Color Customization:
The available options for color customization are incomplete. Only a part of the widget can be styled, making it difficult to fully align it with a company's corporate design. This is not optimally solved.

Separation of Chat Icon and Company Logo:
While a logo can be used, why is it not possible to define a separate logo exclusively for the chat dialog? I want my company logo to be visible inside the chat to ensure brand identity (so users know they are talking to the website operator).

The Problem: Currently, I must decide whether the company logo is used as the chat icon on the website AND inside the chat dialog. A company logo used as the initial chat symbol on the page can be confusing; users might not recognize it as a clickable button to start a conversation.

Request: These graphics need to be separated. I want my company logo in the chat and a suitable, color-customized chat symbol on the website. These forced compromises make implementation unnecessarily complicated.

Simple LLM Integration (Google Gemini / Ollama):
The integration of LLMs (Large Language Models) like Google Gemini should be easy to implement. I already use it in my own chat solutions, where I can create fictional characters with specific attributes by passing the LLM a Markdown file with the necessary information.

Suggestion: Please offer a straightforward option in the settings to integrate Google Gemini. This is a good choice as it is generally simple and often cost-effective. By using a Markdown file, the LLM could also be provided with company information and behave like a virtual employee. This should be a standard feature today.

Alternatively, simple integration via an Ollama server would also be highly desirable.

I hope you view these points as positive and urgent criticism. I believe these changes should not be difficult to implement and would greatly improve the product.

Best regards from Germany.

[haorwen]

You can break down the requirements and publish them on the issue