I'd love to be an Alpha tester for the check in app! I run iOS.
Great! I'll pass your info along to our Check-In team
People search / online directory through the Congregant app would be a top priority for us. We'd love to stop printing directories in favor of an app. Could just be basic information for general congregants, such as name, phone number, email, and address.
Thanks for that suggestion, Greg! I'll pass it along to our team. Some follow-up questions: have you given thought to *who* you'd want to see in this directory (e.g., only people of a certain membership type, in a certain group, etc...)
I'm not sure if this was covered, but in Schedules, I want to know if a volunteer Accepts a serving position, are they able to go back in to Decline if something comes up and they can't serve? Or if they initially Decline, can they go back in to Accept? And if so, will we get a notification if they change their status?
Volunteers *can* go back and change their status. They would do that by following the link from their original Volunteer Request email, going to their Schedule, and choosing to Decline, 'Find a Replacement' (if that setting is enabled for the Schedule Category), or 'Message Scheduler'. A new Decline notification will go to the Schedule Organizer.
Once someone has declined a serving request, there is no way for them to go back in and Accept it. They'd have to message the schedule organizer, who could manually change their status for them.
We only require a background every two years, is there an ability to add a two year background check to a person's profile?
For the purpose of Beta Schedules, the 'Require Background Check' connects to a person's Childwork Approved status in their profile. You can set a Start and End Date for that status, so you can set the End Date to be 2 years out, and when the 2 years expires, you will get a notification in Schedules that the volunteer's background check is expired.
I'm interested in being an an alpha tester for check-in, running Android
We'd love to have you! You can email me at firstname.lastname@example.org with your name, church name, and email address so we can get you on the list.
I'm interested in Alpha Testing Check-in
Great! Our Check-In team will be in touch. Do you have an iOS or Android device?
I would hope that the Congregant App would prioritize a giving component?
Great suggestion, Sheila. That is definitely going to be a component that we build. We've talked about easy ways to create a one-time or recurring gift, and allowing people to see and manage their own giving patterns as well.
So Sad to see Erin go!
Thanks, Samuel. I'll certainly miss your enthusiasm in all of our announcements and events!
There is an aspect of duplicate detector that is troublesome. I shows familiy members living at the same home as possible duplicates. I think the code needs and "if then statement". If John and Jane Smith (plus their 4 children) have the same mailing address, the system should not suggest them as duplicates. Or is there a way to identify them as a family? I spent quite a bit of time marking all the members of pur large families as ignored duplication.
I enjoyed using this feature, it did find some actual duplications, and a few which may be women who used to attend, left, married, and returned. It's been a fun way to reduce the size of our database. I was able to find quite a few possible duplications with no activitiy in their account for 3 years, and have inactivated those pairs. (Their data is so old it doesn't matter if they are duplications. However, if they ever return to our church, we can clarify thelinformation then.)
We built the Duplicate Detector to *not* show someone as a duplicate if they are in the same family (i.e., they share the same family ID). We have discovered that for a lot of our churches, they have full families that are duplicated (i.e., the same family member names listed in two different family IDs).
If you are finding that *isn't* the case for what you're seeing (so, you really are seeing duplicates within the same family ID), let us know so we can submit a ticket for you.
Erin, we have a lot of cases where an adult child is living with their parents, and we've put them in separate families. If the child is working full time/out of college/over 26, we move them into a separate family and treat them as an adult, even though they may have the same address as their parents. Because of this, the duplicate detector is identifying between 558 - 842 potential duplicates. I'm sure some of these are legitimate dupes, but many of these have been intentionally set up as separate families that are now being seen as possible duplicates.
Thanks for describing that scenario, Matt. I'll pass that use case along to our Product Team.
Whats the blog that Erin has? Migration Blogpost link? Thanks!
There are a few blog posts we referenced during the webinar (and some we didn't reference, but should have):
- Duplicate Detector and other Profile improvements: https://www.churchcommunitybuilder.com/software-news/duplicate-detector
- Schedules Roadmap: https://www.churchcommunitybuilder.com/software-news/schedules-roadmap
- Migrating from Old Schedules to New: https://www.churchcommunitybuilder.com/software-news/schedules-migration
- Schedule a Call with Support: https://www.churchcommunitybuilder.com/software-news/support-options
Giving is an essential feature to encourage our members/attendees to download and use a "congregant" app. Many have expressed their disdain with the giving browser experience on a phone! Please make giving a priority in the initial release of the new upcoming congregant app.
Thanks, Alan! We are definitely planning on building giving into the app, with easy ways to give, manage your gifts, and run giving statements. Are there any other essential giving features you would expect your congregants to have in an app like this?
How can I sign up to be a part of the alpha check-in?
You can reach out to Jamie on our Check-In team (email@example.com) and he can get you set up.
Is there something similar to the needs feature in schedules reimagined? I'm having a hard time finding how to accomplish fillin in needs in this system.
If you're describing Needs in the sense of allowing your volunteers to sign up for open serving opportunities, we've built in a "Allow Volunteer Signups" feature that will let your volunteers pick their own slots.
If you're speaking more about using Needs for signing up for other purposes, you will still need to do that through Groups in the software.
"Authorized People" great addition! Have been listing them in the "Family Message"
We started accepting a LTSP (Lost Tag Security Pin)as an identifier for when a family has lost their pick up tag, and does not have a photo ID available. A LTSP / or user defined field added to the Edit Family info would be SUPER!
Thanks for the suggestion, Roger. I'll pass it along to our team.
Under Positions in Groups, you cannot have an LAU member fill a position. Is this true for team members and positions in the Beta schedules?
Hi Cathy. That is still true in Beta Schedules.
Regarding Congregant App, the things most important for us would be to allow people to check-in on the app, and to view their schedules easily.
Mandy, those capabilities will be in the app. Congregants will be able to check in for events and check in for volunteer assignments, and they'll be able to manage everything they need to do with schedules/volunteering. Thanks for sharing your thoughts!