November 3, 2026

Building an Emma campus: How Columbus State runs email across every department

About this webinar

When offices across campus all need to send email, who helps them do it well? At Columbus State University, it’s a small central team. Michael Tullier and one teammate share the internal communications role, and together they support about 25 Emma sub-accounts, coach campus senders, and decide which messages go out as university-level email.

Michael walks through how Columbus State moved from listservs to Emma with a slow rollout, and what that time let his team build: auto-populating groups synced from Ellucian Banner, guardrails for each sub-account, and weekly e-newsletters for students and employees that replaced a stream of one-off campus emails. He shares how his team uses the dashboard to spot over-emailing and rising unsubscribes, how Emma pinch-hit during campus CRM outages, and which automated journeys are next. The session closes with a Q&A covering contact sharing, sub-account costs, SMS, benchmarks, personalization, and more.

You’ll walk away knowing how to:

  • Decide what deserves a university-level email. Learn the litmus tests Columbus State uses, and why most campus announcements now go into a weekly e-newsletter instead.
  • Set up sub-accounts with the right guardrails. See how auto-populating groups from Ellucian Banner control who each department can email, and how approval settings work when students have access.
  • Coach campus senders with real data. Find out what Michael looks for in the dashboard, from send frequency to unsubscribe rates, and how he uses the mailing score to start conversations with departments.
  • Keep your subscriber count in check. Hear the questions Michael asks before handing out a sub-account, especially when a unit wants to add new external contacts.
  • Plan your first automated journeys. Get ideas for birthday and work anniversary emails built from data your campus already has.

 

Webinar speakers

Who you’ll hear from

9551c3fd-b66f-4547-8cd3-271ad14ab959

Michael Tullier, APR

Columbus State University

Executive Director, Office of Strategic Communication and Marketing

d7758d53-b4ed-4baf-bdfa-3d18e0156391

Lori Farrell

Emma

Senior Customer Marketing Manager

By the numbers

What building an Emma campus looks like in practice for Michael’s team

25

Emma subaccounts, one small team

2 weeks

lead time for finalizing emails

24 hours

before judging email performance

Reading materials

Welcome and housekeeping

[00:00:03] Lori Farrell: Hey, everybody. My name is Lori Farrell, and I’m the senior customer marketing manager for Emma. Thanks for being with us today. A couple of things before we get started.

Next to your chat, you’ll see a section specifically for Q&A. Please put any questions you have during the session there. Sometimes the chat moves fast, and we want to make sure we don’t miss your question.

Yes, this session is being recorded. The recording will be emailed to you about two hours after the webinar. If the link doesn’t work right away, it may still be processing.

We’re also launching our new customer advocacy and community platform, Opted In, this Friday. We’re very excited about it. There will be rewards, opportunities to network with each other, and more. I’ll put the link in the chat, and we’d love for you to apply and join us there.

And one last thing. I know some of you may not be Emma customers yet. We’d love to have you join us, too. If anything today sparks your curiosity, click the link in the chat and see what we’re all about.

Now I have the pleasure of introducing Michael Tullier, executive director at Columbus State University. Michael, would you give a short intro about yourself?

Meet Michael Tullier

[00:02:08] Michael Tullier: Sure, Lori. Thanks. I’ve worked in public relations for a little over 30 years now, most of that in higher education. For the last half of my career, I’ve focused on some of the areas Emma is helping us with today: executive communications, internal communications, and a variety of marketing communications for higher ed institutions.

I’ve been at Columbus State, in Columbus, Georgia, for a little over six years. I lead a team that oversees branding, marketing, communication, multimedia, and social media, and we consult with others across campus who support those functions.

I want to say a particular thanks to my University System of Georgia colleagues who are joining today, and a special thanks to my Columbus State coworkers who are here to keep me honest and make sure I’m not overselling what we’re doing. They’re great partners on campus.

[00:03:08] Lori Farrell: So if he’s not telling the truth, put that in the chat, and we’ll take care of it afterward. I have my notes over here, so if you see me looking off screen, that’s why. I have several questions we talked about ahead of time, but we might bounce around a bit.

Why Columbus State moved from listservs to Emma

[00:03:24] Lori Farrell: First, how long have you been using Emma? And if you were using something else before, what made you look for something new?

[00:03:38] Michael Tullier: I came to Columbus State about six years ago, during the summer of COVID. If you worked in that environment, you know what that was like. The university was already evaluating email marketing platforms. At that point, we were a Google campus, and we were using listservs, by and large, to send information to particular audiences and user groups on campus.

It had already been decided that we needed something more robust, something easier for our IT staff to maintain than listservs, especially when it came to putting up guardrails: establishing permissions, handling people opting in and opting out, and moderating those lists.

We realized there were benefits to a platform like Emma. There were also all the back-end benefits you just don’t have with listservs and regular email: readership analytics, a macro view of scheduling, and a real understanding of the communication ecosystem on campus.

[00:04:48] Lori Farrell: I think a lot of people hear “email marketing platform” and think of brands like Target or Nike, and they don’t realize it can help anybody who’s sending emails.

How a slow rollout set up 25 sub-accounts

[00:05:03] Lori Farrell: You have lots of sub-accounts that you manage. What did the rollout look like, and how long was it before departments felt enabled to send emails on their own?

[00:05:18] Michael Tullier: We support about 25 sub-accounts out of our office now, and we’re a small team. I have to give a big thanks to Simone, my partner in internal communication management. She’s the frontline person who makes those sub-account assignments. Then I come in on the back end and do some consulting on each unit’s objectives.

To your question about the rollout, it was very slow. At the time, we were working remotely as a campus, so most of our institutional communications were happening at the communications and marketing office level. That gave us the opportunity to get familiar with the platform.

If you’ve worked with a drag-and-drop web building environment like WordPress, Emma is going to be a very easy transition.

The slow rollout also gave us time to figure out what our processes could be. Our IT team was largely unfamiliar with Emma, and as a communications team, we were largely unfamiliar with IT’s side of things. So we had the chance to think about building auto-populating groups and what subscriber management would look like. We built some infrastructure around our use of Emma so we didn’t feel like we had to be live, on board, and ready to support the number of users and sub-accounts we have now.

Those sub-accounts are in the twenties now, and they’ve grown gradually over time. That certainly wasn’t a first-month or first-six-months threshold.

Do listservs still have a place?

[00:07:08] Lori Farrell: Thank you. I see a question I think would be good to answer now. Jackie is asking: are your listservs completely gone since you moved to Emma?

[00:07:19] Michael Tullier: Thanks, Jackie, and hello. Jackie is one of our Georgia colleagues in communications. We do still have some listservs for things that don’t require the level of attention Emma gets. Those have largely been decommissioned at the university level, but some departments still use them.

We’re not using Emma when a department chair needs to email his or her faculty. We’re not using Emma for “your grades are due” or “pay your bill.” Some of those messages happen in other CRMs on campus because it makes sense. Others happen at the email level within a small group, either through an official listserv or a group a department chair has set up for their department.

That’s our threshold for university-level communications. If a message needs to be curated, if it’s part of our student and employee engagement work, or if the analytics matter to us, then we invest the time to manage it within our office. There are a lot of other campus communications that don’t happen in the Emma platform, and that’s just the ebb and flow of university operations.

What a typical week of campus email looks like

[00:08:42] Lori Farrell: That’s a good segue into our next question. What kinds of emails go out through Emma in a typical week?

[00:08:51] Michael Tullier: By and large, institutional communications: the things we as an institution need to communicate to employees, operational information, and event announcements.

We have a weekly e-newsletter for our students and a weekly email for our employees. Those have been great for us to leverage Emma, because before we had a good cadence on those, we were getting requests from all over the place: “Hey, can you send this out to campus?” We were the Emma keykeepers, so everybody came to us.

Now we’ve created an expectation that if you have a campus email and it isn’t earth-shattering or mission-critical, it’s going to go into that weekly email. That creates a stream of convenience for our employees. Their critical information is in a single source that’s scheduled each week.

There will still be things like “a pipe burst in this building,” and we want to get an email out. And there will be higher-level messages we use to enhance student and employee engagement. If we need to put special emphasis on an event or introduce it before it goes into the e-newsletter, great. Now we have that Emma email we can link back to from the newsletter. We don’t have to tell you everything again. We just provide a little reminder and a click for more information.

We also use it for urgent communications. We’ve had a couple of CRM failures during my time here, and Emma has been able to jump in and support communications that otherwise would have been disrupted.

Emergency management is also big. Our office is the interface with our university police department. When we go into emergency management mode, whether it’s severe weather or another public safety issue, we partner with the police department to communicate with students, employees, and stakeholders.

And we do a little experimentation. Sometimes we’ll use Emma for special campaigns just to see how they perform from a marketing analytics perspective before we put them out into the wild, so to speak.

What does it mean to be an “Emma campus”?

[00:11:17] Lori Farrell: I remember you telling me about the CRM going down and how easy it was to move everything quickly and get that communication out through Emma.

One thing we really liked hearing in our first conversation was that you described Columbus State as an Emma campus. What does that mean to you?

[00:11:43] Michael Tullier: We’ve really been able to streamline our campus communications. We still hear, anecdotally, especially from students, that they’re getting a lot of emails. We’re working hand in glove with departmental communications that go through Outlook, and faculty have to email students about class assignments and everything else. There will always be a lot of touchpoints in the email world.

But Emma has allowed us to create some litmus tests for what we want to elevate to university-level communications. There was a lot of trial and error when we first started, which was another great benefit of the slow rollout. We could say, “We don’t have to email you six times today about this event tomorrow. Let’s look at it from a strategic communications perspective.” Just because you have the tools to do it doesn’t mean you should. That’s a role our office has taken on, both inside and outside the Emma environment.

Which teams use Emma (and which don’t)

[00:12:57] Michael Tullier: We have some other systems in place. I saw Krista asked whether our advancement team uses Emma. We use Emma for our monthly alumni and donor e-newsletter. But advancement handles a lot of donor communications, especially fundraising campaigns, through Raiser’s Edge, which is a Blackbaud product. There are benefits to keeping that communication within a single system, because we can record donor engagement within that platform.

But by and large, for standalone communications, if it’s going out as an internal communication, we’re using Emma.

How the central team supports sub-accounts

[00:13:36] Lori Farrell: Perfect. Eli has a question that ties into one of mine. Eli asked what your sub-account structure or strategy looks like. My question was similar: how are you collaborating with those sub-accounts? Are you building and sharing templates, sharing assets, anything like that?

[00:14:00] Michael Tullier: It’s still a little bit of the Wild West, Eli. I’d love to say it’s clean and structured, but we operate in a world where everyone has email, everybody has a Canva account these days, and everybody knows design. For those of you who want to empathize and sympathize with that environment, I’m sure our world is a lot like yours.

When people express an interest in having a sub-account, it shows they’re taking communication seriously. The benefit to us is that once they have an Emma account, we can see the type, cadence, and tone of their emails and jump in where we may never have seen that communication before. We weren’t part of their offline Excel spreadsheet where they were copying and pasting email addresses. Now they’re putting those addresses into Emma and communicating through Emma.

Our team can see that through the macro dashboard. We can say, “Okay, as an institution, we sent 12 emails today, and three of them came from the same sub-account.” Then we can jump in and do some consulting with them.

It also means we always have access. If someone comes to our office and says, “I just got an email from XYZ department, and it looked weird. It had the wrong colors, it didn’t have the right logos, or something was questionable,” we have the ability as super users to look at it and go back to the department in an instructive way to help them out.

I wouldn’t call it a strategy, unless, Eli, you want to call it that. We have some people who are very adept at drag-and-drop email builder environments, and with a little instruction, we let them go off and do their thing. Others come to us and say, “I’ve never done this before.” That’s when I’ll sit down with them once the sub-account is built and talk through what their goals and objectives are and why they want Emma access.

One important question we ask is who’s going to receive their emails. Our Emma subscription is based on contacts, by and large. All of our students and employees are already in Emma as unique contacts, so internal sends don’t affect our subscription limit. But when we onboard sub-accounts that are likely to add external contacts, we have to keep a closer eye on how large our subscriber pool is growing. We don’t want to risk exceeding our contract limits for the year, so that requires some consultation, too.

[00:16:48] Lori Farrell: Chelsea is asking whether other departments can curate their own messaging, because her team doesn’t have the resources to create every department’s emails. Chelsea, it depends on how you want to do it. Yes, they can. You can set templates for them, and they can create their own messages. It’s really whatever works best for you.

[00:17:11] Michael Tullier: And to that, Lori, the benefit is that at the level we operate within our Emma account, we can drop into those sub-accounts. We can fix things if they’re getting error messages. Sometimes they’ll create a long email and get a spam warning, and we can help them with that.

We can also address accessibility, which is a growing regulatory need on our campuses, and a lot of times people turn to folks in our function to help with it. If there are questions about accessibility or brand, we can do some hand-over-hand consulting using live messages they’ve already built in their Emma sub-accounts.

We can also share. There have been a couple of situations where a faculty member or department chair came to us and said, “We’d like to do an e-newsletter, but we’ve never set one up.” So we take one we’ve already built, tailor it to their needs, and push it out to their sub-account. We know it has the right colors and logos. And we’ve been able to make it different enough from the other units we support, while keeping some cohesion.

It’s what we do with any communications project. We sit down and assess needs, opportunities, and the end user’s technical capabilities so we can design a product that meets their needs.

Approval workflows and sub-account guardrails

[00:18:44] Lori Farrell: Forgive me if you already covered this. I got a little caught up in the Q&A looking for relevant questions. A couple of people are asking about your approval workflow, and whether you rely on other managers or your team handles all of the approving.

[00:19:05] Michael Tullier: No, we didn’t cover that, and it’s a good point. That’s something we discuss with sub-account users, especially when a department chair, faculty member, or department director asks us for sub-account access. Part of our conversation is who needs access.

Because of how our email addresses are structured on campus, it’s easy to tell when we’re giving a student access to a sub-account. We don’t disallow that, but it comes with extra instruction. In those situations, we can offer the sub-account owner guardrails so students can’t send anything without the sub-account owner approving it.

At the macro level, we don’t do the approving, but we will go back and look at emails that went out when a question comes up. Most of the people we assign sub-account access to already have quite a bit of administrative authority on campus. We’re giving Emma access to trusted, known users rather than someone who says, “I’m a faculty member, and I want to be able to email stuff out.”

Auto-populating groups with the Banner integration

[00:20:28] Michael Tullier: We can also regulate who each sub-account can email, mainly for internal communication. One of the nice things that came out of our build-out is that we’re a Banner campus. Our student and employee data is all housed in the Ellucian Banner system, so we can build auto-populating subscriber groups in each sub-account based on Banner characteristics.

Some of our accounts have all employees and all students. We can break that down further: all part-time students, all full-time students, all graduate students, all undergraduate students. Those are specialized subscriber groups we can set up in Emma.

At the departmental level, maybe the Department of English just needs all English students. Or maybe biology wants all full-time biology students or all part-time biology students. Those are all fields within Banner. I can only speak specifically to Banner, but I believe the APIs can be set up with any of these systems. They communicate back and forth every night, adding and removing people as they move in and out of those groups.

That lets us be more particular, so the Department of English, in my example, can’t email everybody. Sub-accounts also provide guardrails so not every department on campus can email all of our alumni. That’s a separate group, and only certain people have access to it. Between our IT department setting up auto-populating subscriber groups and our team setting up sub-accounts for very targeted reasons, we keep each sub-account’s reach where it should be.

Should students and staff be able to opt out?

[00:22:24] Lori Farrell: Something you just said makes me want to ask Jessica’s question now. Are you okay with students and staff being able to opt out of these emails?

[00:22:35] Michael Tullier: For our university-level sub-accounts, the ones that communicate on behalf of the Division of Student Affairs and the university, meaning our Office of Strategic Communication and Marketing, we’ve removed the opt-out option from our Emma footer. We consider those official means of communication on behalf of the university, which is our communication policy on campus.

The caveat I tell anybody is that removing the unsubscribe link from the footer doesn’t mean someone can’t opt out. They can block you. They can mark your address as junk mail or a junk sender in Outlook.

We practice some subscriber list health on occasion. When we see an uptick in unsubscribes through Emma, we’ll send an email through Outlook from our office’s official account that says, “We’ve noticed you’ve opted out. This is a means of official university communication, and we encourage you to opt back in.” But once you opt out of Emma, you’re opted out. We can’t override that. It requires user action, which I wish more companies practiced.

Why brand-locked templates are on the wish list

[00:24:15] Lori Farrell: Right. I have one more question on sub-accounts before we move on. Krista asked: is there a reason you’re not using brand-level templates and locking them so sub-accounts can’t go rogue?

[00:24:27] Michael Tullier: Bandwidth, right now. It’s on our wish list. As I mentioned, it’s me and one other person who share the internal communication role, among other things. If we had the bandwidth, we certainly would, and it’s on our list for this year.

Using the dashboard to coach campus senders

[00:24:43] Lori Farrell: Sounds good. I know you use the dashboard to coach people, and you mentioned earlier that you can go in and see if somebody had an error. Is there anything specific you look for when you open the dashboard?

[00:25:09] Michael Tullier: Frequency is probably the most important thing. I personally subscribe to some units on campus, including research and outreach units, just to gather news, story, and social media ideas.

Monitoring the dashboard when I drop into our account lets me see what else is going on. We also have great customer success support from Emma, and we review the dashboard and our macro analytics quarterly. Blake is our customer success contact, and he helps us triage where we’re seeing high unsubscribe rates in our external-facing sub-accounts, which sub-accounts may be underperforming on engagement, and which ones are over-emailing.

Sometimes that’s just seasonal. This week, for example, is ethics awareness week in the University System of Georgia, so our Division of Legal Affairs is sending a bit more than usual. The dashboard gives us all eyes on the email landscape here on campus. I don’t pretend that’s everything we send. There’s a lot we don’t know about, but thank you, Emma, for helping us see what we do know.

Why choose Emma for campus email?

[00:26:43] Lori Farrell: This next question might be especially useful for anyone considering Emma or not using it yet. What’s your selling point for Emma, whether it’s subscriber management, aesthetics, deliverability metrics, or something else?

[00:27:05] Michael Tullier: I hate to say the whole package, but it really is. You’re not just sending an email out into the void. If you’re not using any email platform at all, Emma or something like it would be ideal, because it gives you a level of design that Outlook or Gmail can’t.

Accountability is another big point. We get a lot of people who say, “I didn’t get that email.” I can drop into Emma and say, “Yes, you did, and you ignored it.” Or maybe there’s a communication issue, or maybe you unsubscribed and didn’t realize it. That’s an opportunity to maintain the subscriber health I mentioned earlier.

And probably the most important thing in our industry is communication effectiveness. We can’t measure that holistically through engagement data, but it’s a good start. It tells us whether we’re building resources into our communications that people find helpful, whether that’s links, buttons, or anything else.

If you’re not working in email yet but you work in an allied area like website content management or content strategy, the same principles apply. Is my information in the right spot? Am I losing people because they’re not getting to the bottom of the email or clicking anything? Emma gives us information we can use to make reasonable assumptions. When readership or engagement drops off, I can go back and say, “Look, you’ve oversaturated your audience with the amount of messaging you send.” That’s real data I can use when I’m wearing my consulting hat with a department chair or an outreach center director.

[00:29:08] Lori Farrell: I love that you said it’s the whole package. I can attest to that, because I use Emma to email our customers. I’ve used other platforms in the past, and I learned Emma on my own when I started. I had resources and help, of course, but I agree with you 100%.

Next up: automated birthday and work anniversary journeys

[00:29:29] Lori Farrell: You mentioned automation is on your roadmap. What are you hoping to set up, and why start there?

[00:29:38] Michael Tullier: So much of our communication is one-way. We’re not doing admissions marketing. That’s handled by our admissions office, and they do their own engagement. But we’re always looking for opportunities to avoid pushing out only one-way communications that sound corporate or institutional.

One thing our campus culture group challenged us to do, at the recommendation of our employees, is celebrate birthdays and employee milestones. So we’re looking at automation built on information that ports over from Banner. If we have your birth date or hire date on file, we’re looking at automated triggers that send you a birthday graphic or virtual birthday card. That’s on top of the more intentional things we do once a year to celebrate employee accomplishments and milestones. How can we make those part of an automated flow?

[00:30:52] Lori Farrell: I love the birthday idea. It’s such a nice touch. My birthday is this month, and I’ve started getting all those little emails from brands.

[00:31:01] Michael Tullier: And when we do it, it’ll be so much better than how it was done when I started. The president’s office scanned a birthday card on a copy machine, dropped the graphic into an Outlook email, emailed about 40 people at once, and said, “It’s your birthday month.” No slight to them. That’s what they were working with at the time. But now the technology is here.

Will someone know it’s automated? Sure. But did someone take a little time to send me a personalized message? That’s what these little touches are about. And there are a lot of other little touches Emma makes possible. We can put your name in a subject line or in the body of the email. It’s elementary, but it’s there if you build it into your work.

Working with Emma’s customer success team

[00:32:00] Lori Farrell: For sure. What has your relationship with Emma been like? You mentioned Blake earlier. How has the support been?

[00:32:15] Michael Tullier: It’s been great, and it’s matured over time. Over the past year or two, I’ve seen a more intentional focus from our support team on making sure we understand the tools we’re using. We also have Sarah, who’s on the call today. She’s our higher ed expert, and she joins the conversation when we have those questions.

We do Emma work every day, but we don’t always look at Emma from an account management perspective and use those tools. Blake and Sarah have been great about reminding us when we’re underutilizing something. Some of today’s Q&A has reminded us there are still opportunities we’re not taking full advantage of.

That’s the nice part about this community. You mentioned the new Emma program that will bring the community together in the next week or so. Like any software or any communications function, it’s nice to have a group of people you can drop in on. So I’m thankful for that kind of support from Emma. It’s not just a slide deck emailed to me once a month with a performance report. I can have scheduled conversations, and I can also reach out and say, “Someone just got us close to our subscriber cap. How do we declutter our subscribers and figure out what sent us over?” Or, “I’d like to set up these triggers, but I’ll need some help once we get all the pieces in place.” Those are the kinds of questions I know I can bring to our team.

The feature that changed his work most: the new email builder

[00:34:02] Lori Farrell: That’s good to hear. I have two more quick questions, and then we’ll look at the Q&A. Of the newer Emma features you’ve adopted over the years, which one changed the way you work the most?

[00:34:21] Michael Tullier: The new email builder. We started with what Emma calls the legacy builder, which isn’t available anymore. What new users are used to isn’t what legacy users like us started with. The email builder is light years ahead of what I started out with.

It lets us integrate a lot of different engagement features, like buttons, and I can use that data to go back to the people who request communication projects. One thing everybody wants to do is put a video in an email. I can go back and say, “For this group that’s done videos before, they’re not performing the way we’d like.” Having that data has even helped us head off some time-consuming projects. Otherwise, someone would have had our office produce a video, we’d drop it into an email, and then we’d watch it underperform.

So it’s a combination of what we’re seeing in the email builder and the ability to pair it with the data and analytics enhancements.

Advice for campuses just getting started

[00:35:48] Lori Farrell: Thanks. And my last question: what’s one piece of advice for someone just getting their campus started with Emma?

[00:36:01] Michael Tullier: I alluded to it earlier: be intentional. We talked about the Wild West potential of creating sub-accounts all the time. We’ve learned to ask some questions.

We’re always adding new users to existing sub-accounts. But when someone comes out of the blue and says, “I’d like a sub-account. I hear y’all offer that,” we push back a little more. We fully support our Emma subscription at the enterprise level. It isn’t charged back to units that have sub-accounts. So we want to make sure each one will really be used, especially if they’re adding a new group of external subscribers, because that affects the total number of subscribers on our account.

If a sub-account sits unused, and then they decide, “Let me send one email,” and never send another, they’ve done two things that hurt the communications ecosystem here. First, they’ve added to our subscriber count with contacts they’re not going to use. Second, they’ve created a communication expectation and haven’t followed through on it. If they’re going to have issues with bandwidth or cadence, we’d like to know that before we assign them an account.

So it’s all the things that come with intentionality. What are your goals? How frequently will you send? Who are you communicating with? What technical support will you need? We don’t have the ability to spend 20 hours a week on one sub-account. We want to make sure we’re handing the keys to someone who either has that level of technical proficiency, or we budget time to support their needs when we can.

Q&A: Contact sharing and deduplicating records

[00:37:49] Lori Farrell: Perfect. We’ve reached Q&A time, and we have lots of questions coming in. Some you may have covered, but I’ll ask anyway in case there’s something you want to revisit.

This one has an upvote, so two people want to know: have you enabled contact sharing, and what are your key contact fields? How do you decide which segments and fields are shared with which sub-accounts?

[00:38:26] Michael Tullier: We don’t share groups among our sub-accounts, because most of them have a pretty niche need. For example, we have a math collaborative outreach program that communicates with K–12 math teachers. We don’t need to share that subscriber group with any other sub-account.

I’d say 90% of our subscriber group sharing happens at the API-automated group level. We create the sub-account, and our IT colleagues drop in the auto-populating groups. If the Department of English needs a sub-account, IT builds the English faculty and student groups for them. They don’t have to do anything on their end, and it lets us control that sub-account’s reach.

Others, like our museum or art gallery programs, communicate internally but also with their alumni and donors. They’ll reach out to our advancement team and get the approved list from that database, which requires some manual updating.

Emma has been great about deduplicating. On campus, we use our employee and student ID numbers. Making that a field in Emma means we avoid duplicates, because that number helps dedupe profiles. Imports from our alumni and donor database include a unique profile number, too. As long as we use that number, it sets the North Star for any import, so Emma knows those people are already there and we just need to update their information. We avoid duplicating anyone just because they changed their email address.

Q&A: Do sub-accounts pay for their own usage?

[00:40:38] Lori Farrell: If you’re comfortable answering this, a few people want to know whether your sub-accounts pay for their own Emma usage or if it’s covered as a whole.

[00:40:53] Michael Tullier: Right now, no, they don’t pay. It’s something we’ve discussed in the past. Administratively, we’ve moved as an institution toward providing software as a service at the enterprise level. We did talk about maybe charging a nominal fee to units with their own sub-account.

Ultimately, it comes down to their share of our subscriber agreement, our count of unique email addresses. As long as a sub-account uses email addresses already in your Emma account, it’s not extra. The challenge comes when we add a sub-account that’s communicating with people we’ve never contacted before.

I used the math example. We have all the local math teachers in our Emma account. Now say another program wants to do the same thing with science, but none of those science teachers are in the account. They have a thousand they want to add, which adds a thousand toward our subscriber agreement. That’s where we have to think things through. Depending on their budget model, an institution might say, “We’ll charge you $500 a year for a sub-account,” or, “We’ll offer it as a service.”

Q&A: How much oversight do departments get?

[00:42:24] Lori Farrell: On that same note, Britney, if you’re still here, I hope your child feels better soon. Britney asked whether you have any units that manage and send their communications independently, without oversight from your office.

[00:42:41] Michael Tullier: All of them do. They all have the capability. If a department chair or dean says, “I really need you to look at this before it goes out,” we can do that. But this model is the same one we practice for non-digital communications. We do a brand compliance review on anything printed. We look at logos, colors, and so on, but the content belongs to the unit. Unless it’s something at the institutional level, the constituency owns its communication.

[00:43:24] Lori Farrell: Thank you.

[00:43:27] Michael Tullier: I’d need to be fully deputized if we started looking at everything.

Q&A: SMS and training

[00:43:33] Lori Farrell: Do you also use Emma for SMS?

[00:43:37] Michael Tullier: We’ve talked about it. I see that question comes from Chelsea. Hello, Chelsea. We have so many other SMS systems on campus that are very niche. Our student success team, which includes academic advisors, financial aid advisors, and admissions, already has SMS built into their CRM. And we have a separate system for emergency communications on campus.

So we’re comfortable not being involved in SMS, although it’s there, and we keep reminding our IT team it could be an option for us. It’s like the fundraising campaigns that come out of Raiser’s Edge. When there’s an opportunity to keep something within a single platform, it seems better for everybody. I also don’t want to be regulating SMS on top of emails I’m not seeing.

[00:44:30] Lori Farrell: Sure. Jackie asks: what kind of training do you provide beyond the Emma training videos?

[00:44:38] Michael Tullier: The Emma training videos are our first go-to. If people are trying to do things we don’t feel best suited for, or it comes at a time when we can’t sit down with someone, the knowledge base on the Emma website is great.

Of course, some people come to us and say, “I’ve never done this before,” which scares me a little before handing them the keys to Emma. Next week, I have a conversation with the new director of our faculty center, which supports faculty development on campus. We’ll talk through what he wants to do. I know he wants an e-newsletter and might want some reminders. Based on that, we can repurpose something we’re already doing and send it to his sub-account with probably 60% to 70% of the ideation done. Then we help him get comfortable if he needs that. If not, we’ve given him resources to run with, and we can jump in when he runs into technical issues.

Q&A: Benchmarks, open rates, and the mailing score

[00:45:41] Lori Farrell: I like this question from Eli: do you have established benchmarks you use to evaluate campaigns?

[00:45:48] Michael Tullier: It depends on the sub-account. One thing we’re trying to teach sub-account users is that a static message makes it hard to track open rates. A reader has to do something, like click or download the graphics. If that’s all you have in your email, it’s going to be hard to measure true opens, because people block images and tracking, so the email server never registers the engagement that triggers an open.

So we help people understand that if you build in a link for more information or a button to a website, anything that gets a reader to take the next step will help you better evaluate your open rate and, hopefully, your engagement rate. Sometimes engagement will be really low simply because there’s nothing in the email but a paragraph of information.

We pay closer attention to large-audience, content-rich emails like e-newsletters. We put a lot in there, and it helps me decide what people care about. If we include a link about knitting and crocheting every week and no one’s interested, we’ll take it out and replace it with something people might be interested in.

What I love about the Emma platform is that the response analytics provide a mailing score that benchmarks you against others in your industry. To me, that’s the quick-and-dirty answer to “Did this email perform better than we expected?”

If you’re not an Emma user, the analytics give you a heat map, open rates, and, within reason, what kind of device and operating system your email was opened on. That helps us decide whether we’re designing more for desktop or mobile users, or for Android versus iOS.

At the top left is the mailing score. It’s benchmarked against our past performance and against other Emma users in the higher education sector. If I get an eight or a nine, I’m outperforming the class. If I get a four or a five, I know something happened and I need to dig in. If I’m seeing eights, nines, and tens, I feel good about that email, especially if I was just letting people know a pipe burst and not to go to a building because there’s no water in the bathrooms. If that scores well, great, but there’s nothing else I could have done to increase engagement on that one.

[00:48:48] Lori Farrell: It feels almost like a game when I send an email and watch the score to see what it’s going to do.

[00:48:54] Michael Tullier: Well, I had to train myself, because Emma’s data is best after 24 hours. We have a lot of people on campus asking, “Tell me, did that perform well?” And I say, “Let’s give it 24 hours first, and then I’ll let you know how it did.”

Sometimes it takes explaining what that number means. The nice thing is I can turn the response report into a PDF that shows the screen, or export the data as a CSV file. That helps me educate people. Someone will say, “I keep sending emails, and no one’s clicking them.” And it’s like, “Well, maybe what you have there isn’t really worth clicking on.”

And I say it much more nicely than I just did. Much less judgmentally. I try.

Q&A: Connecting Banner and Raiser’s Edge data

[00:49:45] Lori Farrell: Great question from Victoria: how do you handle data integration for internal and external audiences, especially employees who may also be alumni?

[00:49:58] Michael Tullier: Data integration. I’m not sure I understand what that is.

[00:50:02] Lori Farrell: I’m wondering if Victoria is asking how you have Ellucian Banner connected. I’m not 100% sure.

[00:50:07] Michael Tullier: Banner is fully connected for us. Raiser’s Edge, the Blackbaud product, is not. So we rely on our advancement team to give us manual updates for our alumni and donor subscribers for the e-newsletter.

We send that newsletter once a month, so it’s pretty easy. Simone and I build it, and when advancement signs off on the e-newsletter, they also export an updated mailing list for us. That import takes all of two minutes. It usually happens on the back end while we’re cleaning up content, and then it’s ready to schedule.

We can also A/B test subject lines, which is a nice feature, especially for some of our external groups. I don’t need to A/B test “the pipe broke.” But for a special campaign, we might want to be a little snazzier with the subject line.

Q&A: Timelines for email requests

[00:51:11] Lori Farrell: Let’s see. Mark asked: do you have an established timeline for email campaign requests to be built, or an approval timeline?

[00:51:26] Michael Tullier: Oh, Mark. Like everything else in our industry, it’s “Right now. Can you send it?” We try to build those expectations in.

Fortunately, if our office is promoting something, we can plan ahead. We have a veterans program on campus on November 11, and I’m already talking with the unit that organizes that event. We know we’ll do a public announcement, put an article on our website for campus news, and include it in the student and employee newsletters. It’s nice that the campus email announcing it can be part of that communication flow. Those are predictable. I tell people we need to get it out two weeks in advance, and it needs to be nailed down.

Then there’s the operational stuff, the institutional announcements, the things that just come up, and we fit those in. Fortunately, most of our Emma communications are structured very similarly to the last one we sent. For emergency communications, we already have severe weather templates with what we said last time, and we just update them.

That’s the agreement with our police department. We’re not going to write five paragraphs about the weather situation. We’re going to say: bad weather is coming, here’s what you need to do, here’s the university’s response, and that’s it. There are probably three sentences we update before we send it. So the expectation is that if it’s last minute, we’ll probably recycle something we’ve used before.

Q&A: Personalization and dynamic content

[00:53:11] Lori Farrell: Thank you. We have six minutes left, just so we’re both aware. Do you use dynamic content in any of your templates or communications?

[00:53:26] Michael Tullier: We use variable fields, especially for messages we want to feel a little more personal. So it’s not just “Dear Students” or “Dear Cougars.” The Cougars are our mascot, by the way.

The president likes to send a couple of messages to students each semester, around midterms and finals, to encourage them. We want those to feel more personal, and we can do that. The reassuring thing is that we’ll always have a first name for our employees and students. In fact, Banner has a preferred name field, and we import that into Emma as well, so we can choose between a student’s legal first name and preferred first name.

When we’re less sure about the accuracy of the data, we’re more careful. In the advancement world, there’s always a little squishiness. Are we using the right first name? If we address “Mrs. John Smith” as Jackie, will Jackie be offended that we used her first name instead of a more formal one? Or maybe we don’t use the right graduation year because someone has two or three. When it gets squishy, we probably back away from dynamic data.

But I do like dropping first names into subject lines on occasion. “Lori, it’s time to register,” when we’re helping our student success team nudge students to register. Or, “Lori, this giving opportunity is perfect for you,” if we’re partnering on an event with our advancement team. It’s all there, and we use it to the extent we’re comfortable with our data. If you’ve used mail merge in Microsoft Word, it’s a very similar process. You can also build in a default, so if someone doesn’t have a first name, it falls back to “Dear Cougars,” “Dear Employee,” or “Dear Student.”

Q&A: Subdomains and communication policies

[00:55:30] Lori Farrell: Are you using a subdomain to send from Emma?

[00:55:34] Michael Tullier: We’re not, but I’ll have to think about the advantages. I’m putting that on the list with the automation and the brand templates.

[00:55:43] Lori Farrell: I think you may have touched on this, but for the sake of not missing anything: did you adjust your formal institutional communication policies when you adopted Emma?

[00:55:58] Michael Tullier: We didn’t. I think we’re fortunate and unfortunate at the same time from an accountability standpoint. We’re pretty flexible, and we have executive support, so we’re given a lot of room to use judgment on the types of communications we send.

We don’t have a formalized policy because we’re not a very decentralized campus when it comes to communications and marketing. It would be different at a large institution where every college, academic unit, and outreach center has its own communicator. Very few people outside our team have a communication responsibility defined by HR. A lot of people do communication work because they maintain social media accounts or something else.

We know some people will come to us with questions, and we know some people need a nudge every once in a while to get back in their lane. But it’s not a large enough operation that we’re seeing infringements every day. So we try to take more of a coaching approach than a regulatory one. That presents its own challenges.

Q&A: Auto-enrolling students into newsletters

[00:57:16] Lori Farrell: We only have two minutes left, so maybe a quick answer on this one. A couple of people asked whether you auto-enroll students into certain newsletters or whether they opt in themselves.

[00:57:30] Michael Tullier: They’re auto-enrolled to the extent that they’re automatically subscribed in a particular sub-account. Every student will show up in our sub-account for university-level communications and in our student life account. We also use those API auto-populating groups for targeted communications. If a message pertains only to graduate students across campus, our IT department has a grad-student-only group for us. If it’s for students in a particular academic program, we can do the same thing.

The one thing we haven’t drilled down to is communication based on geography. For example, you work in this building, so when the pipe bursts in your building, we email just you. It’s possible, because we could use your office location in our CRM. But people move all over campus going to meetings. That’s been an interest and a challenge, especially for emergency communications when we need to say, “Clear this building.” We see the same challenge in our SMS platform. It’s hard to know that you’re only in one building.

Wrap-up

[00:58:57] Lori Farrell: Sure. We have 47 seconds and counting, so I just want to say thank you to everybody for being here. Michael, I really appreciate you joining me, and I enjoyed our conversation. I’ll send you the chat if you weren’t keeping up. There are lots of fans of yours in the audience, and Emma is a big fan of yours, too. Thanks to everyone who stuck around, and I hope to see you at the next webinar.

[00:59:24] Michael Tullier: Thanks, Lori. I’m all over the internet, so if you want to reach out and connect, I invite you to do that.

[00:59:30] Lori Farrell: All right. Thanks, everyone.

Contact Us

Want to engage your
audience and grow your brand? 

See how Emma helps you create, optimize, and send email campaigns with confidence.