Skip to main content

Smokeball Connector

You can now bring your case and case files directly from Smokeball into Supio!

Overview

The Smokeball integration allows Supio to automatically sync cases from a customer's CMS into Supio twice daily. Once synced, case files and basic information become available in Supio for document intelligence and AI-powered analysis.


Setup Steps

Step 1: Install the Integration

  1. Navigate to Apps

  2. Scroll down and locate Smokeball

  3. Click Install

  4. Click Connect to authorize the connection

Step 2: Reach out to Supio Support or your Customer Success Manager

  1. Once you have installed the Smokeball connector within Supio, reach out to support@supio.com or your Customer Success Manager so we can enable the data sync.

Step 3: Configure Cases for Syncing

Cases are synced based on a task trigger in Smokeball. Within Smokeball:

  1. Open any case in Smokeball that you want synced to Supio and navigate to the “Tasks” tag.

  2. Add a task to the case that includes the word "supio" in the task name (the word is case-insensitive)

  3. A team member must be set for the task - we recommend assigning the task to yourself.

  4. Optionally, add categories to the task to specify what artifacts you want Supio to generate.

Supported Supio Categories

Output

Description

Supio-Deep-Dive

AI chat and case analysis

Supio-Chronology

Medical chronology

Supio-Liability-Demand

Liability demand letter

Supio-UM-Demand

Uninsured motorist demand letter

Supio-UIM-Demand

Underinsured motorist demand letter


Sync Behavior

  • Supio checks for cases twice per day (every 12 hours)

  • Once a case is synced, all associated files and basic case information will appear in the case in Supio.

  • You can then use Supio's document intelligence features to analyze the case


Troubleshooting / Common Questions

Issue

Resolution

Case not appearing in Supio

Confirm the task includes the word "Supio" and that CSM has enabled the integration on the backend

Integration not connecting

Re-attempt the Connect step in step 1 and verify credentials

Outputs not generated

Ensure the desired outputs (Deep-Dive, Chronology, Demand-Letter) are specified in the task categories

Did this answer your question?