@evdass We’ve already implemented it and it is published online, available for anyone to integrate into their Zammad. It uses a bridge service we created called Sigarillo, which bridges Zammad and Signal.
However it required changing the Zammad code base. We have a Pull Request open to merge the changes into Zammad, but it hasn’t been reviewed by the core dev team yet.
We’ve released both our Signal and WhatsApp channel code for Zammad. As abel mentioned, there is a patch required for the integration with Zammad, which you can find above.
QuePasa is built on the same approach as we used with Signal, but for WhatsApp. While we have it working in production, it does take a little bit of finesse to get it setup. It is also very much 1.0, and we are looking for help debugging and improving it.
If anyone is interested, please contact me here, or you can find me directly as email@example.com or @n8fr8 in various places (twitter, keybase).
We are also looking to hire another developer to help us with our efforts building on Zammad, including the kind of channel integration efforts we have been posting about here. If you are interested or know someone who might have some spare cycles, please let me know.
first of all thanks for publishing such a useful piece of software. As a long-term admin of our intern OTRS-instance and experienced Python/TypeScript developer I took a first look under the hood of Zammad and it`s really well structured. Great job!
We plan to migrate our intern OTRS-instance and implement a WhatsApp integration.
Is there something new on this topic?
Do you plan it as a core-feature like the Telegram-channel or an add-on?
Is there someone who is willing to share his current achievements?
We are willing to spend some resources on this topic in 2022. But there are some more questions before to start. So if you are working on WhatsApp integration already or plan to do it in near future please reply.
We did communicate about whatsapp, even in this thread we did provide point of views.
What you may not understand (but have to) is that only because you open up a feature request, it doesn’t mean it’s a guaranteed coming feature.
Feature development costs a lot of time, not just for writing the code but also for specifications, verifications and such stuff. (time costs money).
We’re a fairly small team. You had and have always the option to speed up developments by inserting coins. If that’s a thing for you, contact our sales team. We in general do not provide any ETAs.
Sorry if that’s frustrating.
That’s the last time I’m gonna reply on whatsapp related threads - it’s just not bringing anybody forward.
Oh and smile, thanks for keeping us busy on several channels.
If you have whatsapp you are king I have my own open source platform I am running and I definitely know the issue with money and demand. Lots of requests but tipping in seems to be difficult. What kind of money are we talking about if I would like to get it developed?
Just a thought, how about some kind of zammad community crowd funding scheme for projects like whatapp, that way everybody who is interested can donate to the developers on a certain topic to reach a target quicker.