YisraCase
Case management, shaped to your workflow.
Matters, contacts, calendars, tasks, documents, forms, e-signature and a full automation engine — one system, configured around the way your office actually works instead of the other way around.
Where it comes from
Built inside a working practice, not a pitch deck
YisraCase wasn’t designed in the abstract. It grew inside a busy law office, one real bottleneck at a time — intake, scheduling, document chasing, signatures, follow-up — and it runs that practice in production today.
That origin shows. Every feature exists because someone needed it on a live file, and the configuration surface exists because no two practices work the same way.
The core
Four things every practice runs on
Everything else in YisraCase hangs off these.
Matters
Cases, claims, engagements — whatever you call them. Types and subtypes with their own stages, statuses and checklists, so a file always shows where it stands and what’s next.
Contacts
People and organizations in one place, connected to matters by role — client, opposing party, referral source, or any role you define — with their full history alongside.
Calendar & booking
Appointments and deadlines on the file, synced with Google Calendar, plus public booking pages so clients pick a slot instead of playing phone tag.
Tasks & activity
Task lists tied to matters and stages, and an activity log that keeps who-did-what-when on the record without anyone writing it down.
YisraFlow
Automation that follows through
Triggers fire workflows. Sequences pace the follow-up. Scheduled jobs sweep up the rest. Build a chain below — this is the shape of it, simplified.
When this happens…
…YisraCase runs this
Illustrative examples. Real workflows are built from trigger rules, condition filters, an internal function library, and templated variables — and they’re yours to edit.
The rest of the toolkit
Modules that earn their place
Each of these shipped because a real office needed it. Use the ones you need, ignore the ones you don’t.
YisraForms
A form builder with conditional logic, autosave and field-level write-back — intake data lands on the matter, not in an inbox.
E-signature
Reusable templates, send-for-signature flows and automatic filing of the signed document back onto the matter.
Documents
Matter-linked document management backed by Dropbox, with document request links that let clients upload straight to the file.
Client portal
A place for clients to see what you choose to share and act on what you ask of them — without another phone call.
Self-service scheduling
Booking pages and self-service links that put routine scheduling in the client’s hands, on your rules.
Reports
Reporting over your live data — pipeline, workload, activity — without exporting to a spreadsheet first.
YisraView
Custom views over any of your data, so each role sees the columns and filters that matter to them.
YisraVideo
Hosted video with tracked landing pages — send a recorded explainer and know it was watched.
Tracked links
Branded short links with click tracking, for campaigns, print pieces and everything you send out.
Webhooks
Inbound webhooks route outside events — form fills, telephony, partner systems — into matters, contacts and workflows.
Landing pages
Campaign landing pages served from the platform itself, feeding the same intake pipeline as everything else.
Alerts
System alerts that email or text the right person when something actually needs a human.
Integrations
Keep the tools you already trust
YisraCase started with a hard requirement: the attorney it was built for wasn’t going to change how he worked. The software had to adapt to him — not the other way around.
That requirement became the architecture. Every outside service — phones, email, storage, signatures, contacts — plugs in through a driver: a small adapter that teaches YisraCase to speak that tool’s language. The rest of the platform doesn’t know or care which vendor sits on the other end. A text message is a text message whichever phone system sends it; a file is a file wherever it lives.
So you don’t inherit our vendor choices. Start on the defaults, or have us connect what your office already uses — and because drivers are small, wiring up a tool we haven’t met yet is a routine job, not a rewrite.
- RingCentral calls & SMS
- Quo calls & SMS
- Gmail email
- SMTP any mail host
- Google Contacts contact sync
- Google Calendar two-way sync
- Dropbox document storage
- Zoho Sign e-signature
- Clio practice data
- Webhooks anything with an API
No black box
A system you can actually look inside
Most practice software asks you to trust it. YisraCase assumes you’ll want to check.
Your data, on your terms
API keys for integrations and scoped read-only keys for reporting and analysis — your data is queryable, not captive.
Admin tools built in
A database console, an API tester and system alerting ship with the platform — the owner’s tools, not an afterthought.
Documentation in the app
The manual lives inside the product and moves with it, so help reflects the system you’re actually running.
Tells you when it matters
Severity-based alerts reach the right channel — email for the notable, text message for the urgent.
Where it’s headed
One engine, any practice
The configuration surface — matter types, stages, statuses, checklists, contact roles — already means YisraCase isn’t hard-wired to one kind of work. The direction from here is to finish that thought: pre-built configuration packages for common verticals, and AI-assisted setup that turns a plain-English description of your practice into a working configuration you can refine.
Roadmap, stated as roadmap — if you ask for a demo, we’ll show you what exists today and tell you plainly what doesn’t yet.
See it for yourself
The demo is the argument
Screenshots don’t show you how a system feels to live in. Tell us a little about your work and we’ll walk you through YisraCase on a real screen.
Request a demo
Two fields and a sentence. We’ll take it from there.