You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

InLeague Team Conversations feature allows team parents and staff to stay in touch without trading email addresses or phone numbers. It's a quick and easy way for a parent to coordinate team snacks with other parents or for a coach to send his team an important game-day update. We designed Team Conversations to work closely with the inLeague Mobile app (Android/iOS) for a "group text" style experience, but users may also receive and send team messages from the inLeague web application.

 

Accessing Team Conversations

We currently offer Team Conversations to our leagues as a service upgrade. If your league has subscribed to the Team Conversations feature, all of your league's inLeague users may access Team Conversations. (TODO: screenshot mobile) (TODO: screenshot webpage) (TODO: what about menu link for website?) Conversations are sorted in order of most recently updated.

 

Starting a Conversation

Any parent or coach may start a conversation with other parents or staff on their team. After selecting one of their teams, they may choose any combination of recipients, from just one other person to the entire team, to receive the message. (TODO: screenshots)

 

Push and Email Notifications

When the user saves the conversation, inLeague will alert the recipients about the new message as soon as possible. Users who have installed the inLeague Mobile app (and used it to log-in at least once) will receive a push notification on their mobile device. (TODO: screenshot) In most cases, the push notifications are received almost immediately after the author saves the message, but rarely some alerts are delayed by a few minutes depending on network conditions within Google and Apple push notification networks. Message recipients can use their push notification alert to open the conversation in inLeague Mobile.

 

In addition to sending instant push notifications to mobile devices, inLeague will scan the database of team conversations every twenty minutes in order to notify users by email of any unseen messages in their conversations. The email will contain the text and details of every unseen message in the conversation and a link to their inLeague Team Conversations webpage. Our system waits for a ten-minute lull in the conversation before sending an email update.

 

Replying to Messages

Only those people who were originally included as recipients may reply to a conversation; new recipients cannot be added after the fact. When the conversation author saves a new message to the conversation, all the recipients will instantly be sent another push notification. On the other hand, only the conversation author will receive a push notification when one of the recipients replies to the conversation.

 

Private Reply

When more than two people are participating in the same conversation, every reply is visible to each person. However, a user may mark his or her reply message as a "private" reply. In this case, the system will start a new conversation between only that user and the person who originally started the conversation. Note that the new conversation will have lost the messages that preceded the private reply and that its two participants are still included in the earlier conversation.


Opting-Out of Push Notifications

Users may opt-out of receiving any push notifications from inLeague in the settings of inLeague Mobile. Un-installing the mobile app will also turn off inLeague push notifications. Because push notifications are automatically activated the first time the app opens, users who wish to opt-out should verify their inLeague Mobile settings after updating and reinstalling the app. (TODO: settings screen shot) (TODO: talk about email opt-out here, too?) 

 

Conversation Data Expiration

Please note that Team Conversations will not be saved in the inLeague system indefinitely. You will have access to your conversations for at least six months after a new message is saved. If you may need to refer back to a team message in the future, be sure to save the information somewhere else.

 

  • No labels