Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
Integrations/Jobber
Review Jobber setup, expected fields, and validation gates before its records are treated as reporting evidence.
Data brought into SIRJ
Review the signals SIRJ is scoped to map, which records can support reporting, and what setup has to prove before the source contributes to proof.
Dashboard proof path
Each integration page shows what comes in, what dashboard view it can unlock, and what has to be checked before the output becomes client-ready proof.
Connect
Sync: Every 3 hours. During setup, permissions and client-resource scope have to be confirmed first.
Graph
SIRJ previews booked job value from fields such as Clients, Jobs, Quotes.
Review
Jobber record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked work by service before the result is used in dashboards, Ask Data, or reports.
Revenue by service + Close rate by source
Water heater: $18.9k. 5 jobs
Connection and sync stay visible before client reporting.
Revenue proof lens
Jobber matters in SIRJ when its source records can be matched to downstream revenue evidence; otherwise the page shows the missing proof path instead of presenting the connector as attribution-ready.
| Proof question | How SIRJ handles it |
|---|---|
| Source record SIRJ reads | Jobber is scoped to use Clients, Jobs, Quotes, Invoices from records such as clients, jobs, quotes before SIRJ lets the source influence reporting. |
| Revenue match target | The important question is whether those records can be matched to campaign, call, form, payment, and client records that explain where booked work came from inside the same client workspace. |
| Dashboard result | The visible output is booked work by service as booked job value, with sample evidence such as Water heater: $18.9k; Drain cleaning: $11.4k. |
| User decision | The user should verify during setup which campaigns booked the highest-value jobs without jumping into the raw provider account. |
| Safe fallback | If Jobber is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting booked jobs by campaign as proven. |
Unlocked surfaces
A connector should not disappear into a shared data pool. These are the visible places where the source can affect decisions, reports, answers, and review work.
Jobber appears as booked job value with rows such as Water heater: $18.9k, plus source-field context before the card is trusted.
Jobber record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked work by service before the card can be treated as reportable evidence.A user can ask which campaigns booked the highest-value jobs and get a cited answer only when Jobber records are scoped, current, and matched to downstream evidence.
If Jobber is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting booked jobs by campaign as proven. The assistant should return the missing proof path instead of guessing when the source cannot support the answer.The weekly report can summarize revenue by service from Jobber alongside the rest of the client stack, with source rows kept close to the recommendation.
Report output should stay held for review when required records are stale, missing, or unable to prove the visible revenue claim.Jobber can create a visible setup, stale-source, or missing-proof state so operators know whether to connect, retry, review, or explain the source before the client sees it.
The connector state has to remain visible in the client workspace, alert inbox, and review path before reports or AI-generated copy rely on it.Reporting readiness
This keeps connector pages honest: a source can be connected without being safe for client-facing revenue proof.
Booked work by service can appear in dashboard cards, cited Ask Data answers, and report sections after setup, permissions, and first synced records are reviewed.
Jobber record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked work by service before client-facing output can use Jobber.
Jobber stays visible as a setup, stale-source, missing-field, or review-required state when a record path is incomplete.
Operators should confirm source scope, latest sync, selected resources, and required fields before approving the output.
If Jobber is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting booked jobs by campaign as proven.
Dashboards, Ask Data answers, weekly reports, and exports should name the missing proof path instead of smoothing over the gap.
How users see it
Jobber is on the launch track, so this page shows the setup path, expected records, and proof gates before its data becomes dashboard evidence.
| Imported signal | Visible surface | Buyer question answered |
|---|---|---|
| Clients | Booked jobs by campaign | Which campaigns booked the highest-value jobs? |
| Jobs | Revenue by service | Which services convert best from paid leads? |
| Quotes | Close rate by source | What work is booked but not yet paid? |
| Invoices | Booked jobs by campaign | Which campaigns booked the highest-value jobs? |
Jobber data lets SIRJ show which services and jobs are actually created from connected demand sources.
Which campaigns booked the highest-value jobs?
Which services convert best from paid leads?
What work is booked but not yet paid?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
Jobber must complete setup, be scoped to the right client workspace, and sync on its expected cadence before its records can affect a dashboard.
Booked work, jobs, deals, or opportunities, Invoices, payments, and collected revenue become typed revenue-path events, which keeps source-specific payloads from turning into loose reporting copy.
Records have to stay inside the active account and client workspace before they can influence attribution, reports, exports, or Ask Data answers.
Booked work by service appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If Jobber is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting booked jobs by campaign as proven.
Lineage route
Related connectors
Review Housecall Pro setup, expected fields, and validation gates before its records are treated as reporting evidence.
OperationsReview Zenoti setup, expected fields, and validation gates before its records are treated as reporting evidence.
OperationsReview the planned Toast data path, expected fields, and validation gates before it becomes a live connector.
Integration FAQ
Answers stay tied to imported fields, visible dashboard output, and what SIRJ refuses to claim when source evidence is missing.
SIRJ is scoped to map clients, jobs, quotes, invoices, line items, service types from Jobber. The page also names the fields used for visible proof, including Clients, Jobs, Quotes, Invoices, so buyers can see which source records support the dashboard output.
Jobber is expected to support this by giving SIRJ a source-specific part of the revenue path, then matching it to the rest of the connected client stack before the result appears as booked work by service.
The sample revenue view models Jobber as booked job value. Example rows include Jobs booked: 31; Largest invoice: $3,975, with the exact output depending on the client's connected sources and synced records.
If Jobber is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting booked jobs by campaign as proven.
Ready when the numbers need to hold up
Use the workspace intent to begin setup, then confirm permissions, synced records, and validation gates before revenue claims depend on it.