All businesses/Realtors
A buyer who asks about a listing at 9:41 PM gets a reply from your number within a minute and books a Saturday showing. Open-house visitors get follow-up texts, and every closing ends with a review request.
Live, read from this site just now.
An illustration. The business and the people are made up.
Mon 9:41 PMA buyer asks about a listing at 9:41 PM while you are at dinner.Example week
Ortiz Realty is a made-up realtor. 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.
9:41 PMPart of the system: Dispatch
The inquiry arrives by email from a listing website. The AI assistant reads it and replies from your number within a minute, and the buyer books a showing for Saturday at 11:00.
The service this usesFor realtorsWritten to the LedgerMon 9:41 PM
listing-site lead · email read · reply sent from your number · showing booked Sat 11:00
········→········matches
10:15 AMPart of the system: Where actions run
Instead of reaching voicemail, the caller gets a text from your number within a minute asking how you can help. Their reply waits for you in the same conversation.
The service this usesiMessage lineWritten to the LedgerTue 10:15 AM
missed call 10:15 AM · text sent from your number · reply waiting for you
········→········matches
8:00 AMPart of the system: The Directory
The system sends each of them a follow-up text on day 2, and again on day 5 and day 10. The texts to a person stop as soon as that person replies.
The service this usesFor realtorsWritten to the LedgerWed 8:00 AM
open house · 14 sign-ins · follow-up day 2 · stops when each person replies
········→········matches
4:30 PMPart of the system: Permissions and limits
They get one text from you with a review link. A five-star answer goes to Google. Anything under four stars comes to you first and is not posted.
The service this usesFor realtorsWritten to the LedgerThu 4:30 PM
review asked at closing · 5 stars · Google review link sent
········→········matches
5:00 PMPart of the system: Where actions run
The text promised on Monday goes out on Friday from your number, in the same conversation, with where to park and when the lockbox opens.
The service this usesFor realtorsWritten to the LedgerFri 5:00 PM
reminder sent · showing Sat 11:00 · parking and lockbox details
········→········matches
9:00 AMPart of the system: The Directory
The system sends them a short note from your number with a market update about their own street, written in your style and within the permissions you set.
The service this usesFor realtorsWritten to the LedgerSat 9:00 AM
past client · closing anniversary · note sent from your number
········→········matches
4:00 PMPart of the system: Permissions and limits
The AI assistant answers from your calendar, the only thing it is allowed to read for this question, and lists the showings booked.
The service this usesFor realtorsWritten to the LedgerSun 4:00 PM
reply to seller · read: calendar, showings only
········→········matches
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
Services used
Each card is one service. A service is a set of actions from the Directory (the table of every action the system can run), set up for your business. The days on each card are the moments above that use it. The number on each card is how many actions in the Directory that service includes.
For realtors
Portal leads answered from your own number in under a minute, and the review asked at closing.
iMessage line
Customers text your existing business number and get iMessage replies (blue bubbles on iPhones) from an AI assistant that follows the permissions you set.
Meta ads
What each step of an ad costs and returns — impressions, clicks, leads, booked jobs — and which step the system improves.
Creative
AI makes the images and videos, a person chooses them, and they are uploaded to your ad account switched off until you approve.
Permissions
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.
What the AI assistant may read, what it may do, and whom it may reply to. Anything not listed here is switched off.
The AI assistant books showings and answers from your calendar. It does not negotiate, discuss commission or give legal advice; those conversations are passed to you.
Each card shows an action a realtor would use, the limit on it, and what came back, as it appears in the Ledger. A refused request is recorded the same way.
sent from your number
invite sent
uploaded, paused
2 of the 7 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 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 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.
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.
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.
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.
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.
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.
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.
Choose your setup
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.
Other businesses
The same system, with different actions switched on.
Tell me what your realtor 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 · Realtors
Your setup · Realtors
For realtors · iMessage line · Your own number · Customers and leads