Podcast Episode 34: Rock Communication

Description

In this episode we talk briefly about the latest update then jump right in to discuss communicating using Rock.

Transcribed Content

This episode of Rockcast is brought to you by Rock partner Triumph Tech, a full service specialist partner. Rock partners provide crucial support for Spark Development Network and important services for the Rock community. Connect with Triumph Tech today at Rockrms.com/partners. Hello, and welcome back to the Rockcast podcast. This is our seventh episode, and this week marks one month since Rock beta was released. It's been a whirlwind of questions, answers, updates, and continuing feature development. So far, we've had about a 50 installs and more interactions in our q and a community than we could count right now. Today we're going to talk about one of my favorite topics, communication. But first, let's hear a little bit about our updates. I guess I get to take the floor first. Wow. Yeah. The last update, the four update had a a really a bunch of bug fixes that reported from the community. I I feel it was our biggest bug fix patch. In addition, there were some really cool features that we added in there. One of them was the logged in users so you can now see who's logged in to the site. And as we've talked offline, that doesn't include you. You're removed from that list. So don't panic when you see no one logged in to your site. The other feature though that I think we kinda almost stumbled on when we discovered, hey, what if we just made this one little change? How cool would that be? David, did you wanna touch on that? I I think you're referring to just the HTML content editor we can put on any page in Rock. We just added the person merge fields. So what that means is you can now customize content specific to who's logged in, which can get really powerful if you get creative. You could even put a page that wishes somebody a happy birthday if they happen to log in on their birthday. If they haven't signed up for a class, or they have signed up for a class, or they just finished a class, you can actually customize content based on what data about them. And so that whoever goes to that page, that would look different depending on who they are. So that can also see person attributes as Mhmm. So if they're not baptized, you could say, hey, Our next baptism is on whatever date. Yeah. Just all through the HTML editor. Pretty awesome. And I think when people talk about, well, why would I ever use a church management system or relationship management system for my CMS? I mean, until features that come to being, that's a valid question. But now that you have that power, why wouldn't you? , it has a lot of great CMS tools plus the ability to bring that data in as simple and easily as that. I mean, that's what really drives need for the CMS. Yeah. And again, I feel that was a sort of God gift to the team when we kind of realized, hey, why don't we just make that one little change and boom. And we've only scratched the surface of it. Yeah. That sounds a world of possibilities from the communications perspective. Absolutely. Yeah. My gear's turning. Yep. I'm sure our web guys are gonna be salivating when they get their hands on that. Other parts, what else was in the update? Another one was some group mapping stuff that we don't actually put a page during the install, but it's there. Right. So we'll be putting out a pretty quick blog post on that component. It's pretty slick on what you can do. Very powerful as you start creating your group functionality within Rock. And I think that's kind of a point too is there's so many things you can do with Rock through configuration. , we can't dream up exactly how this is going to work perfectly for your church because we don't honestly work or live in your church. But, , our job is to give you the the the Legos, the components, the blocks, and teach you how to use them and maximize them. And this is going to be one of those classic examples of that. We can't really configure it out of the box necessarily in a way that makes sense because we don't quite know how it's best to use in your church. But we'll show you how to use it. And we'll show you how we're using it. I mean, again, we're eating our own dog food on a lot of this stuff. So we're actually using it on the Spark site behind the scenes to kinda just get an idea where people are who are logging in and and and using Rock. So we kinda give you a glimpse of how we use it on the on the backside. And during the update you obviously know you get to see the release notes. But as , if you leave that page you don't see them anymore. So what we did was we've set up we'll have it set up by the time this is published a URL on the Rock website. So if you go to rockrms.com/roccreleasenotes, you'll be able to see the past release notes for every update. Yeah. And , one thing that was in the update that you can't see either is that the updater got updated so it looks a little fresher That's right. And nicer. They'll see it next time now. Right. It's one of those features , oh, this is really cool to look at. And so the update updates it, but you can't see it till next update. That's kind of a fun little feature. And then the Smarty Streets, there is a lot of changes to support that. Yes, there was. I think we talked about it a little bit last time too, is we just combined our geocoding and standardization services into one address verification. We have been really happy with Smarty Streets. Not only their data, but just them as a company too. They've been really willing to work with us and give some great deals to churches. Yeah. It's all free. And and they're some of the nicest people. I mean, it's it's kind of amazing how nice they are. And I was, , playing with some sample data the other day. I I wanted to kinda fake an address for something I was doing. So I went on to Google Maps, found an address that was valid. I looked at their street address on the house, and I said, well, I'm just gonna make it plus one because I don't really wanna it on exactly on someone's house. That's kinda awkward and weird. So I I kind of, , put added one to to the number. And Smarty Streets came back and said, that's not a valid address. No one and I was , oh, dang. They're so good that that I actually have to use someone's real house. So I was kind of surprised by that. And we had some very difficult addresses in our church of people who live literally in the middle of nowhere, on a dirt road in the middle of nowhere. We've had a lot of problems in the past of of getting those those geocoded. And obviously places Google do it well, but a lot of other big firms don't do it well. And Smart Shoots were able to actually get those for us. And because of some of the licensing with Google, we just, , we didn't feel we could use it. We engaged a lawyer. He's he felt that no, it would be outside of the license agreement for us to use it in in a in that way. And so that's why we we don't use Google. And then let's just touch briefly on the next update. There were a lot of changes kind of under the hood, which hopefully no one will notice. But it's going to be good, I think, to kick the tires kind of hard on the 'five update when it comes out. Yeah. Yeah. We are doing a pretty big refactor of kind of the underlying framework. We had put some stuff in there just to support the possibility of using all sorts of different databases. But when we really got down to it, I think we are just going to support SQL. When we come to that conclusion, we can pull out a lot of that abstract code and just make things more efficient and faster. So, that is the biggest thing. There are some areas of Rock that will just be more efficient, the data imports and stuff that. Right. Immediately we saw the sample data load time cut in half just from that change. Well, I love the fact too that when people start developing on Rock, I just the metaphor of the simple way. It is simpler. It's easier to understand. There's not as many things you kind of have to know about. I think it's just an easier methodology. It's more of a pattern, right? It's more So what you read in a book would be more Right. Right. I mean, you're if you're reading about Entity Framework, in the previous versions, would be kind of hard to see how we're using that. But now it's kind of right there front and center. That was a dev alert. Beep. Beep. Yeah. Right. So most of them don't have to worry about that. Sure. What about what about features in the in the next release? There's a couple of new features rolling out too. Right? We've got a new badge that we were kind of some of these features that we kind of see and it's kind of your time on Nick, know, there's a little hint of a feature and then I think that kind of brings to to bear what that feature really could be. And we've extended the page view feature. So now there's a badge that'll show you the last time someone logged in to the website. And then you can click on it and you can actually see each of their sessions, what pages they went to, how long they were on your website, which browser they were in, if it was a tablet or phone or a desktop. And so we really are trying to build this kind of picture of how someone is viewing all of your content. And even in the future, we hope that when you send out an email, that link can trigger, okay, from this email, they went to your Web site, they looked at these five things. So you can have this complete picture of the communications of a person. So it's kind of neat. So for now once you get the new update you can see each session which pages they went to. That's new. A lot of other new communication things though. Yeah, which we're going to talk about here in a minute, right? Yeah. Real quick, from a testing perspective, we now have the ability with the next update when you're loading sample data, if you wanna log in as the finance person or Ted Decker, you can log in as each of those people provided you set up a password for it. And you'll see that when you hit the sample data block. I think that that was a cool little addition to help you guys test and take a look at Rock in different ways. Yeah. And hope those people who are using Rock have two databases. I hope they have one that they're kind of playing with with their data, and I hope they have another one with the sample data. Because the sample data is very cool. I mean, you get to see, , kind of the best practices of how people could look. I think when you use your own data, sometimes it's very blank and you don't get a good picture of what it can do. But Nick's put in a ton of time into this sample data trying to get everything configured it should be in a church that's been using it for two years and a lot of best practices. So I use a sample aid all the time. I love it. I think it's really helped us in the development cycle. Yeah. And it's also helped us maybe scope out a future roadmap for an import. A very simple import tool that will be based somewhat loosely off of or tightly off of the XML specification that that sample data tool uses. So we've learned a lot and and it's helped us to go down a path that we didn't think we were going go down this soon. I think it's good. So anything else in the next five? I'm sure there's a lot of other things, but nothing huge that comes to mind. What do what do we think about Besides the communication stuff we're gonna talk about. Right. When when do we think about a release date on that? Probably maybe next week or week after? Yes. I think next I think we kinda have to do something next week. There's there's some stuff that would be really good to have kinda rolled out for next week. Yeah. So the good thing with the release is if it doesn't make this release, it just makes the next release. So, alright. So but the main topic of today is what communication, right? Yes. Let's get on with it. I'm really excited about this. So there's a lot of tools in Rock for communications. So David, do you want to start off with maybe what we do call communications? Sure. One thing with communications, what we have kind of done in Rock is really, a lot of other areas, is try to make it in a way that can be extended. So that if we didn't pick the particular tool that you want to use, you can extend it. And to do that, we've created this concept of communication channels and transports. So channel being kind of the email or SMS, how you want to communicate with somebody. Right now, and that's the two channels we have right now, but other things would be an application push notice, or even Facebook posts, or anything you can really think of. And then transport is kind of how that data gets sent out. So for the email channel we have transports SMTP, and we have added another one that we will talk about here in a minute. For SMS we have a Twilio. But it could be a different one, Strike Iron, or any other company that assists in sending SMS messages. But we have done that in a way that you can easily add those in. Right now what we call communication would be SMS, emails. Right. But if a third party wanted to add, you said, application push notification and we just didn't have time to get to it, they could really just drop that in and it kind of automatically work inside Yeah. Rock just looks for those kind of interfaces. And if somebody put one there, it just, exposes it as one that's available to be used. So that would mean an admin can go to a page, find a list of people, hit, I wanna send a message and choose let's say this push to their phone. Type a little message, hit send and boom it goes out to their phone theoretically. Right. And to them using Rock it looked exactly the same. They didn't really realize that some new functionality was added in. Right. They just keep using the same exact way. Yep. And so that's an exciting feature when we get the Rock store up. , people can add these channels without having to really necessarily go through the core team. They can whatever their their ideas come up, , write something, write some code, put it in the store, people download it. Yep. Wow. So in terms of communication, you you mentioned SMS. But there's also within email, there's a lot of features that you can do. So the transport that's SMTP SMTP is for those who aren't super technical. That's just the way the basic way things get mailed. , you talk to a server, say, here's a piece of mail, and it sends it for you. That works. That's that's very basic. That's very easy. SMTP has been around for Right. Decades. And everybody can use it, whether it's your server, know, in the building or even if you have a Gmail account. Gmail has an SMTP server you could configure Rock to use. Right. But if you want more advanced features, there is service providers who do more advanced things. So do you want to talk about Mandrill? Actually, will probably let you talk about Mandrill. Okay. Alright. So there are these email service providers. Some of the big ones are SendGrid, Mandrill, Mailjet, Mailgun. There's a whole bunch of them. But basically, they do is they say, okay. Well, SMTPs can be somewhat hard for deliverability. I mean, there's a whole bunch of advanced topics , SPF, domain keys that you just have to really know to deliverability high because all the ISPs are trying to find and filter out the spam. And how do you get your message not to be that? That's kind of the trick. And then they specialize in that. So they write these services where you basically send them your mail. They kind of do some best practices on it and send it out. But they also can add do some value added for your email. So they can tell you when the message was sent to the ISP. They can tell you when it was opened by the person. They put, , some images in there. When that image is viewed, then they know that image came off their service. They know it was viewed. They can tell you if one of the links within the email was clicked. They can tell you if it bounced. So there's different types of bounces. There's a hard bounce that says, hey, I don't know what that email address is. That's not a valid email address. That's a hard bounce so they can alert you of a hard bounce. They can also let you have soft bounces, which is a little bit more nebulous. Everybody's soft bounce is a little different. It could be as simple as they got out of office notice. It could be Mailbox is full. Mailbox is full. That's usually a soft bounce. Each vendor does a little bit differently with a hard and soft, but it can alert you those things. So with our mandrel implementation, we get alerted to those activities. So then we can flag those emails within Rock as being delivered, opened, link clicked, tell you what the link was that they clicked. We can tell you if it was hard bounce, soft bounce. We can disable those email addresses. Because one thing that really kills your deliverability is if you keep delivering to hard bounces, ISPs are , okay, you obviously have no idea what's going on. You must be a scammer. So and there's actually laws that say you have to do this stuff. Fortunately, they're not really super enforced. But it doesn't mean you shouldn't do it because the ISPs are watching and they're going to give you a bad reputation score you're doing these things. So Manjul kind of helps automate a lot of these things. And so we have that integration. It'll be rolling out in the next release. Manjul is also very nice in that it allows you to have do a lot of this stuff for free. So if you're a small church and you send less than 12,000 emails a month, you can use it for free. So that's a great feature. I think in the past, some of our documentation, we talked a lot about Mailjet, and that's still a great service. , actually, we're using that for Spark. But, , looking into some of these integrations and and getting deeper into the code and and and writing the interface, we just were blown away by by Mandrill. They also have another feature that's really what cemented the the the, deal for us was they can inline your your email. So HTML emails is can be very difficult. And we talk about this in our documentation that's coming out. So inlining that CSS and that HTML is actually a really magic feature. And right now, they're the only ones who who who we found that that do that, through the API. Now I have a question. If you if you use Mandrill in all these features you just described with being able to see in Rock the the status of each recipient, does that also apply then with other providers or other transports? Yeah. We've added to Rock is the ability to store all that data and to view it. So it's up to if there's another provider being written for SendGrid or Mailjet, that would we just have a place where that data can be stored. So that provider has to get that data from So if the provider has the functionality, Rock can handle it and do stuff with it. Yeah. Someone has to write that glue code, that code that kind of glues it all together. But it's not that. It's not that. And we've done it for mandrel. And out of the box, we'll have a mandrel provider. Right. Right. But it's pretty trivial if you if c sharp and you have some experience in some stuff that. It's pretty trivial to write another one. I I mean, I think you could do it in a couple of days Cool. If you needed to. All this is documented in in the in the communication guide, is coming out probably next week or week after. Think we're about 90% there. Yep. So it's just in Emily for proofing and voicing and I just finished proofing it last night. Quality control and Now it's a matter of getting it uploaded. To me commas are kind of optional things you kind of add occasionally. I don't know if you notice that. Yes. Yeah. Or or you put them everywhere if you subscribe to my philosophy. Yeah. Or when in doubt, semicolon. Right? If you have two senses and you're thinking maybe they're one, you put a semicolon. Okay. We should stick to coding and not grammar. That's alright. Great. I don't know. Use be some honest. Right? So when you get to the documentation, just ignore the comma placement. It's optional. But Well, by then, it's been fixed by you, though. Right? Hope so. Yes. Alright. Yeah. That's why. I was hoping. I even put notes in there. I I don't know if that's right, but you can fix it. But it the the level of documentation is it's really easy. It's gonna walk you through even how to set up Mandrill step by step even in their on their web pages. Put a lot of time in just making that, , dead simple. So you don't have to know about half the stuff we even talked about. Just go to the site, follow I think it's only, , eight or nine steps and boom. You're ready to send mail. And it looks professional and it does what you need it to behind the scenes to get the message across and make sure it reaches its target every time. Yep. Okay. And I'm impressed with Mandrill too. some of these things, setting up your DNS to get SPF and domain key, they can be a little bit hard. But when you don't get it right, , didn't get it right a couple times when I was setting it up. And they'd actually tell you, , hey, you didn't quite do that right. This needs to change. And so most places, they would just say failed. And you're , you're left kind of going, okay, what did I do wrong? You have to go back and try to figure out. They actually put a lot of time in trying to figure out maybe what you did wrong and trying to tell you what exactly you did wrong and how it should be different. So I was actually pretty impressed, with how they had that set up. Kind of inspiring for us. So when we're integrating with a service Mandrill, it doesn't necessarily mean that we have some other relationship with them. We've just looked around for what seems to work best with Rock and what has the right features and we're making that recommendation to make it easy for the people who want to use Rock. Right? Right. And I'm glad you brought that up because we don't do that. we go find the best vendors. We integrate. We show you how to use them. We never go to that vendor and say, hey, can we get a cut of this? Or hey, we can bring you a lot of customers. We don't do that at all. Clarifying that. Yeah, we're not here to try to skim off the top. , we want to find the best. We're passing along some best practices and helping make that easy for the person who's using it. Yeah. Okay. Just for record, did have one vendor who sent us a gift card because one of you guys signed up. We had no idea. And I did tell John he should report that. And and he's reporting it publicly now. And it was Smarty Street. And I think that person signed up for a free account. So I'm , what? I almost felt I should send it back. , it was just too nice of them. But we'll buy a book, a technical book to make Rock better. So it was only $25. So a couple other things about email communications too that you'll see in Rock is that we have the ability now to unsubscribe. I am not sure if that made it in the previous release or not, but whether it did or not, it has gone through some improvements since then too. So every email that goes out will have, if it is flagged as a bulk email, which is what gets done by default, it will give the recipient an option to unsubscribe. When they do that, it takes them to a page on the public site that they can specify their email preference. And they can say, I don't want to get any emails. I don't want to get bulk emails. I don't go to your church anymore. Stop bugging me. Take me off your list. So, I mean, that's one of the new features. Then And all that is customizable. So, if you don't the message, can Right. The options. I mean, it's just you can add other options there too. One other thing too is that we mentioned HTML emails. A lot of people, I wouldn't say a lot, but some people are using email clients that don't support HTML. So we also haven't if you don't put any specific content for that, when they open their email, they'll just have a link back to where they can view an HTML version on your website. So those are some new things that we have. And that's really important. , you really have to have that if you're sending bulk mail. And to date, we don't have that. And I've always thought it'd be nice to have that. And it's it's great have it now. We meaning your church. Right. Okay. Right. Yeah. Not rocket. Yeah. We've been sending out bulk emails for a long time without that. I'm not sure if nonprofits get a pass on that, but we shouldn't. We knew we should be playing by the best practices. So I love that feature. Yeah. And what's nice too is when you're going to create a communication, you can see right away if there's people on your list of recipients that wouldn't get the email if you sent it. It's a great feature too. So then once someone has selected their, update to the unsubscribe feature, are you getting a report back about that or is it automatically making that switch to the individual person's profile? That's interesting. It is it does both. So it automatically sets their preference up. So whether you've looked at it or not since then, somebody sends another bulk email, they won't get it. But we also flag them. There's kind of a new flag on a person record in Rock that says, hey. This person needs to be reviewed, and this is why. So if somebody on that page says, I don't go to your church anymore. Here's why. They get flagged as that as needing review, and we can create reports off that and even different reports based on the reason they gave. So, , you can have some people look at specific reasons and other people look at other reasons. Could that, in the future, kick off a workflow that, , maybe the workflow says, hey, find the most appropriate person to handle this person, maybe by their address or something that. Is that a possibility? Sure. Oh, for sure. Yeah. Whether it's a workflow or reports. It's just that we're we're flagging that when they do that. Cool. Yeah. Because a lot of times these people, David said, are giving you a reason why they don't attend your church Right. Not to read that and take action. I mean, at least even just read it would be a crime. Know? Foolish. Yeah. There's there's more to communications than just the communications. There's there's also marketing ads. So marketing ads is a way of looking at other so I guess communications is kind of pushed out to you. Marketing ads in some ways is more of a pull. So it helps you organize things your bulletin and also your website. Really, really powerful on the website. It gives you the way. Say you're promoting a car show. We have a car show at CCV we do every year. You need to promote that car show. You can go in there and create a marketing campaign for the car show. You can set up your bulletin when you want it in the bulletin, which weeks you want the bulletin, the content for each of those. You can set up the ads that you would want to put onto your website, maybe on your rotator, on the homepage or on certain sub pages, you can set that all up and you can get approved, prioritized and then implemented. So out of the box when you run it, there's actually a few sample ads already in there. And if you go to the default external site, which is page one, you'll see those ads in the rotator. And then right below it, there's more ads. So marketing campaigns is what drives that. That too is extensible. So you can add different types of mediums. , you're not limited to just bulletins and and and website. You can add those actually without code. You might still need code to to eventually do what you want to do, but you could add new new types if you want. So eventually, those could you could add a Facebook campaign, a Twitter campaign. The code for that's not written, but it could be written in. And we have plans to do that eventually. Someone might beat us to it, which would be kinda nice. Yeah. Hint, hint. Yeah. We don't have to write everything. And where is all this documented? Is that going to be in the communications or in the web CMS guide? A little bit in both. Okay. , how to input it and and administrate it and kind of use it is in the communication guide. How to implement it onto your website is going be in the Designing Building Websites with Rock guide. So it's a little bit split to both. I think if if you're a church that doesn't have a web designer, you could just use the, , the the external site we give you. Hopefully, there'll be some themes coming soon that you can kinda pick from. The one that you you get right now is intentionally left blank. In fact, it's called Stark, not because we Iron Man, but because it's Stark themed. But we do Iron Man. How are gonna okay. So it's a very blank theme. And it's it's intentionally so it's meant to be a starting point. When you wanna create your own theme, first step one, copy and paste theme. It's a starting point. So we didn't put it in there to make it look good. We put it in there to make it a good starting point. We had mentioned earlier about kind of reasons why to use Rock your CMS. For me this is the biggest reason. Your promotions or your ads driving your website just take so much away from having to manage that website. It is all dynamic. You approve ads, they show up on your website. If you are using something else to drive the website, kind of lose that ability to just have such dynamic content based off what your staff is wanting get up there. Right. And then as we get event registrations done, that will all be a part of the ads so that from the ad you can register for the event. Even to the point, going back to what you said in the beginning, you could on your ad detail page, add a little HTML block at the top. And if they're logged in, you could say, David, looking forward to seeing you at the car show. Wow. That's pretty wild. Yeah. Right. And the approvals that you touched on briefly, that's a lot of help when you get into an organization of any size so the people who have the details about the event can enter, the actual promotion they wanna have up there, but it doesn't go live till it's had some review. Right. Because if we have 15 events that, each ministry leader wants to be, put out there and promoted and we have four spots to put them in, that's gonna be a concern if they're automatically approved. Yeah. Get to approve and you get to edit and copy edit them so you can fix the commas for them too. And there's approvals even on the emails and on the communication. So if it's over a certain threshold, you can have it go to someone to be approved first. I know we often use that in in our church today. So if it goes to a wider audience, it needs to be approved by communications. A configurable threshold. Right? Right. And you can disable that, of course, too if you if you don't want that. There's ways to make all staff be able to send as many as they want. A lot of warning bells going off to me when I hear that. We wouldn't configure that. Out the box, it doesn't configure that way. It's I think I think the limit's 300 out of the box, but easy to easy to change. So anything else with communications? If not, we can cover it next time. It's kind of one of those great topics too that, , since where we work, the IT and communications are in one team. We're very passionate about both. So it's not really an afterthought for us because we're actually writing part of our job, ? So we're trying to make that powerful user friendly, to do the things that we need to get done on a daily basis. We can see regularly what problems need to be solved in that area and put some attention to that. This is a really great tool too. You can keep your eye on what's going on, it helps you to see who's involved in the church. It's another great way of really personalizing the experience to people. It's not just a well, we got to have to be able to send email. It's not a check off our list. This is something we're really passionate about for any good communication tools. And at the end of the day, that's what people want now. They want for you to talk directly to them no matter what size the organization is. So if we have those tools in hand, then that makes our job a lot easier. Right. And the professionalism on that has to be very high. They're used to getting professional , HTML emails or websites that are professionally assembled. So we need to make that easy. And that they can view on whatever device they have at that time. Yeah, I mean that's actually something come out in the next update too is, there's a lot of responsive, tweaks to make, the internal portal work really well all the way down to a a cell phone. I mean, it's it's kind of good right now. It's a lot better in in the next update. We have panels that slide in and out better so the menu is easier. The person detail page is almost looks it was made for an iPhone. So, today at CCV we actually wrote a separate iPhone website. The default user interface is going to replace that site. That really wasn't intended. We always intended to say, well, we're not sure we can get Rock to really by default scale all the down to cell phone size. We'll have to create another site, but I think we've been able to really raise the bar and get there. There are certain things that are always gonna be troubling. I mean, when you're looking at a a grid full of financial transactions that's, , a thousand pixels wide, getting that to respond down to an iPhone is gonna be difficult. But but you probably aren't gonna be doing that on your phone. I would hope. And it's gonna be a challenge regardless of whether it's a native app on your phone or a responsive website. Right. It's just cool to see how far the web has come to, making that that a reality. In other words, write it once and let it run everywhere on all devices. Yep. Definitely. So a lot of good stuff coming in the next update. Definitely really read those release notes. They might seem a little lengthy, that's only the good stuff you're seeing. There's a ton of other notes that you're not seeing. I think that's gonna wrap up our podcast for today. If we've missed anything, you'll hear about it next time. And thanks so much to all of you participating in our ROQ and A and our development communities. We really appreciate your interactions there and thanks for listening today. Do a church that loves the idea of using Rock but hasn't taken that leap yet? With managed hosting, churches of any size can get access to Rock's amazing technology, hassle free. With just one click, Rock's managed hosting removes the roadblocks that might stop a church from switching to Rock by making the process simple. Churches get the ease of a SaaS church management system without losing any of Rock's powerful features. Are you ready to take the next step or share with another local church? Visit rockrms.com/hosting today.