One family of actions
Leads and outreach
Find businesses by type and city, find their contact email, score them, draft the emails, and track who replied.
Leads are found in public sources, checked on their own websites, and written to for your review. Nothing is sent in bulk.
Live, read from this site just now.
The groups in this family, counted just now: — actions
This family among all — actions in the Directory, one square each
Each action is one row in the Directory, sorted into this family by the start of its name.
What it can do
What the actions in this family do, group by group.
Each card is a group of actions that do similar work. The number on each card is how many actions are in that group right now.
Switch to “For your developer” to see the real name of every action.
The real name of every action, read from the Directory just now. Names that contain a supplier’s name are left out of the lists, and still counted.
Find businesses
—Find businesses by type and city from map data, Google Maps listings, the United States clinician registry and web search, and fill in missing websites.
Find contact details
—Visit each business’s website to find a contact email, look deeper when the first pass finds none, and check that the email’s domain can receive mail.
Score and write
—Score each lead for fit, write a first email grounded in the business’s own website, and write the follow-ups. Drafts are saved for review; nothing is sent at this step.
Send
—Send one reviewed email at a time. Sending in bulk is switched off.
Track the pipeline
—Count leads by stage, see sends, opens, clicks and replies, and write the lists to a Google Sheet.
Customer profiles
—Keep one record per person with their contact details, devices, page views and orders; merge two records of the same person; link each record to the messages and tasks about them.
Uses
What a business uses these actions for.
Examples of the work these actions do. They describe uses, not results.
Build a list of businesses of one type in one city, with their websites and contact emails.
Draft a first email and two follow-ups for each, for you to read before anything is sent.
Keep one record per customer, with every message and order linked to it.
How it is run
How any of these actions is run.
The same way as every other action in the Directory: one request, the same permissions, one record.
You don’t have to pick an action yourself. You text what you want; the AI assistant picks the action and runs it within the permissions you set. The result comes back to you, and the request, the result and who asked are written to the Ledger, the record of everything the system has done.
Every action is one row in the Directory, and each row can be run — ways: a text, a link, a spreadsheet cell, an iPhone Shortcut, a command, or an AI model’s request. Every way goes through dispatch: one web address that looks the action up, checks the permissions, runs it on the right computer, sends back the result and writes a Ledger entry. The same action answers every way, under the same limits.
Dispatch takes an HTTP POST (a standard web request) of {"key": "<action name>", "args": {…}}. The same key works over the API (the web address your software calls), MCP (Model Context Protocol, the standard way AI apps connect to outside tools), the command line (CLI), a webhook (an address another program posts to), a spreadsheet cell or a Shortcut. A token (a key or a link) can be limited to exactly the actions you allow; every call, and every refusal, is a Ledger entry.
// One action from this family, as dispatch receives it
{ "key": "…", "args": { … } }Ask for this.
The text below opens ready to send. Add a line about your business, and I’ll reply with what this family of actions would do for it.
Every family
Everything else the system can do.
Every family of actions, with how many actions it has right now.