The Jelly philosophy

Here are a few things we believe. If you believe them too, Jelly is likely to suit you well.

Conversations, not tickets

Most customer support tools turn every email into a "ticket". Each ticket joins a queue, and a team of support agents works through the queue as fast as it can.

That kind of production line makes sense for a large company with a whole support department. It doesn't suit a small team that wants to have real conversations with the people who use its work.

Jelly isn't built to push tickets through as fast as possible. It's built to help your team have good conversations with the people who write to you, and to let your whole team see and join those conversations.

Affordability is a feature

Jelly works well for companies, and we want it to work just as well for other kinds of team:

• volunteer-led organisations
• conference organisers
• charities
• community groups

These groups rarely have much money, and the number of people who help out has little to do with the size of their budget.

Tools that charge per person, or "per seat", make these teams ask whether they can afford to give each new helper access to their email. We don't charge per person, because we want Jelly to be the obvious choice for teams like these.

We keep the price low by keeping Jelly focused on what small teams need to work on email together. We're not trying to win by having the longest feature list.

Trust your team

Jelly shows your team who's got what, so nobody needs to hand out work or check up on anyone. Everyone can see what needs doing, and together make sure nothing slips through the cracks.

By default, everyone on the team can see every conversation and add notes to it. With a few exceptions, we think the whole team benefits from that openness.