Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

I'm looking for a super simple (ideally open source / self hosted) ticket/contact management system.

Uncategorized
10 10 0
  • 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.

  • 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.

    @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.

    @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.

    @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.

    @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.

    @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.

    @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.

    @jollyorc The demo application published with 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.

    @jollyorc
    Request tracker from best practical

    Edit: 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

  • oblomov@sociale.networkundefined oblomov@sociale.network shared this topic

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    0 Views
    How to transport #MIDI over #network the easy way? #fedihelp So, my client just called me, and it turns out… I need to have his MIDI signal from stage at my #FOH, which is around 40m of cable.I got a CAT cable running with TCP/IP infrastructure anyways.I know that #RTPMIDI exists, but I never have used it.So I need something that takes #USBMIDI and makes it available 40 meters somewhere else. Or I need to send USB over 40 meters, doesn't really matter.I think the endpoint for the MIDI transmission will be VCV Rack on Linux.Must happen the day after tomorrow, so buying something is not a solution.I have available: 1 Ubuntu Studio 24.4 laptop. 1 Windows 10 laptop. 1 MacBook Pro 2017. Several iPads, something Bluetooth-MIDI working with one of the iPads. I used to have #midimonster but it cannot be installed on Ubuntu any more due to dependency shit.EDIT: See my own answer in 🧵 for a solution.
  • 0 Votes
    6 Posts
    13 Views
    Yes. If no one on, say, mastodon.social is following you then none of your posts will show up in the global timeline there or in searches or in hashtags. Also if you have few followers your posts will receive few boosts so hardly anyone will follow you. So we end up with a handful of wildly popular accounts dominating the conversations which mostly happen on the big instances. Centralised power. Bad. The threadiverse solves this. People don't follow other people, they join communities and it's their membership that determines where the federation traffic goes. So nearly every instance has all the conversation and everyone is on an equal footing.
  • 0 Votes
    2 Posts
    21 Views
    @attksthdrknss substack is a Nazi bar already. I've heard good things about Ghost as an alternative. Latest version even supports integration with the Fediverse, apparently.
  • Hello FediVerse!

    Uncategorized fediart art artist fedihelp
    1
    1
    0 Votes
    1 Posts
    13 Views
    Hello FediVerse! We could use some help identifying the artist of my MIL’s favorite painting. Unfortunately we were unable to record any information before she passed. The appraiser drew a blank.What we know: purchased at an art dealer in Chicago or a suburb around 1965 for around $500. The back of the canvas states “Paris. Place de tertre 1958.” Not much, but it’s what we got.Appreciate any boosts for coverage, thank you so much!Edit sig added24”h X 36”w#FediArt #Art #Artist #FediHelp