Team Registration and Communication

Connect products and forms to a roster, share registration links, message families, and create team automations.

Use Registration to connect the products and forms families use to join a team. Use the team message action and Automations for ongoing communication.

Open the team from People → Teams. Teams must be enabled for your organization.

Connect registration products and forms

1. Open the team’s Registration tab.
2. Select Connect products & forms.
3. Search and select the existing products or forms intended for this team.
4. Review the selection, then connect it.
5. Check the connected list and copy the appropriate link to share with families.

Select the product or form, then check the count on Connect before saving. Products and prices shown here are testing examples.

After connecting, use the copy control beside the intended registration link. The URL and product in this testing screenshot are examples; copy the link from your own team.

Each connected product or form keeps its own shareable link. There isn’t a single replacement registration link for every asset. Check the name and destination when copying a link.

A completed eligible purchase or completed team-connected form submission adds the selected athlete to the roster. Repeated registration for the same athlete does not create duplicate memberships.

The family must register the participating athlete. Where a parent has multiple children, confirm the intended child in the registration or checkout flow. A payer’s profile is not interchangeable with the athlete’s profile.

For product registration, configure the product to require the athlete when the purchase needs to belong to a child. Use the existing product builder and family account guidance.

Check that registration worked

After the family completes registration, check the athlete’s Roster entry, how they joined, and the relevant purchase or form response. A product purchase, a submitted form, a roster membership, and a successful session booking are separate results.

The On roster count belongs to a particular connection. The same athlete can be associated with more than one connection, so do not add those counts together to calculate unique roster size or money collected.

Adding an athlete manually does not create a purchase. Likewise, a registration connection does not replace checking roster-booking status.

Use dedicated registration paths

Choose a product or form that clearly represents the team families intend to join. Do not assume one form can route athletes among teams based on an answer. The current connected-registration workflow should be set up and checked for the intended team.

After connecting an existing product or form, review the roster. If athletes who registered earlier are missing, add them through the Roster tab.

Disconnect registration

Use the connection’s menu when you need to stop future additions through that product or form. Disconnecting preserves existing team memberships. Manage a roster removal separately if an athlete should leave the team.

Payment changes also need their own review. Do not assume a refund or subscription cancellation automatically removes an athlete from the roster.

Message the team

Use the message action in the team header. Review the audience before sending: team messages resolve eligible roster athletes and their linked guardians, with duplicate recipients removed. Check any reported unreachable families instead of assuming everyone received the message.

Use Inbox for the normal composition and sending experience. Delivery still depends on valid contact details, channel availability, and messaging preferences. SMS can use messaging credits.

Create a team automation

Open Automations in the team, then choose Create automation or Templates. Starting from the team keeps its context in the existing automation builder. The current team flow includes an Athlete joins team trigger.

Team automations show each rule's trigger and status. This testing example is Inactive; use the filters to find active, inactive, or archived rules.

Review the trigger, conditions, recipient target, actions, and status before saving or enabling the rule. A useful first rule is a welcome message when an athlete joins, addressed to the eligible contacts you select. Check whether another registration automation already sends the same message before enabling a second one.

Practice and game reminders are configured on their schedulers. Use the scheduler’s reminder settings for session timing and the team automation for the roster event. See Build your first automation and scheduler settings.

When starting from a template inside the team, check that Athlete joins team and the correct team remain selected before enabling it. After a qualifying registration, check the roster and Execution Logs; the log distinguishes completed actions from partial success.

If a family is missing

Confirm the completed registration, the selected athlete, and the product or form’s team connection. Then check the roster and family relationships. If the athlete is on the roster but not in a session, inspect roster-booking details rather than registering them again.