Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Please refer to the Campus Facing Communication Service Catalog Entry for customer-facing information regarding this service offering. DAC professional and student staff should respond to Campus Facing Communication PSU Help Center Requests for Currently, Emma, and Tech Talk blog contentas follows:

Requests for Currently Content

Currently is the weekly faculty and staff e-newsletter published online every Monday during the academic year. News items should be sent to currently@pdx.edu.

Step

Details

Process Incoming Ticket

  • Add a “Communications” label to ensure it appears in the “Content and Communications” filter.

  • Delegate and assign to professional or student staff.

  • Change ticket status to “In Progress.”

  • Reach out to the customer to assess needs.

Manage Backend Content

  • Ensure that you have access to the Google Document version of the Currently submission the customer is wanting to send. 

Consult as Needed

  • The requester may require support in planning and crafting their content from an accessibility, usability, technical writing, or content management perspective.

    • Review the article with them to ensure adherence to the OIT Style Guide and accessibility guidelines.

  • Run usability testing on all steps outlined in the email in order to ensure that the article is as accessible and user-friendly as possible to all users.

  • Ensure that the user is aware of the 70 character limit.

  • Notify the customer that the Marketing team may reword the content provided to them and that they have final say on how the Currently is presented.

  • Provide the dates for submission to the user so that they are aware of publication deadlines.

Revise and Draft and send Currently submission

  • Review with the requester for any additions or revisions they would like made to the Currently submission before sending it.

Resolve Ticket

  • Respond to the requester thanking them for reaching out to us and notifying them that the Currently submission has been sent out.

Requests for Emma Content

Emma is a digital marketing platform used as a mass mailing tool that allows users to send email campaigns. Emma emails are submitted through the help-content@pdx.edu email. For more information on the process of sending Emma emails review the How to Send a Mailing with Emma article.

...

Step

Details

Process Incoming Ticket

  • Add a “Communications” label to ensure it appears in the “Content and Communications” filter.

  • Delegate and assign to professional or student staff.

  • Change ticket status to “In Progress.”

  • Reach out to the customer to assess needs.

Manage Backend Content

  • Ensure that you have access to the Google Document version of the email. 

Consult as Needed

  • The requester may require support in planning and crafting their content from an accessibility, usability, technical writing, or content management perspective.

    • Review the article with them to ensure adherence to the OIT Style Guide and accessibility guidelines.

  • Run usability testing on all steps outlined in the email in order to ensure that the email is as accessible and user-friendly as possible to all users.

Revise and Draft and send Emma email

  • Create a Emma version of the email.

  • Create the group that the Emma email will be sent to. Be sure to add yourself and the requestor to the list of recipients for the email.

  • Review with the requester for any additions or revisions they would like made to the email before sending it.

Resolve Ticket

  • Respond to the requester thanking them for reaching out to us and notifying them that the Emma email has been sent out.


Requests for Tech Talk Blog Content

The OIT Tech Talk blog can be found on the OIT website and features articles put out primarily by the CIO and DAC team. Tech Talk blogs can be requested through the help-content@pdx.edu email and are primarily handled by the Content and Communications Specialist.

Step

Details

Process Incoming Ticket

  • Add a “Content” and “web” label to ensure it appears in the “Content and Communications” filter.

  • Delegate and assign to professional or student staff.

  • Change ticket status to “In Progress.”

  • Reach out to the customer to assess needs.

Manage Backend Content

  • Ensure that collaborators have access to the Google Document version of the blog. 

Consult as Needed

  • The requester may require support in planning and crafting their content from an accessibility, usability, technical writing, or content management perspective.

    • Review the article with them to ensure adherence to the OIT Style Guide and accessibility guidelines.

  • Run usability testing on all steps outlined in the email in order to ensure that the article is as accessible and user-friendly as possible to all users.

Revise and Draft and send Emma email

  • Create and publish a Drupal version of the article in the Tech Talk section of the website.

  • Review with the requester for any additions or revisions they would like made to the article.

Resolve Ticket

  • Respond to the requester thanking them for reaching out to us and requesting that they take a final look at the published article before we resolve the ticket.

  • Once the requester has approved the article, resolve the ticket with a message containing methods for requesting updates in the future.