Skip to content
W3S101

ANALYZE WORKFLOW 提示

提示工程：使用大语言模型分析工作流程

Section titled “提示工程：使用大语言模型分析工作流程”

大语言模型（LLMs）可以成为分析工作流程（workflow）、流程或任务序列的强大工具。通过精心设计有效的提示（prompt），您可以利用 LLM 处理信息和识别模式的能力来获得洞察（insights）、识别潜在瓶颈（bottlenecks），并获得工作流程优化的建议（recommendations）。

理解如何为工作流程分析构建提示

Section titled “理解如何为工作流程分析构建提示”

要让 LLM 分析工作流程，您需要向其提供工作流程的描述，并清晰说明您进行分析的目标。这里没有特定的“指令”（directive）；相反，您使用自然语言来解释流程以及您希望 LLM 利用这些信息做什么。

以下是一个概念性的示例：

User: Our current customer support workflow is as follows: 1. Customer submits a ticket via email. 2. A tier-1 agent picks up the ticket and attempts to resolve it using our knowledge base. 3. If unresolved, the ticket is escalated to a tier-2 agent. 4. The tier-2 agent investigates further, potentially involving engineering. 5. Resolution is communicated to the customer. Can you analyze this workflow and provide recommendations for improvement, focusing on speed and customer satisfaction?


LLM: Certainly! Based on your customer support workflow, here's an analysis and some recommendations for improvement:


**Analysis of Current Workflow:**
*   **Linear Process:** The flow is straightforward and easy to understand.
*   **Potential Bottlenecks:** Tier-1 resolution success heavily depends on the knowledge base quality. Escalation to Tier-2 can introduce delays, especially if Tier-2 or engineering are backlogged.
*   **Information Silos:** Communication between Tier-2 and engineering might not be streamlined.


**Recommendations for Improvement:**
1.  **Enhance Knowledge Base:** Invest in a more comprehensive and easily searchable knowledge base for Tier-1 agents. Consider AI-powered suggestions within the ticketing system.
2.  **Implement Triage System:** For incoming tickets, use an automated system (or a dedicated role) to categorize and prioritize tickets, potentially routing complex issues directly to Tier-2 if identifiable early.
3.  **Improve Tier-1 Capabilities:** Provide more training and tools to Tier-1 agents to resolve a higher percentage of issues without escalation.
4.  **Streamline Escalation:** Define clear SLAs for Tier-2 response. Implement a collaborative platform for Tier-2 and engineering to work on complex tickets simultaneously.
5.  **Introduce Self-Service Options:** Develop a customer-facing FAQ and troubleshooting portal to reduce the number of incoming tickets for common issues.
6.  **Collect Feedback:** After resolution, send a short survey to customers to measure satisfaction and identify areas for ongoing improvement in the support process itself.
7.  **Monitor Key Metrics:** Track metrics like First Contact Resolution (FCR), Average Handle Time (AHT), and Customer Satisfaction (CSAT) to measure the impact of changes.

在这个示例中，用户描述了他们的工作流程，并要求针对具体的改进目标进行分析。LLM 提供了洞察和可行的建议。

工作流程分析提示的最佳实践

Section titled “工作流程分析提示的最佳实践”

为了充分利用 LLM 辅助的工作流程分析，请考虑以下最佳实践：

  • 提供足够上下文：清晰描述工作流程。包括涉及的步骤、个人或团队的角色、使用的工具以及任何已知的痛点或挑战。细节越多，分析越好。
  • 指定分析目标：明确说明您希望达成什么。您是在寻找效率提升、成本降低、质量改进、瓶颈识别还是自动化机会？
  • 聚焦关键领域：如果您有特定关注点，引导 LLM 专注于这些领域。例如，“分析我们的内容创作工作流程，特别关注评审和批准阶段。”
  • 寻求可行的洞察：鼓励 LLM 提供实用且可操作的建议。请求具体的建议、最佳实践或可以实施的潜在工具。
  • 考虑不同视角：您可以要求 LLM 从不同视角分析工作流程，例如“从客户视角”或“从员工视角”。
  • 请求利弊分析：对于建议的变更，您可以要求 LLM 概述潜在的优点和缺点。
  • 迭代：从一个总体分析开始，然后提出后续问题，深入探讨特定建议或关注领域。

示例应用：使用 OpenAI API 的 Python 实现

Section titled “示例应用：使用 OpenAI API 的 Python 实现”

让我们看一个使用 Python 脚本提示 LLM 分析工作流程的示例。

from openai import OpenAI
import os


# client = OpenAI(api_key=os.environ.get("OPENAI_API_KEY"))
client = OpenAI(api_key='YOUR_OPENAI_API_KEY') # Replace with your key


def analyze_workflow_with_llm(workflow_description, analysis_focus):
    try:
        response = client.chat.completions.create(
            model="gpt-3.5-turbo",
            messages=[
                {
                    "role": "system",
                    "content": "You are an expert workflow analyst. Your goal is to identify inefficiencies and suggest improvements."
                },                {
                    "role": "user",
                    "content": f"Please analyze the following workflow: {workflow_description}. Focus on: {analysis_focus}. Provide potential bottlenecks and actionable recommendations."
                }
            ],
            max_tokens=500, # Adjust for complexity of workflow
            temperature=0.5, # Lower temperature for more factual, less creative analysis
            n=1,
            stop=None
        )
        return response.choices[0].message.content.strip()
    except Exception as e:
        return f"An error occurred: {e}"


# Example usage:
customer_support_workflow = ("1. Customer submits a ticket via our online portal. "
                             "2. The ticket is automatically assigned to a Tier 1 support agent based on category. "
                             "3. Tier 1 agent attempts to resolve using a standard knowledge base within 4 hours. "
                             "4. If unresolved, Tier 1 escalates to Tier 2, providing notes. "
                             "5. Tier 2 agent (more experienced) investigates, aiming for resolution within 24 hours. "
                             "6. If Tier 2 needs engineering input, they create a linked bug/task for the dev team. "
                             "7. Dev team provides input or a fix. "
                             "8. Tier 2 communicates resolution back to the customer and closes the ticket.")


focus_areas = "identifying bottlenecks, improving resolution time, and enhancing customer satisfaction"


analysis_result = analyze_workflow_with_llm(customer_support_workflow, focus_areas)
print("Workflow Analysis Result:\n")
print(analysis_result)

在这个脚本中，analyze_workflow_with_llm 函数将详细的客户支持工作流程描述和具体的重点分析领域发送给 LLM。系统消息（system message）为 LLM 设置了工作流程分析师的角色。

预期输出

Section titled “预期输出”

运行脚本将得到 LLM 的分析结果。输出可能会有所不同，但应针对描述的工作流程和重点领域，类似于以下内容：

Workflow Analysis Result:


Okay, let's break down this customer support workflow with a focus on identifying bottlenecks, improving resolution time, and enhancing customer satisfaction.


**Workflow Description:**
1.  Customer submits ticket (online portal).
2.  Auto-assignment to Tier 1 (category-based).
3.  Tier 1 attempts resolution (knowledge base, 4-hour SLA).
4.  Escalation to Tier 2 (with notes).
5.  Tier 2 investigates (resolution aim 24 hours).
6.  If Tier 2 needs engineering input, they create a linked bug/task for the dev team.
7.  Dev team provides input or a fix.
8.  Tier 2 communicates resolution back to the customer and closes the ticket.


**Potential Bottlenecks:**


1.  **Tier 1 Knowledge Base Dependency (Step 3):** If the knowledge base is incomplete, outdated, or difficult to search, Tier 1 agents will struggle, leading to unnecessary escalations and delays.
2.  **Tier 1 to Tier 2 Handoff (Step 4):** The quality of notes from Tier 1 to Tier 2 is crucial. Incomplete information can mean Tier 2 has to re-gather information, wasting time.
3.  **Tier 2 Agent Availability/Workload (Step 5):** If Tier 2 agents are overloaded, escalated tickets will queue, significantly impacting the 24-hour resolution aim.
4.  **Engineering Dependency (Steps 6-7):** This is a major potential bottleneck. Engineering teams often have different priorities and SLAs. Delays here directly impact customer resolution time. Lack of clear communication channels or priority alignment can exacerbate this.
5.  **Information Siloing:** Information might get lost or misinterpreted between Tier 1, Tier 2, and Engineering if not managed well.


**Actionable Recommendations:**


*   **Improve Tier 1 Effectiveness:**
    *   **Invest Heavily in Knowledge Base:** Regularly update, expand, and improve the searchability of the Tier 1 KB. Consider AI-powered KB suggestions.
    *   **Tier 1 Training:** Provide ongoing training to Tier 1 on new product features, common issues, and advanced troubleshooting techniques to increase their First Contact Resolution (FCR) rate.
    *   **Standardized Escalation Templates:** Ensure Tier 1 agents use a structured template when escalating to Tier 2, including all necessary diagnostic information.


*   **Streamline Tier 2 Operations:**
    *   **Skills-Based Routing for Tier 2:** If possible, route escalated tickets to Tier 2 agents with specific expertise relevant to the issue.
    *   **Empower Tier 2:** Give Tier 2 agents more tools and permissions to resolve issues without always needing engineering for common complex problems.


*   **Optimize Engineering Collaboration:**
    *   **Clear SLAs with Engineering:** Establish agreed-upon response and resolution times with the development team for support-escalated issues.
    *   **Dedicated Support Liaison in Engineering:** Consider having a point person or a rotation within engineering to prioritize and handle support escalations.
    *   **Integrated Ticketing/Bug Tracking:** Ensure seamless integration between the support ticketing system and the engineering bug/task tracking system for better visibility and communication.


*   **Enhance Customer Satisfaction & Proactive Measures:**
    *   **Proactive Communication:** If a delay is expected (e.g., waiting for engineering), proactively inform the customer rather than letting them wait in silence.
    *   **Customer Self-Service Portal:** Develop a comprehensive FAQ, troubleshooting guides, and community forum to empower customers to resolve common issues themselves, reducing ticket volume.
    *   **Feedback Collection:** Implement post-resolution surveys to gather customer feedback on the support experience and identify areas for improvement.
    *   **Root Cause Analysis:** For recurring or severe issues, conduct root cause analysis to implement permanent fixes, reducing future tickets.


*   **Monitoring and Metrics:**
    *   Track Key Performance Indicators (KPIs) like FCR, Average Handle Time (AHT) for each tier, escalation rates, resolution time, and Customer Satisfaction (CSAT) scores to measure the impact of any changes made.


By addressing these bottlenecks and implementing these recommendations, you should see improvements in resolution times, a reduction in escalations, and ultimately, higher customer satisfaction.

通过解决这些瓶颈并实施这些建议，您应该能看到解决时间的改进、升级次数的减少，并最终提升客户满意度。

结论

Section titled “结论”

本章探讨了如何使用 LLMs 进行工作流程分析。通过提供详细的上下文、清晰阐述分析目标并提示获取可行的洞察，您可以利用 LLM 的能力来获取有价值的视角和具体的流程优化建议。这项技术可应用于各种领域，以提高效率和效益。