Jebbit can pass collected user data to your Kustomer and associated attributes as Kobjects Fields in real time.
Setting up a Kustomer Integration
There are a few steps we ask you to take so that Jebbit can securely receive access to perform the integration. You will need administrative access to access these
1. Create New API Key
All requests to the Kustomer API are authenticated using an API token that is included with the Authorization header of your request. Admins can manage API keys from within Kustomer from the API Keys settings page. You can access this page by going to Settings and selecting Security > API Keys.
When creating a new key, you can select an API role and apply a descriptive label to the key. Roles are useful to limit the operations requests using that key can perform.
2. Create custom Klasses
You can use custom Klasses to model individual business objects that may have multiple relationships, or to map to your specialized business process in Kustomer. When you create a custom Klass, you can define the name, icon, and color of the Klass.
To create a custom Klass:
Go to Settings and select Platform > Klasses.
Select Add Klass.
Enter a name. Optionally, select an icon and the icon's color.
Select Create.
Add custom attributes to a Klass
You can add attributes to both standard and custom Klasses.
To add an attribute:
From that object's page, select Create Attribute.
Enter a display name for the attribute. Note the following:
When you create the new attribute, Kustomer will automatically generate the attribute's name based on the Display Name and data Type. For example, an attribute added to a custom Klass for an order that has "Assigned User" as the Display Name will have "assignedUserId" as the Name.
An attribute's Display Name and Value properties can be changed after creation, but Name and data Type cannot.
Select a data type from the Type drop-down menu. The following options are available:
Single line text - for example, product name or item color.
Paragraph - for example, notes on a transaction.
Number - for example, price, quantity, or numeric tracking number.
Date - for example, 01/01/2020.
URL - for example, www.kustomer.com
True/False
Multi level list - for example, Level 1 > Item 1.
Id - for example, a kObject.
User Picker - for example, John Doe. Only active users within your org can be selected.
Customer Picker - for example, Jane Doe.
Select the field value for the attribute type. Available options are:
Single Value are fields that accept any value that matches the data type.
Option List will only accept pre-defined values.
Select Create. Continue adding the necessary attributes for that Klass.
Tip: You can require fields to be filled out before marking a conversation done on the standard Conversation Klass.
3. Copy API Integration Information to a .txt file
Collect the API Token and KObjects/atrributes Jebbit will pass attributes collected from Jebbit as kobject, specifically passing the kobject field ID.
Copy the values from steps 1-3 into your .txt file.
4. Submit your .txt file via Dropbox File Request
For security reasons, we ask that you transfer the information from your .txt file via Dropbox File request. Please submit your file using this URL.
Our Jebbit Integrations Team will be notified once this information is submitted, and will be in contact with you regarding timelines and testing.