For Support

Short version

This PR has no effect on the live Dentolize product, so it shouldn't generate any customer tickets. It only affects people opening pull requests against the Dentolize repo — i.e., the engineering team, and occasionally a partner/contractor with repo access.

If someone on the engineering side asks you (or asks in a dev-support

channel) about this

The most likely question, and the answer:

"My PR sandbox isn't picking up my whatsapp: true change" — Check whether the description was actually saved with the edit (the workflow only reacts to edited events where github.event.changes.body is non-null, gate-and-deploy-flow.md), and whether the Sandbox block's content actually changed — retitling the PR or editing other paragraphs in the description does not trigger a redeploy by design.

"Where do I even put these settings?" — Any new PR already starts with a ## 🧪 Sandbox section pre-filled in the description box; just edit the YAML values in place. No separate config file, no CLI flag.

"I deleted the whole block by accident, did I break something?" — No. Deleting the block is explicitly supported and just reverts to defaults (.github/PULL_REQUEST_TEMPLATE.md:13, "Delete the whole block to keep the defaults").

"Why does my sandbox have IS_SANDBOX=true I didn't ask for?" — That's the template's own default env entry, not something they configured. See sandbox-settings-block.md for why, and note it currently isn't read by any application code — so it shouldn't be causing any visible behavior difference to troubleshoot.

"The block is invalid YAML / cron didn't turn off" — the extraction and YAML→JSON conversion are awk + yq on the CI runner (gate-and-deploy-flow.md); malformed YAML falls back to {} (all defaults) rather than failing the job, so a typo silently loses the customization rather than erroring loudly. Check the "🧪 parsed sandbox settings" collapsible group in the deploy job's log to see what actually got parsed.

What this does not change

• No clinic-facing behavior, ever, under any value of these settings.
• No production infrastructure — this only governs ephemeral per-PR preview

environments.