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/Housecall Pro
Review Housecall Pro 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 service value by status from fields such as Jobs, Customers, Estimates.
Review
Housecall Pro record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Service work revenue path before the result is used in dashboards, Ask Data, or reports.
Revenue by service + Close rate by source
Completed jobs: $51.7k. 44 jobs
Connection and sync stay visible before client reporting.
Revenue proof lens
Housecall Pro 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 | Housecall Pro is scoped to use Jobs, Customers, Estimates, Invoices from records such as jobs, customers, estimates 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 service work revenue path as service value by status, with sample evidence such as Completed jobs: $51.7k; Open estimates: $9.6k. |
| User decision | The user should verify during setup which services are driving booked revenue without jumping into the raw provider account. |
| Safe fallback | If Housecall Pro 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.
Housecall Pro appears as service value by status with rows such as Completed jobs: $51.7k, plus source-field context before the card is trusted.
Housecall Pro record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Service work revenue path before the card can be treated as reportable evidence.A user can ask which services are driving booked revenue and get a cited answer only when Housecall Pro records are scoped, current, and matched to downstream evidence.
If Housecall Pro 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 Housecall Pro 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.Housecall Pro 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.
Service work revenue path can appear in dashboard cards, cited Ask Data answers, and report sections after setup, permissions, and first synced records are reviewed.
Housecall Pro record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Service work revenue path before client-facing output can use Housecall Pro.
Housecall Pro 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 Housecall Pro 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
Housecall Pro 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 |
|---|---|---|
| Jobs | Booked jobs by campaign | Which services are driving booked revenue? |
| Customers | Revenue by service | Which campaigns create high-value jobs? |
| Estimates | Close rate by source | Where does the job pipeline stall? |
| Invoices | Booked jobs by campaign | Which services are driving booked revenue? |
Housecall Pro pages show how scheduled service work moves from estimate to invoice to payment.
Which services are driving booked revenue?
Which campaigns create high-value jobs?
Where does the job pipeline stall?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
Housecall Pro 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.
Service work revenue path appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If Housecall Pro 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 Jobber 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 jobs, customers, estimates, invoices, payments, technicians from Housecall Pro. The page also names the fields used for visible proof, including Jobs, Customers, Estimates, Invoices, so buyers can see which source records support the dashboard output.
Housecall Pro 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 service work revenue path.
The sample revenue view models Housecall Pro as service value by status. Example rows include Booked jobs: 44; Top service: HVAC repair, with the exact output depending on the client's connected sources and synced records.
If Housecall Pro 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.