Fieldproxy

Apply the configured late fee to an overdue invoice (adds late_fee_amount to balance_due, sets late_fee_applied). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

Prepare a schedule change for jobs: technician and/or date and/or start time per job (e.g. the assignments a planner returned). Dry-runs it and returns a before→after preview and a pending_id; nothing changes until confirm_write (allow_bulk over 5 jobs), and undo_write reverses it. At most 200 jobs.

Accounts-receivable aging: unpaid invoices with how many days past due. Use for 'AR aging', 'overdue invoices', 'who owes us'.

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). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

The best order to visit up to 50 stops by road, as a round trip: the stops in visiting order with how long after the start each is reached, and the total drive time and distance. Each stop is {lat, lng} (from a record) or an address (at most 10 addresses a call), with an optional label, id and on-site minutes. Without home_base the trip starts and ends at the first stop. Traffic isn't included. Nothing is saved or assigned — to plan technicians' days, use plan_day_routes.

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.

Close one personal-agent task: mark it done (with what was achieved) or stopped (the user no longer wants it pursued). The agent stops checking it. (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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.

Tick off a job checklist item (sets done=true). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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.

Turn an accepted quote into an invoice, copying its line items across. Use for "convert this quote to an invoice", "invoice quote 842". (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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. Apps are private: never set `is_public`, `visibility: "public"` or `auth_table` — people outside the company get a public form or portal-user logins.

Create a customer with contacts and/or locations in one confirm. params: company_name?, first_name?, email?, phone?, contacts(json array {first_name,last_name?,email?,phone?}), locations(json array {location_name,address_line1?}). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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.

Create a job for a customer with a checklist of tasks in one confirm. params: customer_id, title, service_type?, tasks(json array of task labels). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

Create a purchase order with line items. params: supplier_id?, job_id?, notes?, items(json array {description,quantity,unit_cost}). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

Set up a recurring weekly visit schedule AND generate the first N visit jobs in one confirm. Use for "set up weekly Tuesday maintenance for X", "recurring visits every Friday for a month". params: customer_id, title, weekday(name or 0-6), occurrences(default 4), service_type?, start_date?, technician_userid?. (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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.

Create a service contract with its covered-service line items. params: customer_id, title, start_date, end_date, lines(json array {service_name,description?}). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

Create a labour/sold-hour quote (header + labour line item) in one confirm. Use for rate-based estimates like "quote 6 hours at our sold-hour rate". (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

Create a stock transfer between two technicians with items. params: from_technician_userid, to_technician_userid, notes?, items(json array {item_master_id,quantity_requested}). (writes — confirm-gated). Nothing is saved until confirm_write applies the pending_id it returns when it stages the change.

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).

Finds customer feedback sentences with explicit dissatisfaction or churn signals and returns the customer, related job, rating, and the exact sentence that triggered the flag.

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.