Skip to content
    Back to blog
    IMPLEMENTATION

    Supio and Smokeball: Check Activation, Case Sync and Outputs

    By VerifyMD5 min readSupio, Smokeball, case integration, personal injury

    Separate connection, case selection and generated output

    Check Supio and Smokeball activation, matter selection, document sync and output requests separately before reconnecting or uploading another case copy.

    Use the connector-specific instructions

    Smokeball's Supio integration guide, updated March 30, 2026, displays availability on Grow and Prosper+. It describes active accounts plus Supio Customer Success Manager activation. An assigned Smokeball task containing supio selects the matter; optional task categories request outputs. The guide describes a 12-hour cycle and CSM help linking existing manually created Supio cases. Check your firm's eligibility and configuration rather than treating a connected app as a completed setup.

    Supio's current integrations page describes sync timestamps and manual resync, alongside broad real-time connectivity language. That does not settle the schedule or supported return fields of a particular Smokeball installation. Confirm the current connector behavior with the responsible support team before promising an update time. This article uses published documentation and a fictional diagnostic exercise; it is not a test of a live account or a guarantee that every described setting applies to your firm.

    Identify the first stage without evidence

    When a matter seems missing, write down what is actually absent. Is the connection unavailable, the matter absent, a particular document missing, or an expected output not generated? Those observations need different evidence. Start with the first uncertain stage instead of repeating the whole setup. Follow current vendor instructions for configuration changes, and use the firm's authorized administrator when a change affects access.

    Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.

    Proposed diagnostic log: identify the first unconfirmed handoff
    StageEvidence to inspectIf still unknown
    Connection and activationAuthorized connection plus confirmation of required activationAsk the administrator or vendor which prerequisite remains
    Matter selectionIntended matter reference and the selection configurationCheck the current connector-specific selection instructions
    Documents visibleExpected file in the correct matter and observed sync statusIdentify the missing source and last known event
    Output requested and producedRequested output, actual generation state and source referencesInvestigate output configuration separately from file transfer
    Team reviewNamed reviewer and accepted or unresolved resultKeep substantive review open after transfer succeeds

    Keep a small receipt log: internal matter reference, stage checked, observed state, time and next owner. Use approved private systems for identifiers. A screenshot should show only what support needs, without an entire client file. A blank status is unknown, not proof that a connector failed.

    A fictional matter that appears without an output

    Fictional example: an administrator has confirmation that the connector is active. The assigned selection task is present, and after the scheduled run the matter and a test document appear in Supio. A colleague expected a chronology, but the output request had not been added. The correct investigation starts with the output request. Creating a second matter or uploading the same packet again would not address that missing instruction.

    For this exercise, the administrator checks the current output-request instructions with the team and records the authorized change. The task remains open until the expected output is observed and reviewed. The log does not predict how long generation will take. If no output appears, the next support question concerns that stage, with the existing matter and source-document references attached through the approved channel.

    Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.

    Fictional receipt log for one matter, with no promised completion time
    ObservationWhat it supportsNext action
    Activation confirmed by responsible teamThe setup prerequisite is documentedCheck the selected matter
    Matter and test document visibleThis file reached the intended workspaceInspect the requested output
    No chronology request recordedAn output instruction is still missing in this exampleAdministrator confirms the authorized configuration
    Output later appearsGeneration occurred for reviewReviewer checks the expected source and scope

    Resolve an existing matter before creating another copy

    An existing manually created matter needs an identity check before another copy is created. Compare the matter references in the two systems and ask the vendor how the existing record should be linked. Similar client names are not sufficient identifiers. Preserve any analysis or annotations already associated with the old record while the administrator confirms the supported approach.

    Before a manual upload or resync, identify what is missing and whether an earlier version exists. After an authorized corrective action, inspect the expected file. If duplication or version behavior is unclear, retain a small example for support instead of deleting files to make the screen look clean.

    Check one document and one output against their sources

    For a controlled acceptance check, use a permitted synthetic matter and a short fictional document with a distinctive title and known contents. Confirm that the correct matter receives it, that the source can be opened, and that the resulting analysis refers to the intended file. Later add a second clearly labeled version through the agreed path and inspect how the change is represented. These are proposed checks, not promises about any connector's version-handling features.

    If the expected output is a financial ledger, use the Case Ledger reconciliation checklist to review the source and total separately. A file being visible does not establish that a generated result is complete or correct. The integration check ends at the agreed handoff; the substantive review still needs a named person.

    Send a narrow support handoff

    A useful support request reports the narrow symptom, the last stage with evidence and the expected next event. Include approved references needed to locate the test. Distinguish file-addition time, observed synchronization and generation status. A stale document alone does not identify a failed connection.

    Ask support to confirm the current schedule, selection mechanism, supported file types and what data returns to Smokeball for your configuration. Document the answer and any changes that your administrator approves. Keep a rollback or recovery owner for material connection changes. The CMS integration planning guide helps organize those responsibilities without treating a vendor logo as proof that every desired handoff is configured.

    Keep integration scope separate from provider follow-up

    Use the Supio pricing scope worksheet to separate software access, connector setup, analysis outputs and support commitments in the quote. VerifyMD is a separate provider-follow-up service, not a Supio or Smokeball integration provider. Its firm-specific connections require separate scoping and testing; this checklist does not advertise a native adapter or give permission to connect accounts. Choose the tool and setup for the actual task, then verify that task's handoff.

    Explore provider follow-up and source review for your firm. Live calls require agreed setup and activation.

    Book a demo

    Explore the workspace.
    Start with one case.

    Create your account and explore at your own pace. Live provider calls start after your firm's permissions, service terms and calling setup are confirmed. Prefer a walkthrough? Book a 30-minute demo.