Skip to main content
Common questions about actions in Managed Topics. For full documentation, see Actions.
Actions let the agent do things beyond responding with text. They are defined in Managed Topics under the Actions field. The main types are:
  • SMS: Send a text message to the user (e.g., a link, confirmation, or follow-up details).
  • Function calls: Run a custom function to look up data, perform calculations, or update conversation state.
  • Handoffs: Transfer the user to a live agent. Handoffs have their own setup requirements, including logging reasons and configuring routing (e.g., SIP headers). See call handoffs for details.
Example: A user asks about a refund, and the agent sends an SMS with a link to the refund portal.
Yes. You can trigger multiple actions for a single topic — for example, sending an SMS and then initiating a handoff.
Yes. You can use variables and state from functions to conditionally control what happens. For example, you can show different content or trigger different actions depending on whether the user is authenticated or which location they’re calling from.This is set up through functions that run earlier in the conversation. The state they set can then be referenced in your topic content and actions.
If an action does not work as expected:
  1. Open the conversation diagnosis tool for the affected conversation to see what happened.
  2. Check that the action is correctly configured — correct function name, SMS template, or handoff destination.
  3. For handoffs, verify that the target queue or SIP endpoint is reachable and correctly routed.
  4. Reproduce the issue in sandbox to test your fix before promoting.
Common causes: misconfigured function names, missing variables, and unreachable handoff endpoints.
Last modified on March 27, 2026