Interactions is a different view of the Timeline that returns one row per Interaction.

The Interactions section displays a chronological list of interactions, such as form submissions, message history, and payment history, that have taken place on the constituent record.

Sort interactions by column header:

Search for specific interactions using Search Interactions.

Types of interactions

Messages

A Message interaction is automatically added to the record when the following communications are sent:

• Form communications

• Event communications

• Interview communications

• Deliver email messages

• Ad-hoc messages sent through Slate or the Slate Email Gateway

For example, someone who submits multiple event registration forms will have Message interactions for each of the event communications that were sent:

Sources

A Source interaction is automatically added to the record for the following items:

• Form registration

• Event registration

• Interview registration

• Source file import from Upload Dataset

• Application creation

For example, someone who submits multiple forms and also has had data imported into Slate from Upload Dataset may have a record with the following Source interactions:

• These items were added to the record through Upload Dataset.

• When a student cancels their visit, the Source code interaction remains on the record, but it displays in lighter text.

• The name of the Slate user who updated the registration status for this event appears in the User/Status column.

• Click a Source interaction to view information related to that source. For example, event registration interactions will display the registration form responses.

Event registration status

The Event registration status appears in the subject of the interaction row.

For example, when a prospective student originally registers for an event, the status of that event registration is Registered. If the registration is cancelled, the status updates to Cancelled. If the prospective student attends and is checked-in for the event, the status changes to Attend. If the prospective student does not attend and is marked as a No Show, the status then changes to No Show.

Custom interactions and activities

You can create your own interaction or activity codes and subcodes.

📖 Further reading: Create your own interaction types with Custom Interactions.

Adding an interaction to a record’s Timeline

New interactions can be added directly to the record by selecting New Interaction.

A pop-up appears. Configure the following settings:

• User: The Slate user associated with the creation of the interaction.

• Code: Select the Activity or Interaction code to be inserted on the application or person record. Additional options may be available depending on the type of code selected. When adding an activity to an application, typically, users will insert payment activities or modify form/event registrations in this section.

• Subcode: If you have created any subcodes under the parent code you selected, they appear here. The subcode narrows down the activity type.

Different settings appear depending on the code you selected:

Forms and Events settings

• Category: Select the appropriate application-scoped form or event registration folder for the activity.

• Instance: Select the individual instance within the folder to identify the exact form or event registration to be added as an application activity.

• Status: Choose to insert the activity with the applicant as registered, attended, or no-show for the forms and events registration.

Payment settings

• Date: Select the date the activity takes place. This date defaults to the current date and time. Can be post- or ante-dated.

• Payment Type: Choose whether the payment activity is due, received, waived, or refunded.

• Payment Amount: Enter the amount associated with the payment type.

• Payment Account: Choose which payment account should be associated with this payment activity.

• Expires Date (Payment Due only): If not specified, access to payment page does not expire.

• Private Comments: These comments are visible only upon clicking in to the interaction from the Timeline and are not displayed to the student/person.

Source or custom interaction settings

These settings appear both for the Source interaction code as well as any custom interaction codes in your database.

📖 Further reading: Custom interaction codes

• Date: Select the date the activity takes place. This date defaults to the current date and time. Can be post- or ante-dated.

• Subject: This subject displays under the Activities section of the application tab as well as the timeline on the person record. If no additional information is needed other than the interaction code, leave this blank.

• Private Comments: These comments are visible only upon clicking in to the interaction from the Timeline and are not displayed to the student/person.

• Public: Select to post to online status (includes subject and public comments).  Exposes a Public Comments text field if selected.

• Public Comments:  These comments will be displayed to the applicant/person.

Watch flag settings

📖 Further reading: Watch flag interaction

• Date: Select the date the activity takes place. This date defaults to the current date and time. Can be post- or ante-dated.

• Subject: This subject displays under the Activities section of the application tab as well as the timeline on the person record. For a watch flag, the subject is what displays on the top of the entire person record.

• Private Comments: These comments are visible only upon clicking in to the interaction from the Timeline and are not displayed to the student/person.

• Public: Select to post to online status (includes subject and public comments).  Exposes a Public Comments text field if selected.

• Public Comments:  These comments will be displayed to the applicant/person.

Adding links to interactions

You can add a link to an interaction or activity by including a web address in any of the following within the interaction or activity:

• Public Comments

• Private Comments

• Subject

When saving an active link with an interaction, include the correct https:// or http:// prefix in the URL to ensure a functional hyperlink.

Slate adds links in alphabetical order.

Links in an interaction:

Links in an application activity:

Up next: Audit Log

➡️ Audit Log