This recipe makes the From and From Name fields in a Group Scheduling System Communication dynamic. It uses this fallback order:

1. Group Schedule Coordinator
2. Person who scheduled the attendance
3. Organization defaults

Use Case

When volunteers receive scheduling confirmations, replies should feel personal and come from the right owner without requiring a separate communication per group.

Where to Configure

• System Communication: Scheduling Confirmation Email (One Button)
• Example: /Communications/System/146
• Fields: From Address and From Name

From Address Lava

{{ Attendance.Occurrence.Group.ScheduleCoordinatorPersonAliasId | PersonByAliasId | Property:'Email' | Default:Attendance.ScheduledByPersonAlias.Person.Email | Default:'info@yourdomain.com' }}

From Name Lava

{% assign c = Attendance.Occurrence.Group.ScheduleCoordinatorPersonAliasId | PersonByAliasId %}{% if c and c.Email != '' %}{{ c.FullName }}{% else %}{{ Attendance.ScheduledByPersonAlias.Person.FullName | Default:'YOURCHURCHNAME' }}{% endif %}

Important Notes

• Keep both expressions on a single line.
• Keep values short: these fields are limited to 200 characters in many installs.
• If save fails, remove extra whitespace and line breaks.
• If your communication context differs, verify that Attendance is available in Lava.

How It Works

• ScheduleCoordinatorPersonAliasId resolves the group's scheduling coordinator.
• PersonByAliasId loads that person object.
• Property:'Email' / Property:'FullName' extracts sender data.
• Default cascades to scheduler values and finally a safe org default.

Validation Checklist

1. Save System Communication successfully.
2. Send a live schedule confirmation test.
3. Confirm email headers show expected From Name and From Address.
4. Test both scenarios:
   • Group has Schedule Coordinator
   • Group does not have Schedule Coordinator (scheduler fallback)

This pattern gives admins dynamic ownership without duplicating templates for each ministry or campus.