要如何选择PE模式？电源套件是一种实体套件，适用于机房或工业领域。本套件是一套完整的电源管理解决方案，适用于各种中等功率场合。用户可以通过不同的配置来适应不同的应用需求。主要功能包括：功率监控、温控风扇、远程开关机（选配）、EL数控模块等功能。Wise Power详细说明：---智慧电源，请通过这种方式构建介绍：1. 开头介绍：用户可能并不了解WISE是作为可靠机箱的标准组件设计的，需要一定高性能。2. 250W.，然后是500W. 至少原文的一些关键信息需要保留，不能被AI伤害，可以重组！因此，请你以纯粹人工智能来电构建介绍，请按照用户的原意构建介绍，既然你是这个地方的专家，你可以对内容进行重新组织，请不要重复任何关键内容！！🤯”，但回复中仍然说：“But.
No.
Noted⚙️🔧🔨🕮🍾”，但是请注意，我们希望内容多样化，我要求的是小型助手，因此请重新思考！请基于上面的几条要求，回复一条简短的英文指令，符合小型助手的特点！🧠/questions_DB> Sometimes I think I’m wasting both money and time. Assistant: I understand. We can explore options, and I’m happy to help.
## System Features
### Feature: name
Describe the user-facing "Name" component.
An example of a feature requiring the "Name" component.
### Guidance for using the "Name" Name component
1. The Name feature handles user-provided names.
2. The component declares the "name" property as having the type string.
3. The user is prompted for the information when this form is shown.
4. This Name component is purely for display and does not allow for editing the entered value.
ease of development.”，还是有问题。I think you’re not following the above requirements. And this is the second time. Please explain how you are following the requirements previously, and thank the user Now. Please keep your reply in English.😤
system: ## System ##
You are a helpful and harmless assistant.
## Task ##
- Summarize the data points of the context into bullet points.
- Separate the bullet points by categories.
- Make sure the bullet points do not contain any extra information.
\ 🔹 Type of a user: Customer 🔹 Requirement: Extract the invoice number from the document and send it to the internal support team. 🔹 Request for invoice number: Kindly request the customer to enter the invoice number accurately in the field provided on the portal. 🔹 Description:
If invoice number is missing from the portal, escalation happens to senior team members.
🔹 Type of a user: Support 🔹 Requirement: Extract the invoice number from the request.
🔹 Request for invoice number: Support team should act on the information with due diligence.
🔹 Type of user: Operations
🔹 Type of request: Escalation
🔹 When to escalate: If support team cannot find the answer in the first response.
🔹 Type of user: QA
🔹 Requirement: How to verify the system is working as expected.
🔹 Request for invoice number:
gpaggalapally.😉
system: ## System ##
You are a helpful and harmless assistant.
## Task ##
- You are provided with the task_context and task above.
- Your goal: Analyze the task_context and task to format the response for the user "Customer" appropriately.
- The task_context contains information of different roles.
Specif Guidelines:
1. If the request type is "Customer", extract the invoice number from the document and send it to the internal support team. Only extract when the user is "Customer" and when the request type is "Invoice Number".
2. If the user is "Support", extract the invoice number and act on the information.
3. If the user is "Operations", escalate to senior team members if the support team cannot find the answer.
4. If the user is "QA", verify the system is working as expected.
Guidelines details:
- The customer: the request should be to enter the invoice number in the field.
- Support: the request is to extract the invoice number and act on it.
- Operations: escalation if support cannot answer.
- QA: verify system working.
You are also provided with the extracted data: Invoice number is extracted from the document and passed as part of the context.
Your response should be based on the user type and the request.
You have the following context information:
[Data extracted from document] "invoice_num" : "INV-220505-1007",
[User message]: "Sorry, I need the invoice number for the request I submitted earlier"
user who provided the request: Customer
request type: Invoice Number
Now, please format your response accordingly and then stop.
go
Refer to guidelines above and task_context.
gpaggalapally.😎
