I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system.
Uncategorized
10
Posts
10
Posters
0
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
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Oltre le macerie
@anarchia
Eccoci di nuovo qui. Riprendiamo le pubblicazioni dopo le consuete settimane di pausa, ma per le lotte non c’è stata sosta nella crescente stretta autoritaria e militarista. Multe, denunce, sgomberi. Questi sono i regali che si sono scambiati governo e...Vedi l'articolo
https://www.rivoluzioneanarchica.it/oltre-le-macerie/
-
Ha finito di vedere Un film Minecraft
-
@tasket@infosec.exchange an official protocol handler would help a lot. Today there is the option of introducing a web protocol handler but the UX for it is pretty dogshit (Piefed recently implemented it, and the number of dialogues was too damn high!)
That said I don't know if PWAs can register against non-web protocol handlers. That would be useful for sites like NodeBB.
-
@wgwz @IceClimate comes to mind.
-
Testing a Continuous Printing Mod for the Bambu Lab A1 Mini
There are a few types of continuous 3D printing with FDM printers, with a conveyer belt and automatic build plate swapping the most common types. The advantage of build plate swapping is that it automates the bit where normally a human would have to come in to remove finished parts from the build plate. A recent entry here is the Chitu PlateCycler C1M which the [Aurora Tech] YouTube channel had over for a review. This kit bolts onto the Bambu Lab A1 Mini FDM printer and comes with four extra PEI build plates for a not unreasonable $79 (€69).
As also noted in the review video, this is effectively a clone of the original swapmod A1m kit, but a big difference is that the Chitu kit comes with all of the parts and doesn’t require you to print anything yourself.
The different plates are prepared using a special tool that inserts G-code between the plate changes. Moving the bed in a specific way triggers the switch that lifts the finished plate off the magnetic bed by the plastic grip on the plate and loads a fresh plate from the stack. Here it was found that a small tolerance issue prevented the last plate from being used, but some sandpaper fixed this. Other than that it was a fairly painless experience, and for e.g. multi-color prints with separated colors – as demonstrated – it would seem to be a great way to churn out the entire model without manual intervention or a lot of wasted filament.
Perhaps the main issue that is central to all of these build plate swap mods is where the plates go after they’re pulled off the magnetic bed: the padded box is a great idea for the first one or two plates, but after that you get your PEI build plates with parts on them crashing on top of each other.
This is where perhaps something like a passive roller conveyer system could provide a nice gentle off-ramp, though this too would increase the footprint of the system. Regardless, the overall system seems to work well enough, allowing one to stack fresh plates in the chute and if you turn on build plate detection in the A1 you can even prevent the printer from trying to print on the magnetic bed.
-
> 'Veterans GO BALLISTIC on ICE: “Fight These Motherf*ckers!”'
#Trump #ice #minnesota #EU #SecondAmendment #antifa #DeathToAmerica #uspol
-
@fediversereport If they are smart they will fix a raft of fundamental UX pitfalls in current ActivityPub by defining a protocol handler for it.
Email needed its protocol handler spec while it was getting established – and arguably still does – and I do think this is one of the ways in which ActivityPub is "like email".
-
C’era una volta Repubblica – Intervista con Franco Recanatesi
@giornalismo
articolo21.org/2026/01/cera-un…
Cinquant’anni di Repubblica, con tanta nostalgia e un certo dolore. Nostalgia per lo straordinario quotidiano che fu, fondato e diretto da Eugenio Scalfari; dolore per ciò che ha smesso da tempo
