This looks interesting (as does linear, which many have brought up).
For kitemaker - you probably want a "pricing" on your menu - on mobile it wasn't obvious there was any pricing available (and we'll not be using a gratis service for something as essential as this).
Is kitemaker (or linear) intended to also be customer facing? We'd love to switch out zendesk for bugtracking/support tickets, and improve our process vis-à-vis github/gitlab issues in one fell swoop... Is that part of the plan, or is it more of an internal process tool?
Thanks for the tip on the pricing! We'll add it to our menu.
At the moment we're quite focused on teams' internal development process and we're a very small team (though we'll be growing a bit soon). That being said, we're having a lot of discussions with teams on how we can make it even more useful. One area that comes up a lot is capturing user feedback/feature requests/etc. Another is support tickets. Let's see what comes next!
May I ask why you want to switch out of zendesk ? I'm reluctant to use it where I am (we have so many badly integrated third party software already...) but some people are pushing a lot for it.
We have modest needs from a ticketing system, no desire for customer chat - just email to ticket workflow. Zendesk works, but is a bit oversized for our ticketing needs (and slightly overpriced, perhaps - but not by an order of magnitude, so to speak).
We have a lot of history in our zendesk - and some of our customers are acquainted with the workflow.
I would probably not introduce zendesk as a new tool, but I do not have a clear recommendation on what should replace it.
At a previous work place we were quite happy with Trac - and I was a bit disappointed ttha Apache Bloodhound seemingly died off (it was in many ways an opinionated Trac setup/distribution).
On the other hand, if the other choice was a monstrosity like jira, I'd probably prefer zendesk.
I do think it's important to realise that support ticket (sub)systems are not issue trackers/scrum tooling - and vice-versa. Not all tickets are issues, and many issues are not tickets.
But if the two sub systems have some easy integration, that can still be beneficial. Just don't fool yourself into thinking that it can (should!) all be automated. Good support ticket handling provides real value both for customers and the development team.
For kitemaker - you probably want a "pricing" on your menu - on mobile it wasn't obvious there was any pricing available (and we'll not be using a gratis service for something as essential as this).
Is kitemaker (or linear) intended to also be customer facing? We'd love to switch out zendesk for bugtracking/support tickets, and improve our process vis-à-vis github/gitlab issues in one fell swoop... Is that part of the plan, or is it more of an internal process tool?