Use DispatchDeck from Claude

Look-ups

Needs the Dispatch module. Read-only.

• get_today_schedule — today's jobs and how many drivers and trucks are on each.
• find_jobs — find jobs by customer, title, well, location, PO, job number or date, or by the trucks, trailers and crew on their days (retired units included), with the days each one was on. For example: "where has the D6 been since August?"
• find_crew_and_equipment — your active people, trucks and trailers. No phone numbers or personal details.
• find_past_job_locations — pickup and drop-off spots from jobs you've already run.
• get_started — who you are in DispatchDeck, the tools your login has, what needs approval, and example questions for your modules. Any login.
• get_request_status — whether a change waiting for approval was approved, rejected or expired. Any login.
• list_my_requests — your changes waiting for approval and what happened to each one (approved, rejected, expired), so nothing gets lost when a chat ends. The owner sees everyone's. Any login.

Jobs and crew

Needs the Dispatch module. These change the board.

• create_job — put a new job on the board for a customer that's already in DispatchDeck, with crew and equipment if you want.
• update_job — change a job's title, location or well name.
• set_job_po — set a job's PO.
• add_job_note — add a short line to a job's notes.
• add_job_day — add a date to a job.
• assign_crew — add or take off drivers, helpers, trucks and trailers on one day.
• remove_job_day — ask to remove a day from a job (always needs approval).
• delete_job — ask to delete a job that was never run, with every day on it (always needs approval; it reads the job back first). A job with clock time, tickets, permits, a day already past, or rental equipment on a day can't be deleted from Claude — that's done in DispatchDeck.
• cancel_job_day — mark a day cancelled, the same as Cancel on the board (it stays on the job and can be restored). Days with crew on them, today, past days, and days with a ticket or clock time need approval; days with rental equipment are cancelled in DispatchDeck.

Clock

Needs the Workforce module.

• get_who_is_clocked_in — who's on the clock right now, and anyone who may have forgotten to clock out.
• get_clock_history — one person's clock day: every entry, how it was made, gaps and overlaps. Owners and admins also see who edited each entry. Read-only.
• clock_out_person — ask to clock someone out, and optionally move that shift to the shop or another job (always needs approval). The clock-out time is the moment you asked, so approve it within 15 minutes or ask again. To set any other time, edit the entry in Workforce.
• move_clock_time — ask to move a finished shift to the shop or another job, keeping its times (always needs approval).
• edit_clock_times — ask to change a shift's clock-in or clock-out to times you give it, with a reason (always needs approval). The approval shows the old and new times and any hours the change takes off.
• add_clock_entry — ask to add a finished shift for someone, on the shop or a job, with a reason (always needs approval).
• split_clock_entry — ask to split a shift at a time, putting the earlier part on the shop or another job (always needs approval). No hours are added or taken off.

Billing and revenue

Needs the Billing module unless noted. Read-only.

• get_revenue — revenue for a date range, split by customer, job and category, and by day, week or month when you ask. Same numbers as the BI screen.
• list_invoices — invoices in a date range with paid, unpaid and written-off totals.
• get_ticket_totals — dollar totals of field tickets for a job or date range, and by day, week or month when you ask.
• get_revenue_by_vehicle — revenue per truck and trailer.
• get_revenue_report — the numbers plus your company branding, so Claude can lay out a one-page report.
• get_pending_expenses — expenses still waiting for review, with a total.
• get_ar_aging — open invoices by customer, in 0-30, 31-60, 61-90 and 90+ day buckets counted from the invoice date (the ticket date if there isn't one), not from a due date.
• get_ready_to_invoice — tickets in Ready status that aren't invoiced yet, by customer.
• get_spend and compare_revenue_to_quickbooks — spend and revenue checked against QuickBooks. Billing or BI module. See Use it with QuickBooks.
• get_job_cost — hours, labor cost, direct costs, revenue and margin for one job, customer or project over a date range, with hours per person. Same numbers as the BI Profitability drill-down. Workforce alone gets hours only; Billing or BI adds the dollars, and labor cost and margin also need a module that can see pay rates.

Tickets

Needs the Billing module.

• find_tickets — field tickets for a job or work date: number, status, PO, notes. No dollar amounts.
• create_ticket — ask to add a person's hours for a job day to that day's ticket, starting a draft ticket if there isn't one (always needs approval). If the person is already on the day's ticket, Claude shows you that ticket instead of making a second one.
• update_ticket — ask to change a ticket's notes, work performed, PO, AFE, vendor number, well name, well number or location (always needs approval). Hours, rates, lines and totals can't be changed from Claude.
• find_unpriced_lines — why ticket lines from tied fields (like a Dumps count) are $0 on open tickets, grouped by code and customer.
• preview_invoice — what a ticket's invoice will show: every line shown or hidden and why, and the total, from the same invoice the customer gets.

Price book

Needs the Billing or CRM module.

• find_price_book — a customer's contracts and their line items: description, item code, rate, unit and what each line applies to.
• propose_price_book_changes — ask to change rates, add lines, switch lines off, or show or hide a line on invoices, on one contract, for example from a rate sheet you gave Claude (always needs approval). Each line shows its old and new values before anything changes. Lines are never deleted, and tax and field-ticket settings can't be changed from Claude.
• find_item_codes — your Item Codes and their default rates, and which ticket fields are tied to each, including fields tied to a code that doesn't exist.
• propose_item_code_changes — ask to add Item Codes or change their default rates (always needs approval). Item Code rates apply company-wide, and the approval card says so.
• propose_invoice_visibility — ask to hide line types (for example Field Items) on one customer's invoices (always needs approval). The card shows how many open tickets change and by how much. Needs the Billing module.

Driver compliance due dates

Needs the Compliance or HR module. Read-only.

• get_compliance_due — who is overdue or coming due for a CDL, medical card, MVR, annual driving record review or Clearinghouse annual query, with the date, and which drivers have no date on file. For example: "who's due for anything in the next 30 days?" Dates only: no MVR, Clearinghouse, background check or drug & alcohol results.

Ordering an MVR, background check or Clearinghouse query can't be done through Claude. The driver has to sign a disclosure and authorization first, the report has legal rules about who sees it, and every order is a paid report, so ordering happens in DispatchDeck under Compliance.

IFTA miles by state

Needs the Compliance module. Read-only.

• get_ifta_miles_by_state — an estimate of miles by state for a date range, kept in three labelled columns (permit route miles on file, straight-line miles between job stops, odometer totals) with every gap counted. For example: "how many Montana miles did we run last quarter?" A second check for your IFTA return, not a filing record.

Owner and admin

Owner or admin login only. Read-only.

• audit_hours_vs_tickets — compare recorded hours against tickets to find work that was never billed.