Guidelines
Best Practices
Requests

Communication Guidelines

TXST Mobile app notifications are intended for university audiences (e.g. - students, faculty, and staff). Only TXST entities may request an account to send or ask for Push Notifications, In-App Banner Messages, Location-based Notifications, or Personalized Notifications sent through the TXST Mobile app.

The TXST Mobile app team will evaluate each notification request and notify the requestor if approved. The TXST Mobile app team will also inform requestors if adjustments need to be made to allow timely University-wide messages to be scheduled ahead of other communications in the app.

Notifications must be received a minimum of four business days in advance to allow for the review and ahead of other communications in the app. 

Please read and understand the communication guidelines below before you fill out the appropriate request forms for Push Notifications, Location-based Notifications, Personalized Notifications or In-App Banner Messages for the TXST Mobile app.

Expand FAQ List

  • Notifications should be relevant to the person receiving them. We do not allow notifications to be sent to audiences they are not intended for. The more personal and unique a notification is to the recipient, the more likely they are to take action.

    Per App Store Policy Section 4.5.4 - (Push Notifications):   
    "Push Notifications must not be used for promotions or direct marketing purposes unless customers have explicitly opted in to receive them. Apps that send inappropriate content via push notifications may be removed from the App Store."

    Messages from the TXST Mobile app cannot include the following:

    • Sharing personally identifiable information.
    • Solicitation of services or products outside of TXST.
    • Explicit or offensive content.
    • Request for donations. 
    • Student organization advertisement (even if the event is sponsored by an official group); Student Government is the exception to this restriction.
    • Links to non-approved TXST software/systems or sites that redirect to a non-TXST domain without special approval.
    • Research recruitments and surveys (Exception: The TXST Mobile app team can survey app users about mobile feature enhancements and general app improvements).

    Public push notification and location-based notification accounts can be suspended or removed by not following message content guidelines.

    Custom uploaded images are not supported at this time for notification requests.

  • As a university, we must be mindful of the number of messages sent to users. A higher volume of push notification messages may result in TXST Mobile app users disabling the push notification feature.  

    The TXST Mobile app team keeps a comprehensive notification schedule to ensure users are not inundated with too many messages. While we cannot guarantee a message can be sent on a specific date, there are some steps you can take to ensure your message is delivered when you want or need it to be sent:

    • Submit your notification request as far in advance of your preferred date as possible. Notifications must be received a minimum of 4 business days in advance.
    • Adhere to the character limits in the form to reduce the number of modifications needed.
    • Respond quickly to the mobile team's feedback if changes are made and communicated to you.

    Typical Frequency

    • Location-based Notifications: Location-based notifications should typically notify users no more than two times a week.
    • Public Push Notifications, In-App Banner Messages: Public push notifications and in-app banner messages should typically notify users no more than one time per week.
    • Personalized Notifications: Personalized notifications should typically notify users no more than one time per week, with at least one message every four weeks. 

  • The TXST Mobile app team reserves the right to update or make exceptions to these guidelines. All users of the TXST Mobile app communication platform will be updated when changes occur. 

Best Practices

The best notifications are timely, relevant, to the point, helpful, and nonintrusive. Here’s what that means in practical terms as you build creative messages. Ask yourself these questions each time you’re about to request a notification.

Is this the best time to send a notification?

Timing is crucial. If your recipient is busy, or asleep, the chances of getting their attention are slim. Historical data indicates students are more likely to take action on notifications sent later in the morning or early afternoon, while faculty and staff are more likely to take action on earlier morning messages.

Is the notification short and sweet?

Shorter notifications usually perform better. Spend the extra time tightening up your messaging.

Are the recipients receiving too many other notifications?

One major danger with notifications is overload. Too many messages, too often, can lead to dissatisfaction with, or dismissal of, your messages. We leverage message limits and frequency caps on requestors to ensure we don’t overwhelm users as a whole. We also provide users with opt-out options for general audience messages and look at engagement stats to determine whether users are turning notifications off. 

Get your requests in as early as possible. If notification slots fill for a particular day or week, we will not be able to send your message. The beginning, middle, and end of a semester are the highest request periods.

Is the notification personalized for its recipients?

Messages need to be personal and relevant for a user to find them valuable. It’s crucial for you to review your messages to make sure they align with your intended audience’s preferences and interests.

Is the value of your notification clear?

This is the big one. It’s best to avoid sending notifications for the sake of “getting the word out” or “increasing awareness.” As a university, we need to make the most out of mobile notifications by using them for urgent, time-sensitive, or “action-needed” messages. If the value is not immediately apparent, recipients are less likely to engage. Before finalizing each message ask yourself honestly: “is it clear how this could help my user?”

Does the notification have a strong human connection?

Notifications should be written the way you would talk to a person in real life. You have a better chance of connecting with your recipients and increasing engagement if you use words that relate to the way your intended audience speaks or thinks.

Does the notification call for action?

Your notification subject should ask the recipient to do something. Try writing your headline as a complete sentence to deliver a more valuable impression, and pare it down to meet the character limits.

Does the notification have enough context?

Using context words helps create emotional engagement. These words can help increase a person's interest and attention. Context Words into four categories: insight words, time words, space words, and motion words.

  • Insight words provide more detail (e.g. - closure, admit, inform, think).
  • Time words refer to a point in time (e.g. - after, fast, long, prior). 
  • Motion and space words help recipients understand where something is happening (e.g. - appear, replace, arrive, enter).

The purpose of your notification is not to provide all the details of your event or service, it is to pique the interest of your recipients. Use the button options to provide more material, share location (map) details, or registration information. A date, time, and location name are important, but a full guest speaker breakdown or list of supporting offices is not.

Communication Requests

Single Request Forms

Messages must support the academic or administrative functions of the University, and messages must be applicable to most University constituencies, including departments, divisions, or offices critical to the TXST community.

Expand FAQ List

  • Public notifications and messages must support the academic or administrative functions of the University and must be applicable to most University constituencies, including departments, divisions, or offices critical to the TXST community.

    Please contact us for more questions.

  • All requests must be made at least 4 business days before the notification is scheduled to go live. The TXST Mobile App team will review announcement submission requests. Posting is not guaranteed. A TXST Mobile App team member may be in contact to ensure the information’s accuracy and review messaging guidelines before final approval is granted.

    Location-based notifications are only available for:

    • San Marcos Campus OR
    • Round Rock Campus