Community Call – May 2026

What’s New with ImmyBot Community Calls

We’re fixing the community call invites. After this call:

• Existing invites will be canceled/removed
• You’ll get a clean shared calendar link for the rest of the year
• No more duplicates, ghost meetings, or general confusion

Support Snapshot (April)

A quick look behind the scenes:

• 431 closed / 448 tickets opened
• ~6 day SLA (consistent month over month)

Nothing big to report just steady, consistent support delivery across the board.

Product Updates to Watch

A few big things are either shipping or right around the corner:

Coming soon / in progress:

• Huntress Integration → expected end of Q2
• Halo Sync → nearing completion (to go out with v80)
• Onboard Detected Software → still in progress
• Getting Started Wizard
  • Phase 1 → beginner-friendly onboarding nearing completion (to go out with v80)
  • Phase 2 → deeper “ImmyBot 101” for advanced users
• New Billing Experience (coming in v80) This is a big quality-of-life upgrade for your finance teams:
  • Clear visibility into usage vs. spend
  • Direct invoice downloads inside the product

Where We’ll Be

We’ve got a busy few weeks ahead:

• May 11–14: MSP Show (London, UK)
• May 13: Huntress Roadshow (Detroit, MI)
• May 17–19: MSPGeekCon (Orlando, FL)
  • Join us Sunday for an AutoMAYtion Pre-Day (1–4 PM)
  • Build automations live with other partners
• May 26–28: RejectionCon (100% of registration goes to Rural Tech Fund ❤️)
• June 3: Next ImmyBot Community Call (lookout for new calendar invites)

If you’re attending any of these, come find us—we’d love to connect.

Featured Session: Incident Response Planning with Huntress

We were joined by Becky Teal from Huntress for a deep dive into incident response. Want the resources we worked through, view here!

The Big Takeaways:

The middle of a crisis is the worst time to figure out your plan.

Why This Matters (Especially for SMBs)

• 43% of cyber attacks target small businesses
• 60% of SMBs shut down within 6 months after an attack
• Many businesses still:
  • Don’t have a current incident response plan
  • Haven’t practiced it
  • Don’t align it with their insurance

Plan vs. Practice

Having a plan is step one—but it’s not enough.

What actually makes the difference:

• Running tabletop exercises
• Defining roles and responsibilities
• Practicing until responses become muscle memory

Practice → Confidence → Faster recovery

Practical Guidance for MSPs

A few strong recommendations from the discussion:

1. Run tabletop exercises at least annually

Even better if tied to:

• QBRs
• Contract renewals
• Security reviews

2. Make security part of your baseline (not optional)

We’re seeing a shift:

• MSPs increasingly require EDR/security tools
• Liability is too high to make this optional

3. Document EVERYTHING

Especially when clients opt out of security:

• Follow up conversations in writing
• Protect your business and set clear expectations

4. Educate clients on modern risks (AI, etc.)

Real example shared:

• Clients uploading sensitive data into public AI tools

Simple guidance that resonated:

“If you wouldn’t post it on Facebook, don’t put it in ChatGPT.”

Huntress Updates (Bonus Highlights)

• ITDR (Identity Threat Detection & Response) → moving to GA soon
• ISPM (Identity Security Posture Management) → available in beta
• ESPM (Endpoint Security Posture Management) → in development

Final Takeaways

Need Help?

• Partner Success (partnersuccess@immy.bot)→ for anything operational, onboarding, optimization
• Community (community@immy.bot)→ for event and collaboration
• Support (support@immy.bot)→ for technical issues and support

We’re here to help you succeed.