Drafted for SmokeballSome of what we build on Smokeball
Intake to consults
We turn web and phone inquiries into intake summaries, and your team runs conflict checks and decides which ones to book as consults.
Deadlines on the matter
We draft court dates and deadlines from your documents, and an attorney confirms each one on the matter.
Time and billing
We tidy time entries and draft invoices for your billing team to review.
Client updates
We draft client status updates from your matter notes for an attorney to approve.
Document intake
We read, name and file client documents to the right matter.
Answers for your staff
Staff get answers to internal procedure questions from your own playbooks.
Smokeball gives a firm API access when the firm asks for it through its Smokeball account manager. Once access is granted, keys and authentication are managed in Smokeball’s Developer Console, and Smokeball can send webhooks when files are uploaded, changed or shared, or when other Smokeball records change. Sastre makes that request alongside your firm and then connects Smokeball to the rest of your tools, with your team approving each change before it is saved.
Document work is where Smokeball firms feel the handoffs most. Smokeball describes its platform around document automation and legal workflows, and the steps that feed those documents still arrive from outside: intake answers by phone and email, signed forms back from clients, records from third parties. A webhook on each upload lets a workflow name the file, read what it is and propose where it belongs, so your staff confirm a filing and skip the sorting.
While the access request is pending, the work does not have to wait. We start from the exports your staff can pull from Smokeball and queue each drafted change for someone on your team to enter, then move the workflow onto the API once access is live. Browser steps are used only where your firm approves them, and each one is logged.
Once the connection is live, Smokeball workflows can cover:
Documents that arrive by email or upload are named, labeled and filed to the right matter after a staff member confirms them.
Intake answers from calls and web forms become a draft matter, and the names in them are checked against your existing contacts for an attorney to clear.
Consults that never turned into an engagement are listed each week with their last message, for your intake team to decide on.
Signed forms returned by clients are matched to the right matter, and the next step is drafted for your staff.
Answers to staff procedure questions come from your firm’s own precedents and playbooks, with a link to the source.
The approvals arrive by email, and the action log your firm owns records each draft, who approved it and what changed in Smokeball. ABA Formal Opinion 512 leaves the question of informed client consent to the firm, so we set out every tool and data flow in writing for your attorneys.
For a technology company, our pipeline assistant sorts old and lost deals into lists worth a second look and checks new leads for duplicates before they reach the CRM. On Smokeball, consults that stalled before an engagement letter can be surfaced the same way.
Some tools we connect to Smokeball
Questions about Smokeball and AI
How does our firm get Smokeball API access?
Your firm requests it through your Smokeball account manager, and we prepare that request with you. Keys and authentication are then managed in Smokeball’s Developer Console.
Can you start before API access is approved?
Yes, we begin from the exports your staff can pull and queue drafted changes for your team to enter. Once access is live, the same workflow moves onto the API.
Do clients need to consent before AI touches their documents?
It depends on what the tool does with the information, your engagement terms and your state’s rules. ABA Formal Opinion 512 asks for informed consent before confidential information goes into a tool that can learn from it, so we document each tool and data flow for your firm.
How is client information in Smokeball protected?
Each workflow holds only the Smokeball access it needs, and your firm can withdraw it at any time. Client documents are kept out of model training by our providers’ business terms, every action is logged, and we delete the client data we hold 30 days after an engagement closes.
What does a Smokeball project cost?
We start with a free working session of about an hour on one Smokeball workflow, such as document intake or new matters. The workflow map after it ends in a fixed quote, and its fee is credited to the build.