Test and Publish

Test the current draft while editing, then publish and switch the test to the live version. This separates fast feedback on unpublished changes from verification of the version callers will use.

​

Understand drafts and versions

The auto-save message at the bottom of the editor confirms when the current draft was saved. Auto-save does not create or publish a version. Turning a flow on or off is separate from publishing its current draft. Publishing creates a version and turns the flow on. Turning it off does not delete its draft or published version, and turning it on again does not publish newer draft edits.

​

Recommended release process

When a change depends on phone-specific data or behavior, finish with a phone call: use Place Phone Call for an outbound flow or call the agent’s phone number for an inbound flow.

​

Test focused draft changes

Use focused tests for faster feedback while editing. They do not confirm that the flow can be published or that the complete published path works.

​

Test a block in isolation

Some blocks include a Test section in their configuration panel. Enter safe sample values for the variables used by the block, run the test, and inspect the resolved input and result. Some blocks determine their output variables from the test result. For these blocks, run a successful test before using returned values in downstream blocks, and test again whenever the output structure changes. A block-level test does not run the block’s incoming or outgoing connections.

​

Test from a selected block

Test from here is useful when the changed block is deep inside a long inbound flow.

1. Select the play icon on the live-call block where the test should begin.
2. Choose Voice or Chat.
3. Enter representative values for the available variables the test needs.
4. Select Start test.
5. Continue in the Test Call side panel and verify the downstream route.

The dialog shows only variables that can be available before the selected block. Blank values are not passed into the test. If no earlier values are needed, it displays No variables needed for this block. Test from here applies the draft override to the selected flow. If the route enters another flow, that flow uses its latest published version, or its draft if it has never been published. A successful partial test does not confirm that blocks before the starting point produce the expected values, that alternate routes work, or that the draft has been published. Always complete the normal release process.

​

Review and publish

Open the Flow Checklist and resolve every error on a block reachable from the flow’s entry point. Unconnected blocks parked on the canvas are not part of the executable flow and do not block publishing. Then review the affected routes, variable references, and Flow Settings. Publishing can be unavailable when the flow has block errors, a block is not included in the current plan, your role cannot edit the flow, or a newer collaboration update must be resolved. Select the main Publish button to run a quick AI review. Its findings are advisory: inspect them in the Flow Checklist, ask Ask AI to help, or choose Publish anyway after deciding the draft is ready. If the review is unavailable, publishing continues without it. Deterministic block errors still prevent publishing. Publishing creates a version from the current draft and makes it live. The adjacent menu provides related version actions:

• Save as Version creates a checkpoint without changing the published version.
• Version History opens saved and published versions for review or restoration.

The Publish button is disabled when the current draft matches the published version. After publishing, switch the browser test to Live or run the appropriate phone test so you are checking the version callers will use. See Flow Versions for checkpoints and restoration, and Resolve Remote Flow Updates for resolving newer remote updates before publishing.

​

Test the complete flow

Web Chat and Web Call begin at the agent’s First Flow unless a selected flow or block provides a draft override. Choose the test based on the behavior you need to verify.

​

Web Chat and Web Call

Use Web Chat for a quick functional pass through the flow. Use Web Call when you also need to evaluate the voice, tone, pacing, and interruption behavior. For an inbound flow, select the chat icon on the right side of Test agent to start Web Chat. Select the main area of the same button to start Web Call. Both open in the Test Call tab of the side panel. When started from the Flow Editor, both tests begin with Draft selected and use the current draft of the selected flow. Use the Draft / Live control in the Test Call panel to switch targets; switching restarts the test. Live uses the published version real callers receive. If the flow has never been published, Phonely falls back to its draft. During Web Chat or Web Call, the editor highlights the block currently executing and follows block transitions on the visible draft canvas. If the test hands off to another flow available in the editor, the editor follows that flow too. Following pauses while you pan or zoom manually, and the highlight clears when the test ends. The Ask AI tab can inspect and help change the agent, but it is separate from the tests in Test Call. Ask AI can also run a text-only conversation test against one path in an inbound draft. This is useful for checking a specific expected route, terminal block, or captured variable with a reviewable transcript. Review the individual requirements and whether findings reproduced; an inferred requirement or inconclusive result is not proof that the flow needs repair. External actions are simulated and shown as assumptions, so use Test Call or a controlled live test when phone, audio, publishing, or an integration itself is part of what you need to verify. See Test a draft conversation with Ask AI. Browser-based tests do not always reproduce phone-network data or behavior, such as a real caller number or transfer timing. Use a phone call when the tested behavior depends on that information.

​

Run a phone test

Outbound: Open the outbound flow and select Place Phone Call in the top bar. Enter representative input values, including a destination number you control, then run the test. This uses the latest published version, falling back to the draft only when the flow has never been published. Inbound: From a phone you control, call the number assigned to the agent. Start at the greeting and exercise the affected path.