Jelly Philosophy

A few things we believe. If you believe them too, Jelly is likely to be a great fit

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 number of seat-paying interchangable support agents.

That kind of factory-line support 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 isn't built to maximise support throughput. It's built to maximise the quality of the conversations your team has with the world.

Affordability is a feature

AKA "Everyone's Invited"

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 volunteer access to their email system. We want Jelly to be the obvious solution for teams like that.

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