Skip to Content
Node ReferenceEnd

End

Complete the call with a farewell message and gracefully terminate the conversation.

Overview

The End node is the terminal point of your call flow. When a conversation reaches this node, it speaks a farewell message to the caller and then gracefully ends the call. Every complete call flow should have at least one End node to ensure calls are properly concluded rather than abruptly disconnected.

Use the End node when:

  • A caller’s question has been fully answered
  • A support request has been resolved
  • The caller indicates they’re finished
  • A transfer has failed and no other options exist

Configuration

Title

Type: string Required: No Default: “End”

A descriptive name for this node that appears on the canvas. Use titles like “Goodbye”, “Call Complete”, or “Transfer Failed End” to identify different end points in your flow.

End Message

Type: string Required: No Default: None

The farewell message spoken to the caller before the call ends. This message is converted to speech using your configured voice settings.

Example:

Thank you for calling. Have a great day!

How It Works

  1. Flow reaches the End node - When the conversation naturally progresses to this point or is routed here by a Query Processor
  2. Farewell message plays - The configured end message is converted to speech and played to the caller
  3. Call terminates gracefully - The phone call is properly disconnected, and the call session is marked as complete

Connection Rules

DirectionAllowedNotes
InputsMultipleCan receive connections from any node - Query Processors, TTS Responses, failed Transfers, etc.
Outputs0End node is terminal - no outgoing connections allowed

The End node is a terminal node, meaning it cannot connect to any other nodes. It represents the final step in a conversation path. Your flow can have multiple End nodes for different scenarios (e.g., successful resolution, transfer failure, caller hangup).

Examples

Basic Example: Simple Goodbye

A straightforward end to your call flow after handling a caller’s question.

Configuration:

  • Title: Goodbye
  • End Message: Thanks for calling! Goodbye.

Flow pattern:

Start --> Query Processor --> End

Advanced Example: Personalized Farewell with Summary

A more detailed farewell that acknowledges the interaction and invites the caller back.

Configuration:

  • Title: Call Complete
  • End Message: Thank you for contacting Acme Support today. If you have any other questions, don't hesitate to call back. Have a wonderful day!

Example: Transfer Fallback End

When a call transfer fails, route to a dedicated End node with an appropriate message.

Configuration:

  • Title: Transfer Failed
  • End Message: I apologize, but I'm unable to connect you to an agent right now. Please try calling back during business hours, Monday through Friday, 9 AM to 5 PM. Thank you for your patience.

Flow pattern:

Query Processor --> Transfer --> (on failure) --> End

Best Practices

  • Keep it brief - Aim for 5-15 seconds (30-80 characters). The caller is ready to end the call.

  • Thank the caller - Always express gratitude for their time: “Thank you for calling…”

  • Be positive - End on a pleasant note: “Have a great day!” or “We appreciate your business!”

  • Match your brand voice - If your company is formal, keep it professional. If casual, be friendly.

  • Mention follow-up when relevant - If you’re sending information: “You’ll receive an email confirmation shortly.”

  • Use multiple End nodes - Create different End nodes for different scenarios (successful resolution, transfer failure, after-hours, etc.) with tailored messages.

Common Issues

”Message gets cut off”

Solution: Your end message may be too long. The call terminates shortly after the message finishes playing. Keep messages under 100 characters for reliable playback. Avoid asking questions or expecting responses in your end message.

”Call ends abruptly without message”

Solution: Ensure the End Message field is not empty. If left blank, the call will end immediately without any farewell. Always configure a brief goodbye message.

”Caller hangs up before message finishes”

Solution: This is expected behavior - callers may disconnect at any time. Keep your end message brief so the important part (the thank you) is said first. Put the most important content at the beginning of your message.

”End node is unreachable”

Solution: Check that your End node has at least one incoming connection. Use the Node Info section in the properties panel to verify connections. An End node without connections will never be reached during a call.

  • Start - The entry point of your flow; End is the opposite terminal point
  • Query Processor - Often routes to End after successfully answering a question
  • Transfer - Failed transfers commonly route to End as a fallback
  • TTS Response - Can precede End for multi-step goodbyes
  • Conditional Transfer - Routes to End when no transfer conditions match
Last updated on
StartFAQ Loader