
Restoration CRM
Restoration job management: Ruby can search jobs and read notes, carriers, adjusters, AR aging, margins, and work in progress.
Ask Ruby
Ruby reads from JobSight and grounds her answers in your data. Every connection starts read-only: she surfaces, summarizes, and drafts, and your team takes the action.
Search jobs
Search jobs. Search jobs. Every criterion in the body is optional and they combine with AND; text criteria are case-insensitive partial matches. Use Query for a single search box across the job name, claim, policy and file numbers and the primary/billing customer's name, email, phone and address, or the individual fields (claim number, primary or billing customer, status and so on) to narrow further. Results are ordered newest opened first and returned one page at a time with the total count. The best way to find a job: free-text `search` across job name, claim, policy and file numbers and the customer's name, email, phone and address, or the individual criteria (status, type, location, estimator, open-date and loss-date windows, closed). Returns one page plus totalCount; page through before reporting totals. Each job carries its numeric `id` (what every other jobsight tool takes), status, type, claim number, date of loss and the primary customer.
List jobs
List jobs. List jobs. Plain paged list (an array, no total). Prefer jobsight_search_jobs, which filters and reports a total. (GET /v1/jobs)
Get job
Get a single job by id. Get a single job by id. One job by its numeric id: status, custom status, type, claim and policy numbers, date of loss, deductible, primary and billing customer, estimator and production manager, location, scratchpad. (GET /v1/jobs/{id})
List job notes
List a job's user notes, newest first, the notes people type on the job. List a job's user notes, newest first, the notes people type on the job. The notes people typed on a job, newest first.
List job financial notes
List a job's financial notes, newest first, the separate note list kept against the job's money side, alongside invoicing, payments and commissions. List a job's financial notes, newest first, the separate note list kept against the job's money side, alongside invoicing, payments and commissions. The job's financial notes (invoicing, payments, commissions side), newest first. (GET /v1/jobs/{id}/financialNotes)
Get job master report
Get all Job Master Report rows for jobs opened within a date range. Get all Job Master Report rows for jobs opened within a date range. THE reporting endpoint, one row per job opened between startDate and endDate (inclusive, matched on the job's open date; pass YYYY-MM-DD). Each row carries carrier, adjuster, agent, cause of loss, referral source and marketing rep, job type, status, isOpen/isClosed, estimate, invoice, payment and expense totals, amount due, aging, receivable date, days in progress, days since last activity, and the work-in-progress figures (WIP gross profit, running margin, exposure, percent complete). Use it for AR aging, margins, WIP, referral-source and carrier breakdowns, and for any per-job money figure. Keep windows to a quarter or less on a busy account.
Search customers
Search customers. Search customers. Every criterion in the body is optional and they combine with AND; text criteria are case-insensitive partial matches. Use Query for a single search box across name, company, email, phone and address, or the individual fields to narrow further. ClaimNumber finds the customers on jobs with a matching claim number. Results are ordered by name and returned one page at a time with the total count. Search customers (property owners and billing customers) by free text or by name, company, email, phone, address, or a claim number on one of their jobs. (POST /v1/customers/search)
List customers
List customers. (GET /v1/customers)
Get customer
Get a single customer by id. (GET /v1/customers/{id})
List notes
List user notes, newest first. List user notes, newest first. User notes across record types, newest first. Pass noteType plus referenceId to read one record's notes. (GET /v1/notes)
Get note
Get a single user note by id. (GET /v1/notes/{id})
List work orders
List work orders. List work orders. Work orders sent to subcontractors, with status, dates, total and job id. (GET /v1/workOrders)
Read-only: write access is not offered for JobSight yet.
Grounded answers
Ruby works from your actual JobSight data and cites what she found, so answers reflect your business rather than a stale export.
Reads by default
Every connection starts read-only. Ruby surfaces and drafts while your team takes the action; writes are opt-in per connection, human-approved by default, and always logged.
Managed, secure auth
Connect with one click. Tokens are encrypted and scoped per company; revoke access any time.
Knows restoration
Ruby understands jobs, claims, drying logs, and AR, so JobSight data lands in the right operational context.
Connect JobSight once in Ruby. Ask in the Ruby app, or bring the same secure connection into the assistant your team already uses.
Ruby
Ask in the Ruby app and get an answer grounded in JobSight and the rest of your connected stack.
Claude
Bring the same secure JobSight connection into Claude so it can answer with your live data.
ChatGPT
Use JobSight from ChatGPT with the same per-company, permissioned access Ruby uses.
Do I need developer credentials to connect JobSight?
You paste an API key from your account in Settings > Integrations. There is nothing to build; Ruby stores it encrypted and scoped to your company.
Can Ruby change anything in JobSight?
No. The JobSight connection is read-only. Ruby reads, summarizes, and drafts; a human always makes the change in JobSight.
Is my JobSight data secure?
Credentials are encrypted at rest and access is scoped per company. You can revoke the connection at any time from Settings > Integrations, which immediately cuts Ruby off.
Can I use JobSight alongside my other tools?
Yes. Ruby reasons across every tool you connect at once, so she can tie JobSight to your CRM, accounting, email, and documentation in a single answer.