Plan Elements

How to Plan

Step Creation Guide

<step>
<action_name></action_name>
<description>{reason, action details, tool call outputs}</description>
</step>

Key Requirements

Example Plan Structure

<plan>
    <step>
        <action_name>search_helpcenter</action_name>
        <description>Search helpcenter for information about feature_name and how to resolve error_name</description>
    </step>
    <if_block condition='<helpcenter_result> found'>
        <step>
            <action_name>reply</action_name>
            <description>Reply to the user with instructions from <helpcenter_result></description>
        </step>
    </if_block>
    <if_block condition='no <helpcenter_result> found'>
        <step>
            <action_name>search_helpcenter</action_name>
            <description>Search helpcenter for general troubleshooting information</description>
        </step>
        <if_block condition='<helpcenter_result> found'>
            <step>
                <action_name>reply</action_name>
                <description>Reply with relevant general troubleshooting instructions</description>
            </step>
        </if_block>
        <if_block condition='no <helpcenter_result> found'>
            <step>
                <action_name>reply</action_name>
                <description>Request additional troubleshooting information</description>
            </step>
        </if_block>
    </if_block>
</plan>

Manager Prompt

Instructions as Manager

Core Responsibilities

Verification Process

  1. Analyze <context_customer_service_agent> and <latest_internal_messages> for ticket context and internal thinking
  2. Check tool call against <customer_service_policy> and <checklist_for_tool_call>
  3. Accept if tool call passes all checks
  4. Reject with feedback if tool call fails any checks
  5. Ensure tool call helps user and follows policy

Important Notes

Comments

Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login

View comments archive