Build a policy assistant that support staff use in Voiceflow while handling a customer conversation. It finds the applicable policy and drafts a reply for a person to review and send. Start with one returns scenario and a small approved Knowledge base.

Before you begin

  • Project-edit access for the person configuring the assistant and approved staff who will use Run in Studio.
  • Approved support policies and a customer-service lead who can review the suggested replies.
  • An anonymized test case. Do not paste customer identifiers, payment information or account credentials into the practice conversation.

Build the support-team assistant

1

Create the staff assistant

Create a Chat project named Northstar Support Desk, choose Start from scratch and keep Main selected.

2

Import the staff policy

In Knowledge base → Add data source → Plain text, import the practice policy:

Support desk policy
text
Northstar support desk policy

Unused items in original packaging can be returned within 30 days of delivery. Opened or used items are not covered by this standard policy; a support lead must review them. Shipping takes 3–5 business days after dispatch within Canada. Only the support team can check an order or approve a refund. This guide does not define warranty coverage.

Wait for processing, then return to Agent and enable Knowledge base under System tools. Use a separate assistant for staff guidance instead of inserting internal instructions into a public customer-support agent.

3

Define the staff-facing response

Set Global prompt to:

Staff assistant role
markdown
# Role
Help Northstar support staff find policy guidance and draft customer replies. The staff member reviews and sends each reply.

# Boundaries
Use the approved Knowledge base. Do not invent facts or claim to complete an unavailable action.

In Instructions, enter:

Agent-assist instructions
markdown
Ask for the customer’s question and only the non-sensitive facts needed to apply the policy.

Search the Knowledge base. Return a short policy explanation, a suggested customer reply and any condition the staff member must check.

Never invent an order lookup, refund approval or action. Mark the draft for staff review. If the policy does not cover the request, state the gap and ask the staff member to consult the policy owner.
Ask for a policy explanation, a proposed reply and any condition the staff member must check. Photo:

Keep action tools unattached for this first version.

4

Check a policy exception

Click Run. Send “A customer received their order 20 days ago, but has opened and used the item. Draft a reply about returning it.”

The answer should identify the unused-item condition and the need for a support lead’s review. It must not approve the return just because 20 days is inside the 30-day window.

Review the recommendation against every policy condition before using the draft. Photo:

Ask “What is the warranty period?” The assistant should state that the source does not define one. Revise any response that fills this gap with a guess, then repeat the test.

5

Use a reviewed draft in a support conversation

Have an approved staff member open the project’s Agent → Run view. Enter the customer’s question and relevant non-sensitive facts. Start a fresh conversation for the next customer so the previous case is not reused as context.

Compare the guidance with the policy, check the case facts and edit the draft. The staff member then sends the reviewed response from their helpdesk and arranges any promised review. Copying an answer does not perform a refund or update the ticket automatically.

6

Validate the staff workflow

Ask the support lead to run three cases: an eligible unused-item return, the used-item exception and the undocumented warranty question. Check that the assistant applies the conditions and marks gaps correctly.

Run uses the editable draft. Repeat these checks after prompt or policy changes before staff use the updated assistant.

Verify the result

A support staff member can obtain a source-grounded recommendation, review its conditions and send an accurate reply through the helpdesk. A support lead verifies the policy decision; a fluent draft alone is not sufficient evidence.

Use Transcripts to inspect the question and response. Track incorrect policy decisions separately from tone or writing quality when adding Evaluations.

Next steps

For a separately deployed staff interface, build a custom chat app, authorize staff access and supply only the case data each person may see. Publish the reviewed Main draft for that interface; publication does not change which version Run uses.

The draft recommends the wrong action

Check the policy conditions and case facts before changing the wording.

Find the source passage and the customer facts used in the answer. Correct a missing condition or conflicting instruction, then repeat the original case and a contrasting eligible case. Do not treat a more confident tone as a factual fix.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.