I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system.
Uncategorized
10
Posts
10
Posters
23
Views
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc If I understand you correctly, you want something like https://www.znuny.org/de or https://requesttracker.com/ which are both FOSS and pretty good at handling tickets.
We are running znuny and before that OTRS for atleast 15 years in the company without any major issues.
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc I am using Zammad, which works well, but is a bit tricky to install. It's developed by a German company, it's open source.
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc I used Request Tracker (see @Kevin's comment) for the better part of 20 years. It can do all these things and does them very well. It is great to self host. However, it's not really "super simple" and has a list of CPAN modules longer than my "to do" list.
Still, great tool. -
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@ivory fyi: this renders without newlines / list markings in ivory compared to it on the mastodon instance.
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc we use https://freescout.net at work. Based on laravel. Should tick most of your boxes.
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc I have heard good things about https://zammad.org/ for this sort of setup
-
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc The demo application published with #rei3 may already meet your requirements. https://rei3.de/demo_en/
-
@jollyorc If I understand you correctly, you want something like https://www.znuny.org/de or https://requesttracker.com/ which are both FOSS and pretty good at handling tickets.
We are running znuny and before that OTRS for atleast 15 years in the company without any major issues.
@piratehonk @jollyorc alternative: www.zammad.org. Docker compose installation, but does include a KB.
You should keep up with updates. -
I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system. What it needs to be able to do is
- receive random emails at 1-n email addresses (think "info", "sales", "support", etc) from ideally separate POP/IMAP servers
- match those emails to the correct queue / team
- forward that email to the correct team
- team members can simply answer to that forwarded email to answer to the original sender
- the original sender can again answer and that gets routed accordingly
- the system keeps track of which incoming email got an answer etc.
- there's a simple web interface to monitor the queues and keep track of what is an open conversation, what is done, etc.
What is NOT needed and can safely be omitted and ideally also hidden from the interface of present are things like
- SLAs
- priorities
- knowledge base
- asset management
- and anything else corporate-y
Canned answers might be a boon, but not stricly needed.
Any suggestions? Bonus points if it runs on a LAMP stack, extra bonus if it is available in german language. #fedihelp
@jollyorc
Request tracker from best practicalEdit: It is a perl thing that runs in/around apache and has lots of options for routing/ fetching emails. It's likely packaged for your distro already
-
undefined oblomov@sociale.network shared this topic on
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@kuechenlatein @freuwesen hier das issue: https://github.com/Automattic/wordpress-activitypub/issues/2990
hier der fix: https://github.com/Automattic/wordpress-activitypub/pull/2991
-
I have a question about Python libraries and testing scope.
If I'm importing 'serial' in my library, and use it like the following to create a connection to a sensor:
--- start code ---
import serial
class Sensor:
def __init__(self, serial_device):self.__serial_device = serial_device
try:
self.__connection = serial.Serial(
port=serial_device,
baudrate=9600,
bytesize=serial.EIGHTBITS,
parity=serial.PARITY_NONE,
stopbits=serial.STOPBITS_ONE,
)except serial.SerialException:
print("Could not establish serial connection to sensor")--- end code ---
how much testing should I do around the serial connection? Just mock up a few buffers (byte streams), and see how my class handles unexpected input?
One the one hand, I want to make the library as solid as possible. On the other hand, I don't want to run tests on code I don't control (the library module). I know of the 'mock-serial' utility, but haven't used it.
The aim is to make a Python version of my Arduino library for the CozIR Ambient CO2 sensor:
-
@francommit ancora una cosa, se metto un apparecchio fisso sul tetto, esso farà solo da router/ripetitore in quanto il bluetooth del telefono non arriva fino lassù (nel mio caso tre piani) quindi i messaggi verranno hoppati al mio apparecchio "mobile".
Il nodo router/ripetitore avrà un suo identificativo e dovrò configurarlo prima di installarlo sul tetto.
Posso utilizzare la stessa app per configurare due apparecchi? (ricevere solo da uno, quello " mobile")? @snow @lgsp @andre123 @gecco
-
@snow @ilarioq @lgsp @andre123 @francommit ma mi era parso di capire che collegando il nodo a internet serve per coprire le zone che altrimenti non sarebbero coperte. Non ricordo esattamente dove l'avevo letto ma mi pare fosse così.
Dove ho intenzione di mettere il nodo (in cima all'edificio dove lavoro) non arriva nulla (tranne un nodo che è comparso ieri pomeriggio e poi è sparito) e se nel futuro compaiono altri nodi allora lo scollego da internet.
-
@maschinist Nice!
Falls du Lust hast, kannst du es auch sehr gerne als Snippet hinzufügen: https://github.com/Automattic/wordpress-activitypub/tree/trunk/snippets
-
Puoi farlo, sì.
Ma prima capiamo cosa succede davvero.Se nel punto dove hai messo il nodo non ricevi praticamente nulla via radio, metterlo come router non serve.
Un router mesh ripete solo quello che sente.
Se non sente nodi LoRa… non ha nulla da ripetere.Collegarlo al Wi-Fi con MQTT non lo trasforma in “ponte radio”.
Lo trasforma in un gateway Internet.Quindi:
* via radio → inoltra solo ciò che riceve via radio
* via MQTT → scambia traffico con altri nodi collegati a InternetHa senso farlo router con MQTT solo se:
* vuoi fare da ponte tra rete radio locale e rete Internet
* sei in una zona dove almeno qualche nodo radio arriva
* vuoi creare un punto di accesso stabile h24In breve:
Un router non crea copertura dal nulla.
Estende ciò che già riceve.La copertura si crea con posizione, antenna e altezza.
Non con una spunta nell’app 😉
-
@gecco Qui a Milano è un po' un casino, purtroppo.
-
@pfefferle Großartig, vielen Dank. @freuwesen
