Conversations, not tickets
Most customer support tools turn everything into a “ticket”, and each of these “tickets” is pushed onto a queue, to be picked up and processed as quickly as possible by a (potentially large) number of seat-paying interchangable support agents.
That kind of factory line support process makes a lot of sense if you’re a multi-million-making company with a whole support department.
But we’re not that. We’re a small team who values having actual conversations with the people who use our software.
Jelly is not built to maximise support throughput. It’s built to maximise the quality of the conversations your team has with the world, and to enable your whole team to access and contribute to those conversations.
Affordability is a feature
Jelly works well for companies, but we also want it to work for other types of team:
- Volunteer-led organisations
- Conference organisers
- Charities
- Community groups
- … and so on.
What do all these groups have in common? They aren’t swimming in cash, and the size of their team is not correlated with the amount of money they have either.
Tools which charge “per-seat” also inadvertently penalise these kinds of groups, forcing them to decide if they can really afford to give that new member access to their email system. We want Jelly to be the obvious solution for teams like that.
Affordability is one of the most important features of Jelly. We are not trying to hoover up every dollar on the table. We don’t make you pay for every new person who joins your team. The Big Players can have that. Instead, we’re quietly focussed on building a great, simple tool for you and your team to work together on email more effectively and efficiently.
We keep our price low by keeping Jelly focussed on what we believe most small teams need to collaborate on email. We don’t try to compete with other tools via our feature list.
Trust your team
Jelly helps your team see who’s got what without the need for top-down assignments or micromanaging. Jelly helps your team to help itself to make sure that no conversations slip through the cracks.
Our default mode is that everyone can see and comment on every bit of communication in the inbox. With some limited exceptions, we think the whole team benefits from this kind of transparency.