The system
How the system worksThe DirectoryDispatchThe LedgerAI modelsAI agentsYour installationThe appThe research libraryWhat changes for your businessUse it from your softwareEverything it can do
Messaging
iMessageWhatsApp
Ads and leads
AdsCreativeLeads
Devices
Devices
Industries
RealtorsRestaurantsHome services
Explore
How it worksPermissions and limitsCompareSet upQuestionsText me

All businesses/Law firms

Law firms

An evening inquiry gets a reply from the firm’s number and a booked consultation. The court’s website is read in a browser, and a request for legal advice is passed to you and written to the Ledger.

  • 8moments in the example week, each written to the Ledger
  • 3services this example uses
  • —actions in the Directory, the same for every business

Live, read from this site just now.

An illustration. The business and the people are made up.

Mon 8:10 PMSomeone texts the firm at 8:10 PM about a legal problem.

Example week

One week at Reyes & Park, day by day

Reyes & Park is a made-up law firm. For each moment, Monday to Sunday: what happened, what the system did, which service it used, and the entry it wrote to the Ledger, the system’s record of every request and response.

An illustration. The business and the people are made up.

Monday1 moment

8:10 PMPart of the system: Permissions and limits

Someone texts the firm at 8:10 PM about a legal problem.

The AI assistant replies from the firm’s number, says it is an assistant, asks what happened and when, and books a consultation in the hours you made available. It gives no legal advice.

The service this usesiMessage line

Written to the LedgerMon 8:10 PM

inquiry 8:10 PM · reply from the firm’s number · consultation booked Wed 10:00

········→········matches

Tuesday2 moments

5:00 PMPart of the system: Where actions run

Tomorrow’s consultation gets a confirmation.

The client gets the time, the address and what to bring, from the firm’s number, in the same conversation.

The service this usesiMessage line

Written to the LedgerTue 5:00 PM

confirmation sent · consultation Wed 10:00 · address and what to bring

········→········matches

Wednesday1 moment

3:00 PMPart of the system: Where actions run

The court’s website has no way for software to connect to it.

A web browser signed in to the firm’s account opens the court portal, reads it the way a paralegal would, and saves a screenshot of what it read.

The service this usesAutomation on your devices

Written to the LedgerWed 3:00 PM

court portal · read in a browser signed in as the firm · screenshot saved

········→········matches

Thursday1 moment
Friday1 moment

4:00 PMPart of the system: Dispatch

A client abroad sends a message on WhatsApp.

Because the client wrote first, the AI assistant replies in their language, Spanish. Anything about their case is passed to you.

The service this usesWhatsApp Business

Written to the LedgerFri 4:00 PM

WhatsApp · client wrote first · replied in Spanish · case question passed to you

········→········matches

Saturday1 moment
Sunday1 moment

7:00 PMPart of the system: The Ledger

A client texts: “Should I sign it?”

Legal advice is outside the assistant’s permissions, so it says it cannot advise and passes the conversation to you. The refusal is written to the Ledger like every other action.

No extra service · included in every setupThe Ledger

Written to the LedgerSun 7:00 PM

refused · legal advice · conversation passed to you

········→········matches

Each Ledger entry carries a fingerprint of the entry before it.

The two codes under each entry above are the first characters of real SHA-256 fingerprints, calculated in your browser: the fingerprint of the entry before, then this entry’s own, which is calculated from its text plus the one before. Press “Change one word” to edit Thursday’s entry, then “Check every entry”: the check fails at that entry, because its text no longer matches its fingerprint. This is how a changed Ledger entry is detected.

Calculating fingerprints

Permissions

What the AI assistant may read, do and reply to

For each action you decide what information the AI assistant may read, what it may do, whom it may reply to, and limits such as an amount or a time window. A request outside the limits is refused, and the refusal is written to the Ledger.

Permissions switched on for a law firm

What the AI assistant may read, what it may do, and whom it may reply to. Anything not listed here is switched off.

What it may read

CalendarWhat is next, and which hours are open
MessagesThe threads you choose, not all of them
MailSearch and read, tracked sends
FilesThe folders you point it at

What it may do

ReplyIn your writing style, within your permissions
BookOnly into the hours you opened
Missed call text-backFrom your number, within a minute
Invoice and refundSend, finalize, refund within a limit

Whom it may reply to

LeadsTold it is an AI assistant when they ask; passed to a person when they ask for one
Customers
YouAnswers you using the same information
All permissions

The assistant never gives legal advice.

When a client asks “Should I sign it?”, the AI assistant says it cannot advise and passes the conversation to you. The refusal is written to the Ledger like every other action.

Examples of actions with limits

Each card shows an action a law firm would use, the limit on it, and what came back, as it appears in the Ledger. A refused request is recorded the same way.

Text back the missed call
  • read: Messages, this handle only
  • in your writing style, using only prices you approved

sent from your number

Book the 2:30
  • write: Calendar, only hours you opened

invite sent

Moments this week where a permission or limit applied

3 of the 8 moments above were decided by a permission or a limit. Each one is an entry in the Ledger, including any refusal.

How the system carries out the week

The four parts of the system behind every moment

The Directory is a table of every action the system can run. Dispatch is one web address that runs any of those actions. The Ledger records every request and response. The actions run on real computers and phones. Choose how much detail you want: for you, for your team or for your developer.

Numbers are live, read from this site just now.

The DirectoryEvery action the system can run

A table with one row for each action the system can run.

The Directory is a table. Each row is one thing the system can do for your business: send a text from your number, book a slot in your calendar, create an ad, read a web page, take a screenshot of your Mac. If an action is not in the table, the system cannot do it.

Each row stores everything needed to run that action: where it runs, what inputs it needs, what it returns, and every way to call it. Changing a setting is typing in a cell. Files added to the system’s folder are added to the table automatically.

One row per action. Each row has one column per way of calling it, and each of those cells holds the complete request (method, address, headers and body) that runs it, followed by the full response from the last run.

Why it matters to your law firm

Every action your business can use is listed in one place, with where it runs and what it needs. You can see what the system is able to do before it does anything: if an action is not in the Directory, it cannot run.

—actions in the Directory

Actions in the Directory for each service this example uses

  • iMessage108
  • WhatsApp7
  • Devices146
DispatchOne address that runs any action

One web address runs any action in the Directory.

Dispatch is a single web address. You, your staff, a spreadsheet, an iPhone Shortcut or an AI model send it the name of an action and its inputs. It finds the action in the Directory, checks your permissions, runs it on the right computer, sends back the result, and writes an entry in the Ledger.

Because every request goes through the same address, the same permissions apply whether a request comes from a text message, a link, a spreadsheet cell, a Shortcut, the command line or an AI model, and every request is recorded the same way. One action can be switched off in one place.

Every action is invoked as an HTTP POST of {"key": "<action name>", "args": {…}}. REST, MCP, spreadsheet formulas, text tags and webhooks are different ways of making that same request. Actions run on Cloudflare servers, a Mac, an iPhone, a browser, a virtual machine or a phone.

Why it matters to your law firm

One connection instead of a separate integration for every tool. Your staff, your AI models, your spreadsheets and your phone all use the same actions under the same permissions. Changing AI model or vendor does not mean rebuilding, and any action can be switched off in one place.

—ways to call each action
A text messageA web linkA spreadsheet cellAn iPhone ShortcutA command typed in a terminalAn AI model’s tool call
The LedgerA record of every request and response

A table with one row for every request and response the system has handled.

The Ledger is a record of everything the system does: every message sent and received, every action run, every change, every AI model’s answer, and every request that was refused. Nothing in it is overwritten. To find out what happened, you read it.

Each entry stores the full request and the full response. Each entry also stores a fingerprint of the entry before it, so if anyone changes an entry later, the change shows up. Refused requests are recorded the same way as completed ones.

Every payload in or out is a Ledger row. Each action appends one row containing a SHA-256 hash of the previous row; nothing is updated in place. An action counts as working only when the declared surface itself ran and five things are stored for that run: why it ran, the exact request written before it ran, the confirmation, the exact response, and the record.

Why it matters to your law firm

You can see exactly what was sent, to whom, when, and by which AI model, and settle a dispute from the record instead of from memory. You can check what an AI did before trusting it with more, and compare AI models on cost and results. Refused requests are recorded too.

—entries in the Ledger
Where actions runThe computers that do the work

Actions run on real computers and phones.

Depending on the action, the work happens on Cloudflare’s servers (always on), on your Mac, on your iPhone, in a web browser signed in to your accounts, or on Android phones rented in a data centre for apps that only run on a phone.

A website or app with no way to connect to it can be recorded once — the steps a person clicks — and saved as a new action in the Directory that can be run again at any time. The browser uses your own signed-in sessions, not fake accounts.

Executors: Cloudflare Workers and containers, a Mac bridge program, iPhone Shortcuts and App Intents, persistent browser profiles, cloud Android phones and Mac virtual machines. Recording steps and compiling them turns any website into a Directory row callable through dispatch.

Computers and phones that can run actions

  • Cloudflare’s servers, always on
  • Your Mac, through a small program on it
  • Your iPhone, through Apple Shortcuts
  • A browser signed in to your accounts
  • Android phones rented in a data centre
  • Mac virtual machines

Choose your setup

Choose what to set up for your law firm

Pick the services and which phone number to use. The button opens a text message to me with your choices already written in, so my reply can be about your setup.

Your setup

    Text this setup
    1 / 3Which services do you want first?

    Choose any.

    2 / 3Which number?

    Choose one.

    3 / 3Who may it answer?

    Choose one.

    Text me.

    Tell me what your law firm misses in a week: calls, follow-ups, reviews. I will reply with which moment above to set up first, and the entry it would write to the Ledger.

    Your setup · Law firms

    Text this setup

    Your setup · Law firms

    iMessage line · WhatsApp Business · Your own number · Customers and leads

    Text this setup