A subscription can change.
A feed can provide updated events when refreshed. Refresh timing and cancellation handling still need validation for each source.
KNOW WHAT CONNECTED MEANS
One destination.
Different ways in.
Connection methods depend on what each team or platform makes available. A calendar feed does not provide access to private team messages.
Today’s website is a demo.
The methods below describe the separate prototype and development direction. No live accounts are connected through this website.
| Source | Method / current position | What to expect |
|---|---|---|
| TeamSnap | Subscribed calendar feeds used in the private prototype | Schedule data available through the feed. No claim of direct account or message access. |
| Other sports platforms | Supported calendar feeds tested source by source | TeamSnap, LeagueApps and TeamReach feeds have been tested; other providers depend on their available feeds, exports or permissions. |
| Team websites | Selected schedules in the prototype | Website layouts and access differ. Automatic detection of every future change is not guaranteed. |
| Schedule photos | Photo review flow in the prototype | A snapshot to review and import. The original photo does not stay synchronized with a team’s future changes. |
| Email notices | Read-only Gmail monitoring in the private prototype | Relevant schedule changes and travel details can be surfaced for review. Full email bodies are not stored. |
| Voice entry | In the private prototype | Capture a spoken schedule for review. Browser support and transcription behavior can vary. |
An import is a snapshot.
A photo or one-time import needs another update when the original schedule changes.
Messages are separate.
Seeing the schedule doesn’t mean the assistant can read a team’s chats or announcements.
Platform names describe sources under evaluation or use; they do not imply a partnership or endorsement.
START WITH WHAT YOUR TEAMS USE