Call List Query & Form Template
- Helen Williams
Slate Instance | TUP |
Requestor | Hannah Fridy |
Date | 3/11/2024 |
Status | completed |
Summary Description | Develop a query template and a form template with documentation/instructions so that TUSMGP staff are consistently tracking outbound recruitment calls in a way which can be used for lead scoring and reporting. |
Jira Link:
Detailed description of desired deliverable:
TUSMGP currently has several “call lists” which have been configured by different staff and range from somewhat correctly formatted to not formatted correctly at all, which has led to a loss of data and information about the outcomes of those calls.
In addition, Hannah has been building a new system to generate lead scores, and the call lists need to comply with this system.
Finalizing this will also support the audit of the activity and interaction codes (and possibly forms) to continue the long-term project of “cleaning up” the TUSMGP instance of Slate.
Research:
In order to review existing call list forms, we had to figure out how to find out which queries and forms are configured for call lists. This ended up being a bit of an adventure. Eventually I determined that the only way to see that a query was configured to support a call list was to look at a field not available via CJ called config. This field contains XML coding which includes both a variable for call_list and the GUID of the associated form.
This query identifies all queries that have the text “call_list” in the config field and exports the full XML in the query.
https://tusmgp.admissions.tufts.edu/manage/query/query?id=0ab4c965-6006-42a1-a88f-9edfe0ca2a38
By exporting to Excel and manipulating the data in the config field I could pull out just the GUID for the form that is associated with the query. I then de-duped the list and ended up with 17 associated form GUIDs. Using that to filter to form data:
https://tusmgp.admissions.tufts.edu/manage/query/query?id=626eb173-b592-4cb9-8c05-2347c3fbdc0d
I can identify the 17 forms that are used as call lists. Last, I went back to the full query list and matched the names of the forms to the GUID so it would be easier to interpret. Below are the two spreadsheets of data I ended up with:
I then reviewed the 17 forms to see how they were used:
All forms had been saved in the Outreach folder, so that’s good.
Of the 17, only 9 had been used in the last 2 years, so I reviewed those.
Form Name | Date of last Submission | Notes |
|---|---|---|
AAP Yield Contact Report (2024) | 3/4/2024 18:44 | Nothing mapped to interaction/activity code or system fields. Use this form to log yield phone calls to admitted students. The goal is to understand whether a student wishes to attend Tufts. |
Su24 Inquiry Contact Form | 12/11/2023 14:45 | Nothing mapped to interaction/activity code or system fields. Use this form to log phone calls to inquiries. The goal is to understand whether a student in interested in applying and drive them to submit their application. |
DPT Deposit Deadline Reminder | 11/28/2023 10:14 | Nothing mapped to interaction/activity code or system fields. Has field for applicant name (why?). |
In-Person Open House 23 Reminder Calls | 11/1/2023 11:33 | Nothing mapped to interaction/activity. DOES HAVE MAPPED TO SYSTEM FIELDS FOR NAME. |
In-Person Open House Call Form | 10/26/2023 9:14 | Nothing mapped to interaction/activity code or system fields. Has field for applicant name (why?). |
AAP In Progress Contact Report (DPT) | 7/20/2023 10:54 | Nothing mapped to interaction/activity code or system fields. Description says it is for “in progress calls to admitted students” which seems wrong? |
PHPD - AAP In-Progress Contact Report (DPT) | 1/12/2023 16:25 |
|
PHPD - App Conversion Contact Report (MBS, F23) | 10/27/2022 11:24 | Does map to an activity: User, Code, and Private Comments. (App Conversion > Await Submission > one of the four sub-codes). |
PHPD - MPH Staff Admit Calling | 5/12/2022 11:21 | Has status of TENTATIVE. Nothing mapped to interaction/activity code or system fields. |
Outcome:
Original plan was to create a form template and query template to use to build new call lists, but ran into a snag when discovered that when copying a form all conditional logic is removed (even if using a form template and not just copying a form as usual).
Slate solution is to use Suitcase (bizzare and annoying!) https://feedback.technolutions.com/forums/923530-slate/suggestions/38529169-carry-form-logic-over-to-copies-when-using-copy-f
Query Template
Form Template
Entity