What gets created
The documented creation action prepares one disabled Close Forge deployment and an unpublished two-touch workflow for unsold estimates. Supported source choices come from the authorized connected Housecall Pro or ServiceTitan accounts returned for your workspace.
Creating this draft does not activate a campaign, contact customers, import historical estimates or attest to consent. The initial order of work is account selection → explicit channel and copy → reviewed draft creation → separate readiness, publication and activation decisions.
Gather the inputs
- The exact CRM account and a clear deployment name.
- SMS or email, not an ambiguous “follow-up message.”
- Approved first and second message wording; include email subjects when applicable.
- The intended timing and the business context behind it.
- Who will confirm consent and sender readiness before anything is activated.
Prepare a bounded first workflow
Show the supported CRM accounts for a new Close Forge draft. After I choose the account, prepare a disabled two-touch email workflow called Estimate check-in. Use the message copy I provide next. Do not publish, activate, enroll historical estimates or send messages.
Select the correct account from the returned list. Give Work the actual copy before asking it to prepare creation. For timing, state an initial delay and the follow-up interval clearly. Immediate followed by next-day is supported as a timing description, but normal quiet hours and stop rules still apply.
Review the proposal
- Check the CRM account, deployment name, channel, both messages and timing.
- Verify that the new deployment is disabled and the workflow unpublished.
- Read the consent and sender setup warnings. A draft is not evidence that recipients may be contacted.
- Approve the exact creation action, then open the returned deployment and verify its disabled/draft state.
Move toward activation deliberately
Use the Close Forge lifecycle guide to inspect settings and versions. Configure supported settings while the deployment is paused; confirm recipient consent explicitly rather than allowing an assumption. Provision and verify senders in the secure owning setup flow.
Workflow publication and deployment resume are separate requests and approvals. Publishing a workflow while paused is not a send. Resuming permits future eligible intake under the normal gates; it does not replay all old estimates or recreate stopped messages.
When creation is unavailable
Check app access, lifecycle permission and the connected CRM account. A disconnected or changed account should be reviewed again, not replaced silently. If the draft-creation capability is not enabled, create the deployment in Close Forge itself.
After an interrupted request, inspect the saved operation and deployment list before making another creation request. The goal is one verified draft, not several similarly named copies whose status is unclear.