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/Zenoti
Review Zenoti 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 jobs by campaign output from fields such as Opportunity or job ID, Pipeline stage, Booked value.
Review
Zenoti record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked jobs by campaign before the result is used in dashboards, Ask Data, or reports.
Revenue by service + Close rate by source
Booked work, jobs, deals, or opportunities: Normalized. Available to dashboard and Ask Data
Connection and sync stay visible before client reporting.
Revenue proof lens
Zenoti 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 | Zenoti is scoped to use Opportunity or job ID, Pipeline stage, Booked value, Owner from records such as opportunities or jobs, pipeline stages, booked value 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 jobs by campaign as booked jobs by campaign output, with sample evidence such as Booked work, jobs, deals, or opportunities: Normalized; Invoices, payments, and collected revenue: Normalized. |
| User decision | The user should verify during setup how does opportunities or jobs affect booked revenue without jumping into the raw provider account. |
| Safe fallback | If Zenoti 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.
Zenoti appears as booked jobs by campaign output with rows such as Booked work, jobs, deals, or opportunities: Normalized, plus source-field context before the card is trusted.
Zenoti record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked jobs by campaign before the card can be treated as reportable evidence.A user can ask how does opportunities or jobs affect booked revenue and get a cited answer only when Zenoti records are scoped, current, and matched to downstream evidence.
If Zenoti 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 Zenoti 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.Zenoti 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 jobs by campaign can appear in dashboard cards, cited Ask Data answers, and report sections after setup, permissions, and first synced records are reviewed.
Zenoti record to Booked work, jobs, deals, or opportunities to Scoped client workspace to Booked jobs by campaign before client-facing output can use Zenoti.
Zenoti 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 Zenoti 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
Zenoti 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 |
|---|---|---|
| Opportunities or jobs | Booked jobs by campaign | How does opportunities or jobs affect booked revenue? |
| Pipeline stages | Revenue by service | How does pipeline stages affect booked revenue? |
| Booked value | Close rate by source | How does booked value affect booked revenue? |
| Owner | Booked jobs by campaign | How does opportunities or jobs affect booked revenue? |
Zenoti records show up as booked jobs by campaign so buyers can see what the source changed downstream.
How does opportunities or jobs affect booked revenue?
How does pipeline stages affect booked revenue?
How does booked value affect booked revenue?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
Zenoti 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 jobs by campaign appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If Zenoti 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 Housecall Pro 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 opportunities or jobs, pipeline stages, booked value, owner, close date, service type from Zenoti. The page also names the fields used for visible proof, including Opportunity or job ID, Pipeline stage, Booked value, Owner, so buyers can see which source records support the dashboard output.
Zenoti 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 jobs by campaign.
The sample revenue view models Zenoti as booked jobs by campaign output. Example rows include Booked work, jobs, deals, or opportunities: Normalized; Invoices, payments, and collected revenue: Normalized, with the exact output depending on the client's connected sources and synced records.
If Zenoti 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.