Skip to main content
A customer asks support to turn off Do Not Disturb for a specific user in their voice service. Give the agent responsibility for the complete result: identify the right customer and user, confirm the request, change the setting after approval, verify the new state, and complete the customer conversation and ticket. This recipe uses a help desk such as HubSpot or Zendesk and a service such as Dialpad. Connect your accounts, configure the support agent, and test the complete workflow in your environment before enabling production intake.

​
Prepare the workflow

  • Configure the help-desk and service connectors as eligible organization service connections, with separately authorized worker accounts or credentials.
  • Grant the channel and workflow stages only the endpoints needed to read the request, inspect the user, propose the setting change, verify it, reply, and update ticket status.
  • Supply a trusted customer/account mapping. Do not let an address or account identifier in untrusted ticket text choose the worker’s authorization scope.
  • Define the intended state, the independent approval owner, and the conditions for escalation or closure.
  • Configure a supported trigger, such as an authenticated help-desk webhook carrying the ticket reference. Native inbound-email worker triggers are not enabled in production.
The connector target must be reachable through a public HTTPS endpoint. This workflow does not require the agent to borrow an engineer’s desktop session or reach a private customer network.

​
Carry the request through the support loop

This sequence shows a successful case. Each approval applies to the specific request that follows it; the reviewer is an authorized manager who did not start the run. Studio handles the human tasks and checks reviewer authority. If approval is refused, verification fails, or a reply or status update cannot complete, follow the configured escalation path with the evidence collected so far.
1

Read the ticket and customer conversation

The agent reads the ticket, its conversation, and the relevant account through the granted endpoints. For HubSpot, the workflow can retrieve the ticket and conversation thread; for Zendesk, it can read the ticket and its comments. Record the source identifiers needed for later updates.
2

Establish the requested change

Look up the affected service user within the trusted customer scope and read the current setting. When Org Brain is enabled, search eligible organization-visible knowledge for the team’s troubleshooting and service policy. If the requester, target user, or intended outcome is ambiguous, ask the support team rather than guessing.
3

Ask a teammate when needed

A worker human task pauses the work item for a question. With native Slack routing configured, the mapped support channel can receive an Answer card. Keep the answer attached to the run so the agent resumes with the decision and its context.
4

Approve the concrete service change

The agent proposes the allowed Dialpad setting change through its configured endpoint. Studio freezes the method, target, parameters, and body for review. An authorized channel manager or organization administrator who did not start the work item approves the exact request in Studio or through the configured Slack review path. A changed request requires a new approval.
5

Execute and verify

The agent executes the approved API request, then reads the user’s setting again. Compare the returned state with the requested outcome. If the action fails or the setting does not match, follow the configured retry or human-escalation path and include the observed result. A model-generated success summary is not a substitute for this check.
6

Send the customer response

Prepare the reply from verified results: which account was changed, what setting now applies, and any next step. Request independent approval for the exact customer-visible write before sending it through the help-desk conversation. A separately configured Outlook or Gmail worker connection can provide another approved delivery path when the workflow requires it.
7

Resolve the external ticket

Apply the team’s closure policy and use the correct ticket state for that help desk. For HubSpot, discover the appropriate closed pipeline stage instead of guessing its ID. Submit the ticket update for independent approval, execute it, and record the result. Completing the Studio work item alone does not close the customer’s ticket.
8

Review the outcome and retain the lesson

Leave a concise outcome linking the request, approvals, action, read-back, response, and ticket update. Review failures or unnecessary questions to improve the agent’s instructions. Publish suitable reusable knowledge with an explicit audience; worker Brain search does not automatically retrieve channel-only work reports.

​
What success looks like

The target account has the requested state, the customer has received a verified response, and the help-desk ticket reflects the agreed resolution. If any part cannot complete, the case has a named next owner and enough evidence to continue. Track the difference between a proposed change, an approved change, a successfully verified change, a sent reply, and a resolved ticket. Those are distinct outcomes in the full support loop.

Digital workers

Set up triggers, service connections, stage permissions, approvals, and outcomes.

Support loop

Define intake, investigation, action, verification, communication, and learning.