Interim messages
Use an Interim Message when a block may leave the caller waiting in silence. It tells the caller that Phonely is still working and does not affect routing. Choose how the message is created:
Keep the message short and neutral. It should acknowledge the wait without claiming that the action has already succeeded. For example:
One moment while I check that for you.Enable Post Interim Message Delay to pause briefly after the message before the flow continues. Set a delay of up to 60 seconds.
Error handling
Enable Error Handling when the flow needs separate paths for success and failure. The block replaces its single continuation with two routes:- Success runs when the action completes successfully.
- Error runs when the action fails.
Call outcome tagging
Use Call Outcome Tagging when reaching a block represents a result worth tracking, such asAppointment booked or Needs follow-up. Choose an existing outcome or enter a new one.
Outcome tagging affects reporting, not routing. Use exit conditions, Filter cases, and connections to control what happens next.
If a call reaches multiple tagged blocks, the last tagged block determines its outcome. Tag stable business results rather than routine progress through the flow.
Use Focus blocks by call outcome on the canvas to highlight every block that uses a selected outcome in the current flow.
Troubleshooting
The caller does not hear the interim message
The caller does not hear the interim message
Open Advanced Settings and confirm that Interim Message is enabled. For Fixed, enter the message to play. For Promptable, provide instructions for the message to generate. Then confirm that the call reaches the block.
Success and Error handles are missing
Success and Error handles are missing
Open Advanced Settings and enable Error Handling. The block updates automatically to show Success and Error source handles. Connect each handle to the appropriate next block.
The call has an unexpected outcome
The call has an unexpected outcome
Use Outcome Focus to find the configured blocks, then review the call path to see which ones ran. The last tagged block reached determines the outcome.

