Bexar County Criminal Defense
Reset a court date by text
Court moves in the hallway, not on a software form, so the board listens for a plain-language text from your own Signal thread and updates the matter while preserving the old setting in the history.
Before you start
This works because court does not wait for you to open a laptop. A case gets reset in the hallway, the judge calls it for a new date, and you are already three courtrooms away. So the board listens for a text. You need your own trusted Signal thread, the one the watcher is set to read, and you need to know the two shapes a reset takes. A same-day in-court reset is a last name and a date, the way you already talk about it. An out-of-court reset uses an explicit command with the cause number. Either way the watcher reads only your trusted thread, and either way it would rather report ambiguity than guess a court date onto your calendar, because a guessed date is worse than no date at all.
Have the matter already open on the Case Board, so there is a case for the reset to land on, and have your Signal thread in front of you.
1. Send the same-day reset from the hallway
You are standing outside the courtroom and the case just got reset. Send the trusted same-day note from your own thread in the shape the watcher expects: a last name and a date, for example a client’s last name and 5/14. That is the whole message. You do not open the app, you do not type into a form, you send the text the way you would tell your paralegal what just happened.
The in-court reset watcher reads that thread on its hourly pass and also accepts a normalized #reset command if you prefer the explicit form. Either reads as the same instruction: this matter, this new date.
2. The watcher matches the message to the matter
On its next pass, the watcher reads the trusted message and matches it to the open matter by the last name and what it already knows about your boards. This is the moment the hallway and the board line up. The watcher is not guessing which client you mean from a stranger’s text; it is reading your own thread and resolving the name against the matters you actually carry.
If the name resolves cleanly to one matter, it moves to creating the new hearing. If it cannot tell which case you meant, it stops, which is the next-to-last step below.
3. The new future hearing is created, the old setting preserved
With the match made, the watcher creates the new future hearing on the matter for the date you texted. The key word is preserved: the old setting is not deleted, it is kept in the matter’s history, so the record shows the case was set for one date and reset to another. A defense file that quietly overwrites its own history is a file you cannot reconstruct under questioning. This one keeps the trail.
The calendar now carries the new date, the matter remembers the old one, and you did it from the hallway by text.
4. For an out-of-court reset, send the command form
Not every reset happens at the courthouse. When you need to move a hearing from your office, the out-of-court reset watcher takes an explicit command with the cause number and the new date, in the shape #outreset CASE_NUMBER month/day. It moves the next future event on that matter to the new date and preserves its details, the court, the room, the Zoom information, rather than rebuilding the event from scratch.
The command form exists because an out-of-court move is deliberate and benefits from naming the cause number outright. The same preserve-the-history rule applies.
5. When the message is ambiguous, the board opens a task instead of guessing
This is the safety rule that makes reset-by-text trustworthy. If the message is ambiguous, two clients share a last name, the date does not parse, the cause number does not match an open matter, the watcher does not drop a best-guess date on your calendar. It reports the ambiguity and opens a task for a human to resolve. A wrong court date is how a good lawyer misses a setting. The board refuses to manufacture one.
So a text that does not resolve cleanly comes back to you as a question, not a silent mistake. You clarify, you resend, or you fix it on the matter directly.
6. The reset shows up on the board and in the day’s review
Once the new hearing is written, it lives on the Case Board with the rest of the matter, on the same timeline as the appointment that opened the case and the hearings the court’s own feeds created. That night, the branded daily review that emails the firm a full accounting of the automations’ work includes the reset among the calendar changes, and the Sunday operations report rolls it up with the week’s resets and calendar moves.
That is the receipt. You reset the case the way you already talk about it, from the hallway, by text, and the system both made the change and showed you it made the change.
What you have now
A court date moved by a text from your own thread, with the new hearing on the matter, the old setting preserved in the history, and nothing guessed when the message was unclear. The in-court watcher reads the hallway shorthand, the out-of-court watcher takes the explicit command, and an ambiguous message becomes a task rather than a wrong date on your week. The change is on the board and in the night’s review. This is the board keeping up with the courthouse instead of asking the courthouse to keep up with the board, which is most of what a defender on a heavy docket needs the calendar to do.
The whole machine
Ten logins down to two
One subscription stands in for the stack a defense firm usually stitches together, so the practice runs on two things it already trusts: Google Workspace, where the files and matters live, and The IMC Machine, where the matter runs. LawPay and QuickBooks, the money rail, stay where they are, fed by the Machine. Casework, evidence, motions, vouchers, marketing, and events, in one place.
San Antonio and Bexar County. The Machine is built for here first. For another city, county, or region, the build-out is custom and carries its own setup fee.
