Fieldproxy

Lists every tech note that says 'follow up', 'revisit', 'call back', 'next week' etc., cross-referenced against whether the SPECIFIC promised action actually happened (invoice on that job, follow-up job created, payment received against that job's invoice, or communication sent about that job). Shows ONLY the promises that were never fulfilled.

Move every open job on one date to another date (e.g. weather day, tech on leave). Optionally limit to one technician. Use for "reschedule all of Friday to Monday", "push tomorrow due to storms". (writes — confirm-gated). Prepares the change and returns a pending_id; nothing is saved until confirm_write.

Drop a proposed action without doing it.

Cancel your follow-up reminder on a thread.

Discard something prepared but not yet applied — a change from propose_write or a message from draft_email/draft_sms.

Pause, resume or delete one of your alerts, or check its current value now (check_now sends nothing).

Pause, resume or delete (unschedule — the saved question stays) one of your scheduled reports, or run it now to see its row count (sends nothing).

Scans customer feedback (satisfaction ratings + written feedback), and both job-level and customer-level notes for churn risk signals. Returns each flagged customer with the exact sentence that flagged them and the full context.

Prepare a comment on a record in the workspace's comments table for that kind of record (e.g. job_notes for jobs — look it up with describe_schema). Mention people by writing @[Name](userid) in the text; each is notified when the comment is applied. Dry-run like propose_write: returns a preview and a pending_id; confirm_write adds it, undo_write removes it.

How a record's fields differ between an earlier time and now (or between two times) — for "what changed on job 42 since Monday?". The table must have history switched on.

Carry out an action another tool proposed (it returned a pending_id): only after the user has seen the proposal and agreed. Runs it once; a second confirm is refused.

Apply a promotion prepared by plan_promotion, after the user has agreed. Tables are added first, then apps are saved as DRAFT versions (publish_app makes them live), automations and agents are saved switched OFF.

Send messages prepared by draft_email or draft_sms. Call ONLY after the user has read the drafts and agreed — these reach real people and can't be recalled. Returns a result per recipient: queued, skipped (opted out, outside allowed hours) or failed.

Apply a change prepared by propose_write (or a custom action). Call ONLY after the user has seen the preview and agreed. Returns the rows changed and an undo_id. Set allow_bulk: true only when the proposal said requires_bulk_confirmation and the user agreed to change that many rows.

Propose an activity alert rule (administrators). kind: bulk_delete, bulk_change, off_hours, field_change, new_actor_table. config — bulk_delete / bulk_change: {threshold (default 25), window_minutes (default 5), tables?}; off_hours: {timezone, start_hour, end_hour, days ([1..5] = Mon–Fri), tables?}; field_change: {table, field, to?, from?}; new_actor_table: {tables?, actor_types?}. It is dry-run against the last day of activity first; confirm_action saves it (it only alerts on what happens next).

Propose a data alert. Three kinds: preset (new_customers, new_leads, new_requests, new_jobs, overdue_invoices, unassigned_jobs, unaccepted_quotes); new_rows — notify when a row is ADDED to a table (optionally matching a condition); threshold — a SELECT returning one number, compared to a threshold. It is test-run now and created only by confirm_action. Tell the user what it watches and where it notifies — not the SQL.

Create a NEW app from complete compiled_data. It is saved as version 1, not live — publish it with publish_app. Read get_widget_docs('app') and ('view') first (platform 'mobile' for a mobile app). Set `type: "web"` for a web app; omit it for a mobile app. Like every save it is checked: lint, every SQL statement against this workspace's tables, and navigation targets.

Propose a new, UNPUBLISHED dashboard (only you see it until you publish it in the app). Created on confirm_action.

Make a sign-off link for one job, for a subcontractor (no login needed): they see the job and can record completion. Returns the URL and how long it lasts.

Make a private copy of this workspace to build and test in. The copy's automations and mailbox sync are off, it can send no email, texts or calls, and it is deleted after 7 days unless extended. IMPORTANT: making the copy disconnects everyone using the LIVE workspace for a few seconds, and a save in progress at that moment can fail — ask the user first. One sandbox at a time, one new sandbox a day. Returns a new MCP key and URL for the copy: add it to the AI client as a second connection.

Propose a new business table. `id`, `created_at` and `updated_at` are added automatically. Name it in plural snake_case (e.g. site_visits). Read get_widget_docs('tenant-schema') for the conventions first. Once confirmed, the table exists and AI tools may read, insert and update it (it is added to Command Center's settings; deleting rows stays off until an administrator turns it on). Nothing changes yet: this returns a proposal (pending_id). Show it to the user; only after they agree, call confirm_action with the pending_id.

Finds customers whose job feedback contains churn-risk language or a low satisfaction rating, and returns the exact sentence that triggered each written-feedback flag (or the rating evidence when no sentence matches).

Propose approving or rejecting a waiting automation step (by approval_id from list_pending_approvals). The automation continues (or stops) right after confirm_action; once approved, its next steps run as written, and they may send email or texts or call outside services.

Delete a sandbox and everything in it, now. The live workspace is not touched. Ask the user first.

Delete a saved filter preset: your own, or (administrators) a shared one.

Propose deleting a service zone for good (administrators); confirm_action does it. Its membership goes with it, and automations watching only this zone stop firing.

Describe the workspace's data tables you may read. With no `tables`, returns every readable table on one line each (name, description, first columns). With `tables`, returns their full column lists, types, foreign keys and notes. Call this before writing SQL.

Propose marking a failure as handled so it leaves the worklist (the run stays failed in history). Pass run_id, or outbox_event_id for a failed record-change event. Applied with confirm_action.

Per-technician capacity in ONE call. mode='availability' (date): booked minutes + job count per tech on that day, lightest first. mode='workload' (from_date,to_date): booked minutes + job count per tech over a range. Use this instead of looping find_jobs per tech.

Prepare one or more emails WITHOUT sending them. They go from your own connected mailbox. Give subject + body_html, or a saved template (+ template_vars). Returns the drafts and a pending_id; nothing is sent until confirm_send. At most 20 per draft and per hour.

Prepare one or more text messages WITHOUT sending them. Returns the drafts and a pending_id; nothing is sent until confirm_send. At most 20 per draft and per hour. Opted-out numbers are skipped at send time.

Road drive time (minutes) and distance (km), one way, from one place to another. Each place is an address or {lat, lng}. Traffic isn't included. Places outside the routing network's coverage are refused with the region named.

Propose deleting a column that was added through MCP (add_column, or any column of a table made with create_table) — with its values; it can't be undone. id, created_at and updated_at stay. Nothing changes yet: this returns a proposal (pending_id). Show it to the user; only after they agree, call confirm_action with the pending_id.

Propose deleting a table that was created through MCP (create_table) — with every row in it; it can't be undone. Tables the workspace already had can't be dropped here, nor one that another table links to (drop that link first). The proposal shows how many rows would go and which screens, automations and tools mention the table. Nothing changes yet: this returns a proposal (pending_id). Show it to the user; only after they agree, call confirm_action with the pending_id.

Change part of one screen without resending it, saved as a new DRAFT exactly like save_draft (same checks; nobody sees it until publish_app). Each op targets a widget by `element_id` and/or a JSON Pointer `path` (relative to that widget when both are given): set (replace a value or add a key), remove, insert (into an array: /children/2 before item 2, /children/- at the end). Find targets with get_view `outline: true`. base_hash is required (from get_view / get_app, or from your previous save — use that one to make several edits in a row; they stack in one draft).

Run one SELECT and save the result as a CSV file (up to 10000 rows); returns a download link. The link is public — anyone who has it can open the file — so share it only where the user intends.

Keep a sandbox longer: push its expiry out by 1–30 days (at most 90 days from when it was made).

Find SENT emails/SMS from the communications log (distinct from drafts awaiting a Send click). Filter by channel and/or customer.

Find service contracts, optionally expiring soon. Returns id (DB pk), customer name, status, end_date.

Find customers / leads by name or company. Returns id (DB pk), name, email, phone, city, lead_status. For geo filters (within N km, by city) use search_freeform.