The Invokable Destination Container is an entry point in Policy Builder for calls that are started by an automated process rather than by an inbound dialled number. It is commonly used for scenarios such as web-to-lead calling, where a call is triggered programmatically and then routed through the policy.
Policy availability
Available in the Call Policy? | Available in the Data Analytics Policy? | Available in the Digital Policy? | Available in the System Policy? |
|---|---|---|---|
✔ | ✖ | ✖ | ✔ |
Purpose
The Invokable Destination Container lets an automated or external process invoke a routing policy directly. Instead of a caller dialling a Natterbox number to enter the policy, the call is triggered programmatically and enters the policy through this container. This makes it the starting point for automated call flows.
Location
The Invokable Destination Container is found in the ‘Click here to START’ box, alongside the other entry containers such as the Inbound Numbers Container and the Extension Number Container.
Appearance
Use cases
Web-to-lead calling, where a new lead submission triggers an outbound call that is routed through the policy.
Automated or programmatically triggered call flows that do not begin with a caller dialling a Natterbox number.
Configuration
The Invokable Destination Container is the entry point for the automated process, so any calls invoked against the policy will begin here and follow the apps connected after it.