constraints stringclasses 2
values | dialogue_text stringclasses 2
values | workflow_steps stringclasses 2
values | automation_goal stringclasses 2
values | expected_result stringclasses 2
values | trigger_condition stringclasses 2
values | final_workflow_plan stringclasses 2
values | conversation_summary stringclasses 2
values | unresolved_questions stringclasses 2
values |
|---|---|---|---|---|---|---|---|---|
Include only open tickets that meet the stated attention criteria; exclude tickets waiting on the customer. Use only ticket number, subject, current owner, priority, and last customer-facing reply date. Do not include customer names, email addresses, or message text. The digest must remain a draft until the team lead a... | User: We get a lot of support tickets, and I’d like a weekly digest of the ones that still need attention.
Assistant: When should the digest be prepared, and where should it go?
User: Every Monday at 9 a.m. local time. Put it in our support team’s shared channel.
Assistant: Which tickets should count as needing attenti... | 1. On the scheduled run, retrieve open support tickets. 2. Exclude tickets waiting on the customer. Include the remaining open tickets if they are marked urgent or have had no customer-facing reply for at least two days. 3. Group matching tickets by priority and sort each group by age, oldest first. 4. Prepare a digest... | Prepare a privacy-conscious weekly draft digest that helps the support team identify open tickets needing attention and awaits team lead approval before posting. | A Monday digest draft, grouped by priority and ordered oldest first, is available for the team lead to review. It is posted to the support team's shared channel only after approval. If no tickets match, the draft says so; if approval is still missing at noon, the lead receives one reminder and the draft remains unposte... | Every Monday at 9 a.m. local time. The exact time zone has not yet been specified and must be confirmed when the support system is connected. | After confirming the local time zone and connected systems, run every Monday at 9 a.m. Retrieve open support tickets, exclude those waiting on the customer, and select tickets marked urgent or with no customer-facing reply for at least two days. Group the results by priority and order each group oldest first. Build a d... | The user wants a weekly Monday 9 a.m. digest of open support tickets with no customer-facing reply for at least two days or tickets marked urgent, excluding tickets waiting on the customer. The digest should be grouped by priority and then age, oldest first, and prepared as a draft for the team lead. It must not be pos... | The time zone for the Monday 9 a.m. schedule is not yet known. The support system and shared-channel integration details also need to be confirmed when the system is connected. |
Do not place orders automatically. Keep the original form submission unchanged. Share request details only with people already authorized in the purchasing process. Do not route incomplete requests for approval. Send only one reminder after three business days without a response; leave the request pending afterward. | User: I want to automate the intake of equipment purchase requests.
Assistant: What should start the workflow, and what should happen to each request?
User: A new submission in our purchase request form should start it. I need the request checked for required details, then routed for approval.
Assistant: Which details ... | 1. Read the new submission and check for an item description, quantity, estimated cost, department, and business reason. 2. If any required detail is missing, ask the requester to update the submission and pause the workflow without routing it. 3. If the request is complete and estimated cost is under $1,000, route it ... | Validate equipment purchase requests, obtain the required approvals, and create a purchasing team task for approved requests without placing an order. | A complete, approved request is recorded in a task for the purchasing team. Incomplete, declined, or still-pending requests follow the specified notification or pause behavior, and no order is placed automatically. | A new submission in the purchase request form. | On each new purchase request form submission, verify that the item description, quantity, estimated cost, department, and business reason are present. If anything is missing, ask the requester to update the submission and stop before approval routing. Route complete requests under $1,000 to the department manager; rout... | The user wants purchase requests submitted through a form validated and routed for approval. Requests below $1,000 require department manager approval; requests at or above $1,000 also require Finance approval. Missing information blocks routing. Approved requests create a task for purchasing, but the workflow must not... | The user did not specify which form, messaging, approval, or task-management systems should be connected, or the exact fields and destinations for the purchasing task. These implementation details need confirmation before configuration. |
AI Workflow Requirement Clarification and Design Dialogue Dataset
This dataset focuses on multi-turn conversations between users and assistants about automation needs, covering key details such as goals, trigger conditions, workflow steps, constraints, and expected outcomes. The dialogues show how an assistant can identify requirements, ask for missing information, and develop a workflow proposal. It supports dialogue SFT and evaluation of requirement understanding, clarification, and workflow design for orchestration assistants.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| constraints | string | User-stated restrictions, prerequisites, permissions, or other limitations that the workflow must respect. |
| dialogue_text | string | The complete multi-turn conversation between the user and assistant about the desired automation workflow. |
| workflow_steps | string | The proposed workflow actions in their intended order, including important inputs, decisions, or branches. |
| automation_goal | string | The outcome or task the user wants the workflow to automate. |
| expected_result | string | The intended final output or state after the workflow completes successfully. |
| trigger_condition | string | The event, schedule, or condition that starts the workflow, including relevant details clarified in the dialogue. |
| final_workflow_plan | string | A consolidated natural-language workflow proposal incorporating the clarified goal, trigger, steps, constraints, and expected result. |
| conversation_summary | string | A concise summary of the key clarifications and decisions made during the conversation. |
| unresolved_questions | string | Important requirements or implementation details that remain unclear or unanswered at the end of the dialogue. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- -