Submitting and checking the status of Registrar incidents (for customers)

Submitting an incident/request

There are two ways to submit an incident/request.

1. Complete the Registrar Support form.

2. Send or forward an email to help@tulane.edu and add “#registrar” anywhere in the subject line.

Managing or checking the status of an incident/request

Current students and employees

You can view your open incidents in the IT portal. (Note: the tool we use is provided by IT, so all open Registrar incidents you created will display here in the IT portal.)

Your open incidents appear in the My Incidents section. Any resolved incidents will not appear here. Only incidents you opened will appear here.

Instead of submitting a new incident to check the status of an incident you previously opened, you should review your open incidents in the IT portal. Duplicate incidents can result in incorrect or incomplete processing of your incident.

Open

Alumni and third parties

When you submit an incident/request, you will receive an email notification that an incident was created. Reply to that email to inquire about the status of your incident.

Any comments or questions from the agent will be sent to you via email and you can reply to those emails with a response.

Adding additional information to an open incident/request

You can add additional comments, view other available comments, and add/view attachments.

To add additional comments, type them in the box with “Type your message here…” and click send. When you add comments, the agent working the incident/request (indicated in the top right box) will receive a notification.

To add an attachment you can either click the paper clip icon in the title line or you can drag and drop files into the Attachments box in the lower left. Click on any attachments in the activity stream to view.

1. Add an attachment

   1. This incident’s attachments (you can also drag files into this box to add attachments)

2. Enter additional comments

3. Identify the agent working on the incident

4. View additional comments

Open

On this page