What this workflow reads
Work can read saved Site Spark settings for an authorized deployment, including overview, booking, chat, theme, CRM and embed sections. It can also read bounded lists such as service cities and ZIP codes, booking trades/issues, callback windows, chat topics and allowed origins.
These are configuration reads. They do not change mappings or settings, provision senders, validate live CRM resources or certify how the widget renders on a customer website. The read explicitly distinguishes saved connection state from provider, messaging and public-rendering readiness.
Inspect one section at a time
- Open the intended Site Spark deployment. Confirm its name and workspace.
- Ask for the saved section you need, such as booking or CRM.
- For long lists, request continuation of the same version until the relevant items are complete.
- Use the returned app link to inspect the same settings in Site Spark.
Try these requests
Read the saved booking settings for this Site Spark deployment. Explain the service selection and customer next step. Identify which readiness checks were not performed; do not change anything.
List the configured service cities and ZIP codes for this deployment. Include any continuation or truncation notice, and keep the list bound to the same saved version.
Turn observations into a safe handoff
Suppose the read shows an outdated callback window. Ask Work to describe the intended replacement and the affected setting, then make the supported edit in Site Spark unless Work exposes an explicit authorized action for it. A copy change to a smart form is not a change to the booking widget, chat policy or CRM configuration.
Before changing routing or eligibility, record the current selection, confirm the provider account and review the full customer journey. Use the owning app’s preview and testing controls. Check receipt in the destination rather than assuming that displaying a form means an inquiry was booked.
What to do with an access or version warning
An archived, unavailable or mismatched deployment may be rejected. A CRM account mismatch requires reviewing that relationship in Site Spark; do not ask Work to substitute another account automatically. A changed version means rereading the first page before continuing configuration lists.
If a read succeeds but the live experience fails, report both facts: “The saved settings loaded; the public booking test did not complete.” Include the deployment and non-sensitive error information. That is more useful than marking the whole connection healthy from a settings read alone.