SB+ Messaging "Parents" available does not match "Parents" in Roster Builder Report

Some more feedback about SB+ Messanger- The list of parents available that I can message is a subset of the list of parents that show up in the roster report. Why is this the case/how can it be fixed?

image

For context - since SB Classic messenger was clunky & frustrating to use, I have a custom report to generate a list of all the the active scout’s parent emails and send that out via my personal email. I would love to get out of this practice and just use SB+!

Roster builder is probably not setup for relationships yet is the issue

Roster builder has “desired” output though. I.e. more accurate, both parent emails, etc.

@MichaelCasella

Scoutbook Plus will only allow e-mails to parents listed with relationships. The Roster Builder report is probably still showing parents connected in Legacy Scoutbook but do not yet have Relationships.

All parents need to be listed with relationships by the end of the year.

What is the plan to

  1. Port existing parent connections over to “Relationships”.

  2. Make it so that a parent tied to their scout’s account can add the second parent on their own? Self service for the families that want both parents to have email access. Take the load off of your pack administrators!

NOTE: If it was easy, it wouldn’t be a huge problem. Needing to look up existing accounts by Member ID + Last name + DOB is tedious. I don’t have every parent’s DOB, so I can’t add them easily.

#2 is already in place for existing parent in relationship can add others in SB+

2 Likes

The problem with #1 is that there’s no way to automatically validate those connections. That is, if a parent is already in the Akela database (i.e. can be validated), they don’t need to be ported since that’s the source of the Relationship in SB+. However, if a parent connection in classic Scoutbook isn’t already in the database, they need to be validated somehow. However, there’s no way for Scouting America to do that automatically, since the Akela database doesn’t contain a relationship for the person who needs to be validated (or else they wouldn’t need validation). Thus the manual intervention process that exists for adding the new connections.

1 Like

Here’s what I’m doing with my units:

  1. Run custom roster report including all scouts and selecting PG relationships.
  2. Look at parents listed in legacy scoutbook and compare against the roster report.
  3. Any in legacy messaging but not the roster report will get an email with instructions to have the other parent add them or they’ll stop receiving messages. They will also be notified that they will receive an email link to approve once the other parent adds them.
  4. Circle back after a week and repeat 1 and 2. Hopefully, it’s a shorter list with the issue. This time, I’ll reach out to the existing parent with the relationship.

Note, key 3 (delegates) could also initiate the new relationships if you prefer. But I’d rather leave it to the parents and hope it reduces the number. There may also be some parents who don’t want the messages and are happy to let the other parent cover it.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.