Doodles or Data: A Conference Note Survival Guide

By  
El Copeland
March 2, 2025
20 min read
Share this post

Before you get started

This article is a companion to my article on how to get the most out of Conference and Industry events. While most of the concepts here will not require external explanation, some things will be linked to subsections in my article, “Ripe for the Picking: Maximize your Conference ROI” and you may benefit from skimming that piece for context or discussion.  

This article is about the importance of good notetaking including a demonstration of one of the methods I personally use. I have a lightweight template in OneNote that I’ve scrubbed for your use and you can download that here. We will also use a fair amount of genAI through ChatGPT.  

As with most things from Rising Tide, this document is not dictatorial. We feel everything evolves and the goal for this was to be an easy tool that can be implemented with little effort. If you have feedback or questions or just want to argue, feel free to find me on LinkedIn or the MSPGeek Discord community (@cinakur) and I’ll be glad to chat!

Why take notes? This isn’t school.  

I was a poor student in school, ironically driven but unmotivated. I knew I wanted to make a difference in the world, and that was it. I didn’t even plan on getting an Engineering degree. My family was lower-middle class in a rural town in the southeast United States that sprung up around an Air Force Base 80 years ago. I was the first on both sides of the family to go straight from high school to college, so I had no context or support about what it would take to be a Doctor, Lawyer, or even Engineer. I thought maybe I’d just get some vague Liberal Arts degree and become a teacher or get married and be a mom. Nothing bad about being a teacher or a mother, I still could see myself being both one day: it’s just that I had no dreams of my own, no direction or understanding. I thank all that is good in this world that college counselor looked at my SAT scores and was surprised I wasn't already pursuing something explicitly science and math focused!

proof I graduated, or stole some other sucker's stole.

While I say I was a poor student, I did receive good grades in basic classes and hands-on labs as I am a generally curious person, so talking about theory, tangible experience, and writing about it carried me a long way. However, as classes advanced from practical to theoretical, I rarely operated well under pressure and had poor time management so I would often fail homework and mid-term exams. When my Master’s Thesis was due, an advisor of mine chided me, noting I should be much further along in my research and analysis and questioning if I’d even make the deadline to defend it that year. (His talking-to was the motivation I needed to complete, even if I was doing it out of spite.)

School was miserable, sitting at a desk for hours a day was miserable: there were a million other things I could be doing and were already thinking about as I am half listening to a tenured professor drone on about whatever heady topic the syllabus offered.

Did my notes in those classes carry me through? I think back to them and I can clearly see in my mind’s eye: a doodle I made of my water chemistry professor as a lobster from 17 years ago. So, I guess you can say, yes, they carried me, but probably not for the right reason.

So why am I, an admittedly poor student, writing a blog post about note-taking? How did I even get out of college with two degrees? And why a lobster!?

I went through notes I've saved from school. I couldn't find the lobster, but I found this. How we didn't know I was ADHD sooner is beyond me.

Well, here’s the thing: with each exam I took, and with each hands-on lab, I finally understood the concept. Something about the adrenaline and skills that I needed to perform helped the concepts solidify in my mind, and eventually I even had enough confidence to tutor others in those courses!  

The key was, and is, action.

It’s easy to freeze after a conference. You’ve taken in so much information: new names, new faces, new products, new settings, new experiences. Hopefully, most are good, but maybe some are bad. How do you KNOW what action to take, how do you even remember?

In this article, we’re going to talk about one way to create meaningful plans of action through note-taking at conferences, using the template that I created as a guide. We’ll look at our notes according to the lifecycle of your conference attendance: choosing the event, attending, and after. For this article, I’m going to use the two examples, one of planning to attend CodeMash, Home - CodeMash., following their 2025 event, and the other with my actual notes from Right of Boom 2025.

Let’s start at the beginning.  

El’s Template Overview: A Walkthrough

Before getting into how I use the template, let’s go over what is in it and my thought process behind it.  

Did you download it yet? You can get that OneNote file here: Conference Note Template. (Contact me if you want a different type of export!)

The key thing about building with action in mind is that I bookend my trip with intentional processing and preparation so I can enjoy the event with confidence, knowing I am being responsible with my time, skill, and relationships. There are three main parts to the thought process that governed my template: 

  1. Know Your Why. Expending mental energy at the beginning reduces the number of decisions and subsequent decision fatigue you'll experience on-site. Set the vision upfront and it will go a long way.
  2. Keep it Simple. You want something you can return to throughout the conference, without "debt" or guilt. Giving yourself something easy to come back to as a touch point and "source of truth" will make this more attainable.
  3. Be Accountable and Finish Strong. Have a dedicated time to synthesize and analyze what you've learned and what your next steps are!

I personally do this by bookending my trip with 1-hour on each side: the hour before I plan my goals, and the hour after I summarize and make an action plan. Considering a conference with travel is easily a 40-60 hour week (and longer for vendors!), 2-hours is a small investment on the success of my conference attendance from a content perspective.  

If we’re looking for direction on action at the end of this, we need to know where to find certain things we talked about, and that is all this OneNote template is. So, let's take a look! If you'd like to follow along, I have screenshots that follow as well as a video I recorded, available here: A Conference Note Survival Guide.

When you open up the OneNote Template, you should see some version of this.  

I like to have a Conferences Notebook shared between the team, and for each conference I add a Section Group, with the given year as a Section. So I copy parts of my template to the given location as needed.  

A preview of what my Conferences Notebook looks like with the hierarchy beneath it.

Within the template, you will find four main sections:  

  • Conference Overview
  • Session Notes
  • Networking
  • Vendors

Let’s talk about each section and how they’re used.  

Conference Overview  

Template view of the Conference Overview

The point of this page is to visualize what success looks like for this conference, personally and as a team. You’ll find there are a lot of questions on this first page. You don’t have to answer all of them, but asking them ahead of time will give you some clarity on the type of questions you could be asking to get the most out of this event.

Session Notes  

Session Notes are broken up into two parts: Agenda and Session Notes.  

Agenda

Make an Agenda page for each team member attending so you can compare sessions, notes, and ask questions!

Template View of the Agenda Page

Session Notes

Session Notes are for the actual Session Notes. Even if you don't take notes or even attend the session, you can fill in things you hear other people mention about it down the road!

Yes, more questions for you to ask.  These are helpful when you do some AI analysis at the end.

Template for Session Notes.  

Networking  

Networking should be lightweight! You're going to meet a ton of people, quickly. Keep it at a high level as much as possible.

Template for Networking.

Vendors

Vendors should generally be separate from your Networking so can have a place for notes about their product that aren't related to them personally.

Template for Vendors.

Before you go: Know your Why.

Now that we have the lay of the land for the template, let's set up our example of attending Codemash 2025 (CodeMash).

We create the new Section for this event and copy in the template pages.

Taa-dah, we're done now! Right? Right?!

Now, the work starts. For me, I like to give myself one-hour to work this through. It’s enough time to do research and not too much time that I feel like I’m getting in the weeds.  

Set the Course: What's your Why? 

If you read the article this is a companion to, you know I think setting your intentions for a conference is the foremost important thing to accomplish once you decide you’re going.  

So, tell me, why do you want to attend CodeMash?

  • My friends are all going and I’d like to see them.  
  • There is a certain topic on the schedule I want to learn about.  
  • [Semi-famous Person] will be speaking.
  • Networking with new people or people in a specific industry.  
  • Some other secret reason.  

Do you have clear reasons you want to attend? Take a look at the Agenda from a high level or ask around. Maybe it’s worth asking a generative AI to help frame this. Perhaps ask, “Why should I, as an MSP (or individual, or business, depending on the data you’ve fed your AI!), want to attend Codemash?”

It’ll likely give you a bunch of reason, and while these are all probably valid to some degree, limit it to 1-2 main reasons and let the rest be a bonus. Review the website for vendors and key speakers that are meaningful to you. Fill out this section on the Conference Overview page.  

Ok, but now I'm honestly wishing I had attended CodeMash this year.

Fully Review the Agenda.

Now, it's time to review the conference agenda a little more thoroughly. Which sessions do you want to attend? Here is their 2025 Agenda for context: 2025 CodeMash Conference

This session looks interesting. As does breakfast.  

Ok. First two important things. Breakfast and second breakf--er, a workshop.

Fill those in on the Agenda page. Each team-member attending can have their own Agenda page so you can see what courses everyone else is taking and divide and conquer the session topics, or take joint notes on the same document and fill in each others’ blanks.  

And add the Description and key notes to a new page in that section. Read the questions in the Session Notes section and write out your OWN questions of what you'd like to learn in this session based on your understanding of the Summary.

I literally just copypasta'd all this from the website and fixed a little formatting.

Rinse and Repeat until you have a full schedule. Be sure to put breaks in there occasionally for client calls or for serendipitous hallway meetings!

Now I'm SERIOUSLY regretting not going. Guess this gives me time to plan for 2026!

Some of these sessions, I won’t be taking active notes in (like the soldering course) but may want to have somewhere to dump resources or other notes afterwards! There may be a few different days that I jump into lightning talks, so I group them all together, they don’t need separate pages!  

Got it? 

The main things to remember here echo the blog post on conferences.  

  • Determine your why by seriously evaluating the agenda, determining your goals, and talking with your team about their own.  
  • Pre-prep what you can so you don’t have to make too many live decisions.  
  • Don’t overcrowd it. Make sure you’re not overcommitting!  

One more thing I pre-prep to help keep my focus: I travel with my work laptop but I do not take it to the sessions. Instead, I take a lightweight tablet. This allows me to focus on what I’m here for: networking and learning and not answering emails or surreptitiously working on projects.  

Boots on the ground: Capture Insights, be Present.

Time to actually take notes. At this point, we'll transition from planning the CodeMash trip to looking at my actual experience at Right of Boom this past year. Depending on your situation, you may or may not have the time or space to take “good” notes. I generally find myself in one of two situations:  

  • Session Notes: Sitting in a session with a tablet in front of me, able to take thoughtful notes
  • Conversation Notes: Standing in a hallway, at a meal, or in other fast-paced Conversations, where I’m unable to take good notes, if any. Sometimes I have half notes on a Notes app or something because I don’t want to forget.  
I went through the notes app on my phone to find some examples of half notes and found this glorious one. Others are better, but like...what the heck was I talking about on February 16, 2024?

In general, focus on the main things and let noise drift to the side. Here is some advice I have for handling each of these situations, and examples of how I handled them while at Right of Boom this past February.  

Session Notes

In general, any live note-taking completed by you should be about action, not mindless transcription. There are AI transcribers like Otter.ai or Plaud.ai for that. Your goal should be three-fold: 

  1. gathering the big points and the nuance of the conversation
  2. collecting data points and future research opportunities and
  3. identifying how those fit in with your goals or understanding.

Keep your notes high-level; focus on engaging in the sessions and ask questions. Write just enough to help jog your memory or find the source information later. If you wrote out your own questions in the planning phase, those can help guide your notes as well, or give you questions to ask when they open up the mic.

Here is a snippet from my notes I took in Brent Adamson’s session on the Framemaking Sale.  

As you see in my notes here, yes, take photos, but where do those go when you’re done? Do you review them? Really?  

Put that information somewhere useful, friend. Here are few things you can do to help shape your notes:  

  • Use OCR. The notes under Dimensions of Customer Decision Confidence, I did not type. I took a photo and then grabbed the text from that image. Your device may have OCR built into the camera app.  
  • Use Reverse Image Search. Find Images online that speakers referenced, through reverse image search. They will be better quality AND will often bring you to the source material the speaker used.  
  • Capture concepts that will be hard to track down later. Did they mention a data point or statistic? What was the source for that? What was the exact number? 
  • What do you thinkWhat concepts do you agree with? What do you disagree with? What makes you feel uncomfortable? What do you want to learn more about? 
  • Review before you leave your seat. Before getting up from a session, take 5 minutes and catch up on your notes. Don’t make a big deal of it, it doesn’t have to be perfect, just scrub through them to make sure they’ll make sense for “future you” when it’s time to review them.

Conversation Notes

Taking notes on conversations is a lot harder. Who did you talk to and what did you talk about? Where were you? What actionable things can you remember, jokes, or meaningful things about that situation?  

The Networking and Vendor sections are a lot lighter because they should be. Hopefully, you are living in the moment and connecting with these thoughts and ideas you discussed over a meal and worrying less about getting notes from these experiences. The point of these notes are to remind yourself of the important stories or experiences you had with someone, to build camaraderie and sometimes wise insight that these strangers-turned-friends-and-colleagues shared with you.  

For conversation notes, I would encourage you to take notes you can, by texting or sending yourself a brief message through Teams/Slack, or recording a voice memo. Sometimes, I also just message my business partner if it’s a particularly lovely exchange.  

Also, make sure you connect with that person, by social media, email, or business card. As with the Session Notes, triage throughout the day, or at the very least at the end of the day/beginning of the next to make sure all of your notes end up in one place.  

These are my notes from a recent conference, with enough redacted so you can see what I do, but enough showing so you can see I am not perfect or 100%. I didn't fill in some of the blanks as I've mentioned in later segments, I’m not building dossiers, I’m only writing out just enough information to jog my memory. Some of the experiences were highly memorable, so the names were enough.

In the end, the most important thing for your notes is that they are here for you to return to at any time during the conference. If you’ve done the pre-work of laying it out, you don’t have to expend energy to get back on track. You just find the next session or meal and pick it back up again.  

Transition Power Hour: Prioritize and Process  

It’s the last day of the conference. You are exhausted and it’s time to pack up and hit the road.

I’d argue that THIS is the most important time in this entire document, this liminal space between education and action that will determine if you actually learn anything from this event!  

Before things get “Back to Normal,” it is vital that you take the time to review your notes, whether alone or as a team. Here’s how I do it:  

  • Give yourself One Hour (or less) to Clean up.
    Before heading home or within 24 hours of landing back in reality, spend one dedicated hour to intentionally review your notes. This isn’t deep work, it’s just filling in the blanks where you forgot or didn’t have time/energy to upkeep things.  
  • Fill in missing details. While things are still fresh, make sure there are enough notes to make your notes make sense. Take out things that don’t make sense or that aren’t actually actionable or useful.  
  • Highlight key takeaways that actually matter. (Do this by hand before running through genAI! Don’t let a robot tell you what was important from your experience!)
  • Extract action items. Do this religiously, even if it's just "Follow up with $Name from $Company." Add them to a separate, trackable document: 
    • in a project management tool like Trello or Clickup,
    • a Personal Knowledge Management System (PKMS) like Logseq, or even
    • your PSA.
  • Use genAI to organize and identify the big ideas. On each page of this document, I have questions. Drop the summary and your notes for each session in a genAI of your choice and have it analyze the event for you. Then, at the end, have it analyze the conference as you attended it!

Here is what I distilled the Business Track at Right of Boom into.  

I fed genAI each session with a few questions, and then fed the outputs together into genAI for the "Big Ideas" and then I edited them down and removed 2-3 points and subpoints I felt were unneccesary.

The Important Takeaways are all me. I even wrote them during the conference as they stood out to me. The Common Themes and Trends is supported by GenAI.

Back to Reality: Notes into Action.

There it is, you have your nice, neat notes reflecting what you learned at a Conference! Now...what...what do you do with them?  

Share the Knowledge with your Team

  • What sessions were actually valuable? (And which were a waste of time?)
  • Is this a good event for you to attend again next year, or is there someone else who would be a better fit?  
  • What key industry trends did you notice?
  • Are there any immediate action items?
  • If you can present ONE THING to implement immediately, what would it be? Make a plan to do it.  

Follow Up with Friends, new and old.  

Debrief with your friends who also attended. What did they get out of the event that you missed? Be ruthless about which product you’re going to try from which vendor following this event and stick with it. Go ahead and write up a short “sorry not interested, do not contact" template email to send to vendors, or email rules to send them to another folder/trash. (You can always come back to them, give them a clear templated no and move on!)

Share the knowledge with others.  

I mean, my notes from Right of Boom literally led to two (maybe three) blog posts on getting the most out of conferences, a video, and probably a webinar reviewing content as well. There is a depth of knowledge that comes from diverse conversations on topics, don’t be scared to have opinions or speak your mind, you never know how that can help our entire industry in the long run! Make videos, blogposts, or LinkedIn Articles. Share the wealth with others who couldn’t make it. Who knows, it may be helpful to you, to help you sort out your ideas better.  

In Closing

My goal in sharing with you how I take conferences notes, is to encourage YOU to get the most out of your conference attendance. However you do that is up to you, but hopefully this framework helps you practically implement how you can best ideate, execute, and close out your event experiences with Action in mind. Remember: 

  1. Know your Why before you go and invest energy upfront to give yourself structure you can use.
  2. Keep it Simple and come back to Notes whenever you stray.
  3. Finish Strong and transition back to reality, prioritizing Action.

If you take nothing else, I hope you consider that a conference isn’t just about showing up. Instead, it’s about capturing insights, making connections, and turning those ideas into action. Take notes that matter, review them before they fade into oblivion, and for the love of all things good, do something with them!

Share this post
El Copeland

Throughout my career, I've had the joy of leading many diverse and multifaceted teams.

Community building, especially within the technical community, is truly at the heart of what I do. I’m dedicated to fostering inclusive spaces where professionals can connect, share insights, and grow a culture of innovation and ongoing learning together, both in-person and when the team is 100% remote. I take pride in my ability to lead with both clarity and empathy, deftly handling the complexities of technology-driven projects while always keeping the human connection at the forefront of every decision.

For companies seeking consulting and project work, I bring a deep understanding of operational efficiency and project management. I am skilled at not only identifying areas for improvement but also implementing strategic solutions that enhance productivity and outcomes. My strong background in technology, education, and people management allows me to seamlessly integrate innovative tools and processes to address specific challenges, ensuring that projects not only meet but exceed expectations, and that teams are motivated, well-coordinated, and focused on delivering and maintaining organizational goals.

Outside the office, I enjoy blueberry muffins, Doctor Who, weight-training, gardening, and spending time with my cats.

See some more of our most recent posts...
June 30, 2025
8 min read

By The [Run]Book: Episode 1

What do webhooks, Agent Trophies, and a 10-year scheduler have in common? In Episode 1 of By the [Run]Book, consultants from Renada and Rising Tide walk through HaloPSA releases 1.86 and 1.88—field-testing features, skipping the fluff, and asking better questions than the release notes ever do.
Read post

Welcome to By the [Run]Book

HaloPSA features, field-tested.

We’re not here to sell you a perfect system. We’re here to show you what’s possible when smart, slightly feral people get curious about tools that were allegedly designed to help us.

By the [Run]Book is a new podcast collaboration between consultants from Renada and Rising Tide, where we dig into the latest HaloPSA features, challenge what’s been handed to us, and ask: What else could we do with this?

No fluff. No shiny demo decks. Just real-world testing, practical breakdowns, and a healthy disrespect for default settings.

By the [Run]Book – Episode 1 Feature Guide

By the [run]Book's first episode breaks down HaloPSA releases v1.86 and v1.88, this episode explored what’s new, what’s weird, and what’s actually worth your time. Use this guide to follow along.

Event Management | 2.186 #798529 | ▶️ 6:06

Create and update tickets based on webhook events—without needing Runbooks.

  • Easier interface for handling alert data
  • Trigger rules based on payload content
  • Map fields into tickets dynamically

Chat Interface Redesign | 2.186 #764942| ▶️ 10:06

The new chat view makes internal and client conversations more manageable.

  • Conversation list/table instead of floating popups
  • MS Teams chat support improved
  • Much more usable in high-volume settings

Tabbed Interface in Halo | 2.186 #446952 | ▶️ 12:03

Multiple tabs now open inside Halo, not your browser.

  • Reduces tab clutter
  • Smooth for screen sharing
  • Plays well when Halo is run as a desktop app

Agent Trophy Feature | 2.186 # 831583 | ▶️ 14:28

Yes, agents can now earn trophies for closing tickets.

  • Visual badges on agent records
  • Available in assignments and dashboards
  • Fun, but scoring logic is a bit suspect
  • Custom Leaderboards via CSS. Mostly a morale booster—not reporting-grade insight

Date Filters, Forecasting Module + TimeGPT Integration | 2.186 #830461| ▶️ 19:41

Prevent retroactive ticket floods when new rules are applied.

  • Set start dates to control retroactive logic
  • Helps avoid spam from old data
  • Crucial for clean automation rollouts

Enforce Unique Email Addresses | 2.186 #829650 | ▶️ 20:43

Avoid duplicate users and weird portal issues.

  • Blocks user creation if email already exists
  • Critical for integrations and self-service portals
  • Best turned on early before it breaks things quietly

Opportunity Variables: Annual, Monthly, One-Off  | 2.186 #828897 | ▶️ 22:31

New fields help break down potential revenue at-a-glance.

  • Available for ticket templates and reporting
  • Auto-updates from quotes (with correct config)
  • Useful for sales forecasting and quote summaries

Runbook Sleep Steps | ▶️ 30:55

Introduce delays in automation logic—finally.

  • Wait X seconds before next Runbook action
  • Great for API pacing or async dependencies
  • Simple but long-awaited

To-Do Groups Linked to Clients | ▶️ 33:28

Tie checklists to specific clients.

  • Good for client-specific onboarding/offboarding
  • Still clunky, but now usable in context
  • Replaces “one-size-fits-all” task lists

Dynamic SQL in Ticket Actions▶️ 33:34

Use SQL-powered fields in your ticket logic.

  • Previously unreliable, now stable
  • Can pull dynamic field values into workflows
  • Adds power to advanced configurations

Xero + Avalara Sales Tax Integration▶️ 34:15

Auto-calculate sales tax in Halo quotes synced to Xero.

  • Uses Xero’s built-in Avalara tax engine
  • Requires invoice.updated webhook enabled
  • Real-time, regionally compliant tax logic

Direct User-to-Client Association | ▶️ 37:40

Users can now be tied directly to clients, no site required.

  • Supports more flexible org structures
  • Great for shared-stock or multi-client setups
  • May simplify certain workflows

10-Year Scheduling Period | ▶️ 42:24

Because someone, somewhere asked for it.

  • Schedule things a decade out
  • Useful for contract reminders or licensing renewals
  • Feels deeply aspirational

Got a Feature You Want Us to Cover?

Send us a message!

July 2, 2025
8 min read

Introducing Rising Tide Proactive Support

Tired of tools slipping through the cracks? Discover why Rising Tide built Proactive Support: a low-lift, high-impact way to stay in control of your systems like HaloPSA, Hudu, and Rewst—without needing a full consulting engagement.
Read post

Built for Busy MSPs: Why We Created Proactive Support

While we pride ourselves at Rising Tide on being clever, we didn’t make this up on our own.

Over the past year, multiple clients told us the same thing in different ways:

“We don’t need a full-on consulting. We just need someone to help us stay on top of the tools we already have.”

“Can you set aside time each month to tell us what’s working, what’s not, and what we should actually do next?”

“Honestly, I just want to know if anything’s falling through the cracks.”

MSPs weren’t talking about emergencies. They meant the small stuff. The not-yet-broken-but-might-be. The features that got launched but never rolled out. The bugs they forgot to follow up on. The process that made sense when they built it... but not anymore.

So we listened and built out a Proactive Support offering for teams like yours. Support that pays attention, leveraging the best of Rising Tide to make the best of your systems. It’s not reactive. It’s not rushed. It’s not about being broken.

It’s about staying in control, without wasting time figuring out where to start.

What You Get Each Month

Designed for Rising Tide clients who’ve already implemented tools like HaloPSA, Hudu, and Rewst, and just want to keep things running smoothly without spinning up a full project or workshop every quarter.

Here’s what Proactive Support looks like in practice:

1. Systems Health Review

A short, focused check-in on the systems you want our guidance on. for:

  • Are automations running like they should? 
  • Are there missed SLAs or ticket pileups that can be fixed with better workflows?
  • Are there any underused (or over-complicated!) features?

You’ll walk away with a small, clear action plan that you can execute on your own or leverage the Rising Tide team to complete.

2. Feature Release Briefing

We read the release notes so you don’t have to. You’ll get:

  • Highlights of what’s new
  • Suggestions for features worth trying and what isn't
  • Warnings about what’s likely to break or change

3. Vendor Liaison Support

We’ll chase the vendor on your behalf. That includes:

  • Logging and tracking bug reports
  • Validating bugs and escalating to dev teams directly.
  • Identifying workarounds and assisting in implementation.
  • Following up on feature requests or stuck tickets
  • Communicating feature requests clearly (and tracking them)

4. Immediate Error Support

If something breaks in a tool we’ve implemented or documented, we’ll:

  • Help triage and fix it
  • Identify if it’s a vendor issue
  • Tell you clearly if it needs escalation into a project

What Proactive Support is Not

To be clear, the Rising Tide Proactive Support Plan is not consulting. Proactive Support is only for systems we’ve implemented and reviewed. It doesn’t include:

  • New tool or system implementation
  • Redesigning workflows or processes
  • Training or onboarding
  • Deep reporting or strategic planning

If we find something that should be a project, we’ll tell you and help you decide how you would like to move forward.

Pricing

$900/month
Includes up to 5 hours of support time
Bundled with licensing or dashboard/reporting add-ons, if you need them.

Let’s Be Real

The goal isn’t to keep you dependent on us. It’s to help you feel like you’re on top of your systems instead of under them.

We’ll help you spot friction before it becomes fire, surface fixes you might’ve missed, and give you the clarity to act, delegate, or table things with confidence.

That’s the tide we’re trying to raise.

Ready to add Proactive Support? Or want to see a sample check-in?
Contact Rising Tide Consulting Today. We’ll show you what this looks like.

July 4, 2025
8 min read

2025 Q3 Newsletter - Get more out of Halo, Hudu, and Rewst

Rising Tide’s Q3 2025 newsletter is here—with fresh updates shaped by the conversations we’ve had with you on the road and in your consulting calls. Check out our new Proactive Support plan, admin tools in the client portal, and hands-on YouTube training for HaloPSA, Hudu, and Rewst. Let’s keep your team sharp and your systems humming.
Read post

It’s been a few months since our last update. We’ve enjoyed seeing many of you on the road at Right of Boom, MSPGeekCon, and Flow. Hopefully you’ve taken the learning and tools you picked up at each even and are using them to their fullest!  

In light of the conversations we’ve had with many of you at these conferences and in your consulting calls, we’ve been building a few new offerings that we hope will help you and your teams continue to learn and grow in your use of HaloPSA, Hudu, and Rewst. Take a look at our new Proactive Support, YouTube videos, and Administrative tools for you in the Rising Tide Portal.  

Proactive Support with Rising Tide

Shaped directly by your requests, the Rising Tide Proactive Support plan is for teams who want another set of eyes on your systems, to make sure you’re getting the most out of your subscriptions. This new monthly support plan includes:

  • A health review of applicable systems
  • Updates on vendor features that matter to you
  • Vendor liaising regarding bugs and requests (we’ll validate bugs and escalate to dev teams directly. If there's a workaround or fix we'll identify that and provide them for you too.)
  • Hands-on support for tools we’ve implemented or reviewed

Read more about it here:
https://www.risingtidegroup.net/thoughts/introducing-rising-tide-proactive-support

Learn With Us

We’re actively growing our YouTube channel to create more and more helpful resources  for you as you implement your tools and automations. Of note, check out:  

  • By the [Run]Book – A bi-weekly series, aired live with our friends at Renada where we review HaloPSA’s release notes and make suggestions on what to implement (and what not to!) in your HaloPSA instance. Watch the first episode here.  

There’s plenty more! Be sure to subscribe to our channel and hit the bell to get notified when new videos drop.

Let's keep your projects moving!  

As a reminder, if you have hours on your pre-pay total, we keep them viable as long as you have a project on the books with us within a calendar year. If you want to know what your current hours are,  visit the Rising Tide user portal at portal.risingtidegroup.net. In this area of our website, you can:  

  • View hours remaining on pre-pay blocks.  
  • Submit and track tickets.
  • Refill Pre-Pay hours for consulting work.  
  • View feature requests and bug reports submitted to Halo by Rising Tide.

We recommend booking an hour at least once a month, and more frequently if you have work you want to get done! We don’t charge cancellation fees, so book time freely with any of our consultants and we’ll get your sorted.  To book time, access your project from the portal to grab your booking link or pull it off any of the recap emails sent.

  • Mendy Green - Halo General, Automations – Halo and Rewst, Hudu General and Migrations from IT Glue
  • Jason Parsons - Halo General
  • Jen Butler - Automations – Halo and Rewst
  • El Copeland - Halo Invoice/Quote/Email Templates, UX/UI, Branding+Marketing

Of Note

A recent change to how HaloPSA processed notifications caused them to break in certain conditions. If your notifications stopped working, update your Permissions - Base role client restrictions to grant all clients to role members. Reach out for more specific instructions if you need it.

Lastly, as a bonus, enjoy the new Rising Tide theme song generated with Suno by our very own Jason Parsons.

Thanks for trusting us and being part of this work with us. We’ll keep refining what we offer based on your feedback so don’t hesitate to reply and tell us what’s working, what’s still messy, and what you’d like to see next.

Until next time,  

The Rising Tide Team