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
-
@julian @silverpill @slyborg the changes I have marked for the next version are here.
https://github.com/w3c/activitypub/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Next%20version%22
I know there are some on there that Silverpill won't like, such as supporting IRIs for object IDs. I think it's worth having that conversation.
-
@julian @silverpill @slyborg most importantly: no protocol is mandatory. No protocol revision is mandatory. If the work the WG does isn't useful, nobody has to implement it.
-
@julian @silverpill @slyborg it's also worth noting that all discussions of the WG will be on a public mailing list. People can join the meetings, comment on drafts on GitHub. People interested in making more substantive contributions can become invited experts, even if they're not from a member organization.
-
@julian @silverpill @slyborg I will fight pretty hard against breaking changes in ActivityPub. We have an active network with tens of millions of people and tens of thousands of servers. It's too late for breaking changes and it has been for a really long time. Expect changes like: describing required properties of activities better. How `replies` (and maybe `context`) work. References to OAuth, Webfinger and HTTP Signature.
-
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/
-
Another object study from an anime series: Izzy's laptop, Digimon.
-
@julian IMO there's no reason why a web browser should understand where to open fedi links, without having any other type of app properly address those links as well.
What if someone in an instant messenger or email app sends you a link to fedi content?
Defining it at the system level (again, as is done with email) removes critical uncertainties.
Fedi has other big UX issues as well. Celebrities don't like it here because the TL mechanics make them unintentionally annoying... users follow then later mute them because their posts are popular for a while and we have to see them each and every time they're boosted (or manually silence those posts). Allowing the selection of some transparent algorithms could fix this.
-
Ha finito di vedere Un film Minecraft
