Same licence, more capability. Here’s what’s sitting untapped in your Service Collection.

If you’re running Jira Service Management, chances are you’re paying for more than you’re using. Between February and June, Atlassian rolled Customer Service Management, Assets and Rovo into Service Collection at no extra cost for existing JSM customers.

That’s not just a few extra add-ons, either. Customer Service Management is Atlassian’s first real move into external customer support. For anyone currently paying for a separate support platform, that’s a shot at retiring the whole thing.

We’ve seen the savings add up before. Harrison AI consolidated onto Atlassian’s Teamwork Collection and avoided AUD 229k in costs over 24 months, a 4.4x return with breakeven in six months. Service Collection runs on the same logic, more of what you need, bundled into the subscription you’ve already got.

What We’ll Cover

• Live build: watch Vincent Wong build a Customer Service Management AI agent from a blank canvas, so you can see what’s actually possible rather than just hear about it
• Assets deep dive: Mark Edwards walks through the standard plan expansion, attribute configuration and CMDB requirements, the practical detail that usually gets skipped
• Data protection, compared: where Atlassian’s native capability stops and where Keepit’s backup solution for JSM picks up
• Practitioner Q&A: a direct conversation with the people who build this stuff, not a vendor pitch

Come ready to ask questions. Leave with something useful.

This session is for ITSM leads, JSM administrators, and anyone deciding what Atlassian tooling looks like at your organisation next year.

No slides for the sake of slides. A live build, a real Assets deep dive, and breakfast.