The Customer Support dataset is used within the Immersion block, and is comprised of four (4) datasets:
- Tickets
- Users
- Customer Satisfaction (CSAT)
- Team Ledger
Important Note
These datasets are small on purpose, and not to be underestimated. It's incredibly powerful, and a great learning environment to know exactly what you're dealing with. In each new learning endeavor you'll be able to see the entire dataset shift in front of your eyes, thus allowing you to easily quality assure your progress. You'll still have an opportunity to uncover sophisticated SQL tasks.
Dataset Overview and Specifications
All of the support tickets that have been opened by customers.
Fields
This dataset contains eight (8) fields with one thousand two hundred (1,200) total entries/rows of data. Below is a breakdown of each field:
ticket_id (INT)
Unique identifier for each support ticket that's opened
ticket_created_ts (TIMESTAMP)
Timestamp recorded upon a ticket being created
ticket_closed_ts (TIMESTAMP)
Timestamp recorded upon a ticket being closed
priority (TEXT)
The priority of the ticket
category (TEXT)
The category/type of ticket
user_id (INT)
The User ID for the customer who needs support
assignee_id (VARCHAR)
The customer support agent that supported the user
status (TEXT)
The status of the ticket
Relationship(s)
Because this dataset is in the Immersion block, it's important to identify dataset relationships on your own (as this is what it's like in the "real-world").
Find yourself still needing help? Reach out via the Community, or Slack if you're a Premium Member.
The customer list.
Fields
This dataset contains four (4) fields with five thousand (5,000) total entries/rows of data. Below is a breakdown of each field:
user_id (INT)
Unique identifier for each customer
signup_month (DATE)
The month in which a customer signed up for an account
paid_user_flag (BOOLEAN)
Whether or not the user is a paying a customer
region (TEXT)
The general region where a customer resides
Relationship(s)
Because this dataset is in the Immersion block, it's important to identify dataset relationships on your own (as this is what it's like in the "real-world").
Find yourself still needing help? Reach out via the Community, or Slack if you're a Premium Member.
The submission of Customer Satisfaction surveys from customers
Fields
This dataset contains three (3) fields with eighty five (85) total entries/rows of data. Below is a breakdown of each field:
ticket_id (INT)
Unique identifier for each support ticket that's opened
csat_submission_ts (TIMESTAMP)
The timestamp in which the survey was received
csat_score (INT)
The score the customer provided to us (1 = Poor Service / 7 = Great Service)
Relationship(s)
Because this dataset is in the Immersion block, it's important to identify dataset relationships on your own (as this is what it's like in the "real-world").
Find yourself still needing help? Reach out via the Community, or Slack if you're a Premium Member.
A record of the customer support agents
Fields
This dataset contains five (5) fields with two (2) total entries/rows of data. Below is a breakdown of each field:
agent_name (TEXT)
The name of each customer support agent
team (TEXT)
The name of the team the customer support agent is on
start_date (DATE)
The date the customer support agent started
end_date (DATE)
The date the customer support agent stopped working on the team
crm_id (VARCHAR)
The ID associated to the customer support agent for the technology where they do their work
Relationship(s)
Because this dataset is in the Immersion block, it's important to identify dataset relationships on your own (as this is what it's like in the "real-world").
Find yourself still needing help? Reach out via the Community, or Slack if you're a Premium Member.