ConcertAmiDocumentation
Collaboration

Messages to the organization and lineup

Choose recipients, write an announcement and review history.

Messages do not replace the program

Messages support organizational communication: a rehearsal venue change, a preparation request or a short announcement for the lineup. Also put lasting decisions about the event sequence in the appropriate program, so they need not be reconstructed from conversation history.

Authorized people can send messages. Recipients see messages addressed to them. Organization access alone does not grant the right to read every message sent to others. Check the current organization before sending.

Write and send

The subject may be generated automatically using the organization name. A missing subject field is not a form defect. Searching for recipients should not accidentally send a message when you press Enter.

  1. Open Messages from the available menu or the message action in an event.
  2. Search for recipients and use section or role filters.
  3. Select the people who should actually receive the announcement.
  4. Write concise content and check the dates, times and venue.
  5. Review recipients after the last filter change and confirm sending.

Selection and visible people

Filters help select a particular part of the lineup but change the visible set. In the current selector, the message goes to people who are both selected and visible after filtering. Check the final list again after changing filters.

Read Select all in the context of visible people. To contact the entire organization, remove restrictive filters and review the result. Do not rely only on your memory of an earlier selection.

History and notifications

Saving a message and queueing delivery are separate stages. Channels respect organization settings and participant preferences. Push requires an active device session and system permission. History allows later reading of content when the recipient has access.

If someone cannot see an announcement, first check whether they were an actual recipient, then check their account and organization. Only then investigate email or push. Do not send the same message repeatedly without checking the first attempt's result.

A clear announcement

Start with the specific change, then give the date and time. If you need a participation response, identify the event and ask for a status update. A reply in a conversation outside the app does not necessarily update the lineup.

Do not send passwords, sign-in codes or private recovery links in messages. Store materials as the appropriate resources with access control. The intended result is one clear announcement sent to a verified recipient group.

Search guide contents · Enter opens the selected result