CumulusDocs
Open Studio
On this page

Build a branching support agent

A customer calls with an invoice question or refund request. The agent needs to verify account access, read the account and choose the right next step. If it cannot resolve the request, it should offer a specialist.

Build those decisions in Studio using conversation nodes, an HTTP action and a reusable refund-review component. The example records are fictional; your team supplies the account service and business rules.

Map the decisions

For the business access check below, your endpoint decides whether the caller may see the record. If you need verification through a private telephone keypad, use the private verification workflow instead of collecting sensitive answers in the conversation.

A billing-support flow with caller identification, verification, an HTTP lookup, branching, a reusable refund review and transfer

StepWhat you configureWhat to check
Identify callerAsk for the account reference and explain the purposeDo not disclose account details before verification
Verify accountThe verification conversation and confirmed-identity transitionTest refusal, wrong-person and ambiguous answers; enforce access checks in the account service
Look up accountA function node bound to your HTTP actionValidate the input and response schemas; define timeout and uncertainty behavior
Route requestA branch with conditions on variablesMake the default path explicit; missing variables must have a defined outcome
Refund reviewA reusable componentReview eligibility before promising an outcome
Explain invoiceInstructions using the returned account facts and approved policyAnswer from available facts; escalate when they are insufficient
TransferA transfer node and a destinationTest unavailable or failed transfers as well as successful ones
EndThe terminal nodeDecide what completion means for this business workflow

Define the verification and refund rules before connecting the nodes. Use conversation conditions for answers such as “I want a refund,” and equation conditions for returned values such as eligibility. Test ambiguous answers and missing values.

Bind an external action

A function node inspector with the selected action, wait-for-result behavior and execution message

  1. Open Settings → Actions and define lookup_account. Supply the HTTPS endpoint, method, input/output schemas, timeout and credential reference.
  2. Add a function node and select that action. Enable Wait for result when the next decision requires its response.
  3. Choose whether to speak during execution. A short status message can explain a pause without claiming that the request already succeeded.
  4. Configure response variables and the transitions that consume them. Treat an empty result, an error and an uncertain outcome as separate cases.
  5. Use a mock response in a simulation. Verify the real endpoint separately with an authorized integration run.

Credentials belong in secrets, not in prompts. Your endpoint still owns authentication, input validation and business authorization. For writes, it must honor the action's idempotency contract. Reconcile an uncertain write with the business service before retrying it.

For API configuration, see HTTP actions and draft edits. Review attempts and delivery results through action receipts.

Reuse a subflow

The refund review component opened on its own canvas

Move the refund review into a component with its own entry and return point. The main graph calls it when the customer requests a refund. Test eligibility, confirmation and rejection inside the component, then check how each result returns to the main flow.

Studio and the draft API edit the same definition. Publishing pins the main flow and its components together, so each run uses the component version you tested.

Ground answers in documents

For policy questions, upload your approved sources through Knowledge and documents, wait for the index to be ready and pin the source documents on the draft. Publish that draft to make the knowledge configuration part of the version.

Keep account facts and policy retrieval separate: the account action reads the customer's record; knowledge retrieval finds supporting policy. Include missing or conflicting policy evidence in your test cases.

Validate, test and release

A candidate published with live: false can only run with test: true. To use the reviewed behavior for regular calls or tasks, publish it with live: true; moving a test version to the head does not change that restriction. Publication and recovery covers the exact requests.

  1. Save the draft and run validation. Fix errors; review warnings against the intended behavior.
  2. Publish a test version with live: false. Run the regression suite against that exact version.
  3. Inspect failed assertions and tool behavior. Edit the draft, publish another test version and rerun the same suite.
  4. Refresh and validate the reviewed draft, then publish it explicitly with live: true for regular calls or tasks. Verify its returned digest and test flag. Existing runs keep their original publication; assign phone routes separately.
  5. Review a real run using the run investigation guide. Test real business endpoints, carrier connectivity and audio separately.

Each run records its publication. When a production issue appears, open that version to inspect the flow and component that executed.

Content version e416ca6cCustomer SDKMarkdown source
Build a branching support agent · Cumulus developer docs