The Complete Guide to Connecting Technolutions Slate and Olark Live Chat
Why Connect Olark to Slate?
There are many reasons why you should integrate Slate and Olark. Here are the highlights:
- Measuring effectiveness. With Slate and Olark working together, you can measure the effectiveness of Olark and gain insights to increase student engagement and service.
- Saving your team time and providing better service. With Slate and Olark working together, you can avoid extra clicks and automate repetitive tasks. Out of the box, Olark passes along a link to Slate student records for existing students in Slate, and your Olark account manager can help you unlock additional capabilities: route based on the content of the conversations, automate FAQs, and make sure students questions are routed to their admissions counselor when they are available.
- Better lead capture and lead scoring. Data from Olark can both help increase the lead score of highly engaged students and help add prospective students that are asking questions—but haven’t started applying—to the top of your funnel.
A successful integration will help your team be more effective, provide tactical tools to help you increase enrollment yield, and give you strategic information to make long-term decisions around maximizing yield with chat.
Here’s a realistic view of what someone could do with an Olark report in Slate. (Data is made-up data from one of our partner schools):
How to integrate
Most of our partners have Olark running in with Slate in their test environment within a day of involving their Slate/CRM administrators, and go live in production within 2 weeks. An experienced Slate administrator can set up the integration in between 1-4 hours, including all coordination with Olark.
Note: This integration requires an Olark Pro account.
We always recommend starting simple and then expanding with more customized functionality. If you need more guidance, your account manager can talk you through the pros and cons.
We recommend completing these steps once with your test environment, and then once again in production once you are satisfied with the integration.
To ensure you are working with relatively recent data, it might help to update your test environment with the latest data from production before getting started. If you are unfamiliar with this step, we’ve added a quick tutorial at the end of this document.
Step 1 - Create a new interaction type called “Chat”
Start by creating a new category of interaction with students. Slate calls each category of interaction an “interaction code”. We’ll associate all the Olark interactions we push into Slate with this interaction code.
It’s good to get this out of the way since our customers report a delay in the amount of time it takes Slate to show these fields up as an option in Remap.
Create an interaction code for chat Go to Database and select Activity & Interaction Codes. Click “Insert”. In the popup, choose the Code “chat” and Label “Chat” for your interaction code, and then save.
Step 2 - Create a username and endpoint so Olark can give operators a link to information inside Slate
This is a quick way to save time for your Olark operators by adding links to Slate user context into Olark. This endpoint will also be used in the future to extend Olark with more automations, by taking an Olark-provided student email address and matching it with a record in Slate.
Creating the query endpoint
Go to the Queries page.
Click the New Query button and create a new Configurable Joins query with the Person base. (Make sure the User, Realm, Sharing, and Folder settings are appropriate for your instance and business practices.) These settings determine how your query is shared/displayed to other Slate users. We’ve included possible settings, but how you set it up may vary slightly, depending on your school’s way of organizing folders and permissions.
Click the Edit Web Service button.
Add the following custom parameter:
<param id="email" type="varchar" />
Select JSON as the Service Type and then save.
Add a subquery filter, symbol as shown: Select Formula in the Aggregate dropdown.
Add an export for Person Email: This formula will take the @email parameter (provided by Olark) and match it to any record in the system with that address as their rank-one email.
Enter @Person-Email = @email in the formula box.
Then click Save.
Add two Exports: Person Reference ID and Person GUID. Your final query should look like this:
Create a web service username to give access to this query. In the Olark Endpoint query you just created, click the Edit Permissions button and then Add Grantee.
Set the type to Username. Give it a name, username, and password (we recommend calling it “Olark” as the name, and something like “olark-slate” as the username). You’ll need to provide the username and password to Olark later. Make sure to check the Web Service checkbox before saving these settings.
After saving, close Edit Grantee by clicking the X. Back in your query, click the JSON link in the top left.
In the popup opened by clicking the JSON link, choose the Service Account in the dropdown that you just set up. Copy the URL to give to Olark.
To send Olark the credential information, contact your account manager to set up a secure transfer.
Step 3 - Configure your Olark Import endpoint inside of Slate
Now you’ll want to define where your Olark data will live inside Slate. In Slate, go to the Database page and choose Sources / Upload Dataset. In the sidebar, select Source Formats and click the New Source Format button.
In the popup, use the following settings in the General tab. Make sure to follow them exactly. (See screenshot below for how they appear on the page.)
Remap As of Date: Today’s Date
Remap Active: Inactive
Replace Existing Datasets: Inactive: Files are ad-hoc
Scope: Person/Dataset Record
Unsafe: Safe: Sources will not update person-scoped data for records with active applications
(This import will still add interactions to records with active applications! However, since it’s not adding or modifying any biographical information, it’s better to leave it as a Safe import.)
Hide: Hide source interactions
(Olark will add a source interaction every time a student initiates a chat, in addition to the user-facing Chat interaction. You can choose not to hide the source interactions if you prefer to see them in the Interactions section of the timeline.)
Disable Update Queue: Allow records to enter update queue upon import (allows rules to fire)
(Allow rules to fire if you use rules for functions like interest level or lead scoring.)
Update Only: Update only
Notification: No notifications
Read Permission: (leave blank)
Upload/Build Permission: (leave blank)
In the Format Definition tab, paste the following code into the XML box:
<layout type="xml" node="/interactions/interaction"> <!-- only visible when we can find the student email address --> <f id="Student Slate ID" s="slate/PersonReferenceID" /> <f id="Student Email" s="visitor/emailAddress" /> <f id="Student First Name" s="visitor/firstName" /> <f id="Student Last Name" s="visitor/lastName" /> <f id="Operator Email" s="operator/emailAddress" /> <f id="Interaction Start Timestamp" s="timestamp" /> <f id="Interaction Subject" s="subject" /> <f id="Interaction Body" s="body" /> <!--TODO: consider adding additional fields for tags and chat feedback --> </layout>
Note: There is more data passed into Slate from Olark than shown in the above mapping template. For each interaction we have complete data from the Olark webhook API available. This should get you started, but to optimize for your use case, talk to your account manager.
Step 5 - Create secure remote access to your your Import endpoint
Now you’ll connect your import endpoint to a new service account for Olark, to use to make imports. The service account will be used to push data automatically into Slate with a 15-minute delay when a chat is complete (this 15-minute delay is based on your Slate import settings for web services).
Go to the Database page and click User Permissions. Click the New User button to make the service account.
Fill in the First Name as “Olark,” Last Name as “Service Account,” Preferred Name as “Olark,” and Email field with your Slate administrator’s primary contact email.
Select Service Account as the User Type. Choose a secure user ID and password for the service account. We recommend using “olark-slate-import” to make it easy to remember the purpose of the user account. Make sure to check Enable account for access before clicking Save.
Step 6 - Contact your account manager so we can set things up on our side.
In most cases it’s good to set up a shared Slack or Teams channel with Olark, and/or hop on a Zoom phone call to verify that everything is set up correctly for Olark to work with your Slate environment. You can shoot us an email at email@example.com or email your account manager directly to set this up.
We will need the following to set everything up in one go.
- The URL for the export query you created to get student information by URL. This should look like:
- The username and password for the service account that has access to this export query.
- The domain name of your test and production Slate instance:
- The web services endpoint where we will be posting student interactions:
- The username and password for the service account that has access to this import endpoint.
- Confirmation that the following URLs will work given how your Slate instance is configured:
- An example of a test student email for us to test the integration with. A dummy account is fine.
Step 7 - We’ll send in sample data that you can Remap in Slate
We’ll create your custom Slate integration on our side, and send some test data over while we are chatting on Zoom or on a shared Slack channel. Once this test data is sent in, we can work together to map the fields from Olark into your Slate instance.
How to see the pending web service imports (test data) from Olark Go to the Database page, select Sources / Upload Dataset, click Source Formats in the sidebar, then select the Olark format. Here you can see the web services imports:
Note: While implementing, you may want to pin the Olark source in the Database tab for easy access.
To speed up imports while testing: While on the call with your Olark rep, you can speed up Slate’s automatic 15-minute import interval. On the Database page, select Force Process Import. (Since this will run all pending imports, you may want to check and make sure you don’t have any large imports pending prior to the call.)
Remapping the fields: Once Olark has posted data for the first time, you’ll be able to remap. In the Olark Source Format, click the Remap button. Map to the following standard Slate fields:
|Source Field =sample value||Destination|
|Student Slate ID =123456789||Record - Slate ID Matching Only|
|Student Email =firstname.lastname@example.org||(Do not map)|
|Student First Name =Ella||(Do not map)|
|Student Last Name =Student||(Do not map)|
|Operator Email =email@example.com||Interaction - Interaction: User|
|Interaction Start Timestamep =10/14/2021 06:4…||Interaction - Interaction: Date|
|Interaction Subject =Chat on https://admission…||Interaction - Interaction: Subject|
|Interaction Body =https://www.olark.com/tranc…||Interaction - Interaction: Private Comments|
In Slate, it will look something like this:
Remapping Olark operators to Slate users
Value Mappings: In the sidebar, select Value Mappings. Click the Interaction: User mapping and make sure all possible Olark operator emails are mapped to Slate user accounts. You can get a list of your current Olark operators from the Olark team page. Use the Append Values button at the bottom of the popup to add emails to the list.
Static Mappings: In the Static Mappings section, click New Static Mapping. In the popup, select Interaction as the destination, and then Interaction: Code in the second dropdown menu that appears. In the Value field, type the name of the interaction code you created earlier, select it from the suggestion list, and then save. (Your interaction code name from Step 1 will likely be called something like “Chat”.)
Your static mapping should look similar to this:
Activate the Remap when all the mappings are in place: When you’re ready, return to the main view of the Olark source format and click Edit. Set the Remap As Of Date to today and set the Remap Active to Active, then save.
Once this is done, you can navigate to the user linked to one of the records you just populated from the Olark interactions import, and see the chat show up on the student’s timeline.
When you click on this chat, you will see additional details like comments and transcript:
Step 8 - We’ll finalize the integration on our side by linking it to your Olark instance
Inside of Olark, the integration will appear as a webhook. You shouldn’t need to use this interface to manage the integration, but just be aware this is where it lives, and it can be disabled and enabled from here.
Step 9 - Run the Slate integration from your test environment for a few days and let Olark know when you are ready to go to production.
To go to production, repeat the above steps 1 through 8 with your production instance of Slate, and coordinate with our team to set up a time to verify your setup. Since you’ve already done the steps once, the process will be mostly identical and go pretty quickly. To ensure there are no delays in getting the imported data Remapped, give us a little bit of notice to make sure we are available to push in test data when you need it.
Step 10 - You are all set.
Congrats, you’ve now integrated Slate with a powerful new tool! Your data team can now run reports on Olark inside of Slate’s interface. Your Olark agents and admissions counsellors can save time with direct links to Slate student records and all Olark history appearing on student timelines.
Step 11 - Talk to us about how we can streamline things even more.
Reach out to your account manager if you have feedback or requests. Improving automation for higher education customers is a key priority for Olark. We’d love to understand how we can make your workflow more efficient, and help you get all the data you need in one place. Olark integrates with a variety of analytics and automation platforms, and our CoPilot chatbots can be tailored to your exact use case, including financial aid, student services, admissions counselling, housing, and more.
Appendix: Refreshing your test environment
We recommend refreshing your test environment if you haven’t done so in the last month. Using an out-of-date test environment means using outdated data, which can result in (among other things) missing student contact records to align with your Olark chat data.
Important: Before updating your test environment, check with other Slate users to make sure there is no unsaved work.
When you’re ready, go to the Database page and select Launch Test Environment. Click the Request Refresh button and submit your request. The process of updating your test environment with the latest data from Production normally takes a couple of hours.