turnly VS laudspeaker

Have you tried using something designed for the job? Like this? https://github.com/turnly/turnly

👋 Hi, everyone, maintainer here. As we prepare for Turnly's initial release, I want to introduce some fantastic features that will bring us close to being a viable alternative to existing QMS. TLDR; → Turnly at GitHub Turn 0.3.6 comes with fantastic new APIs and other unique features! ☑️ Support for multiple locations (branches) ☑️ Web-based widgets for ticket-taking ☑️ Customizable branding ☑️ Custom Data Fields to gather initial information ☑️ Integration with Twilio for turn notification And more! We'd love you to try Turnly and share your valuable feedback, and together, we can make it better 🙏

https://news.ycombinator.com/item?id=39836316

Laudspeaker | Remote| Full Time | Senior Software Eng / Founding Eng

We posted on hacker news a few days ago - you can see the whole post here (https://news.ycombinator.com/item?id=39836316)

Summary below:

We are building a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker

We are a small team of 3, had a successful launch on HN a year ago, are backed by YC, and and are now starting to close large companies deploying our software to touch millions of users.

Who You Are:

Our mission is to build a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker and our site here: https://app.laudspeaker.com/login

We had a successful launch on HN a year ago, and have moved quickly since and are now starting to close large companies deploying our software to touch millions of users.

We continue to have an ambitious roadmap and are looking for a founding senior engineer to radically improve the product (take it from a 1->10, we have already built the 0->1) and help "level-up" the founders. We need our product to scale to tens of millions of messages sent an hour, handle millions of incoming api requests, add introduce engineering best practices, and tooling for our product to maintain SLAs

The right engineer will be excited to join a small team, excited to work on open source software, works well autonomously, can deal with ambiguity, and wants to work remotely (with minimum 4 hours of overlap sometime between 8am - 8pm pst)

Some more details:

- We work in Typescript with Nest.js for the backend and react for the frontend

laudspeaker: https://github.com/laudspeaker/laudspeaker

c) We can be self-hosted (A few users are self hosting today)

For others checking this out there are also older projects like Mautic [5]. And customer engagement is a large enough category that it includes projects like Chatwoot [6] that focuses more on customer support.

[1] https://github.com/laudspeaker/laudspeaker

Play around with our cloud option : https://laudspeaker.com/ / https://app.laudspeaker.com/

Check out our GitHub (Licensed MIT + Apache 2.0): https://github.com/laudspeaker/laudspeaker