create_support_ticket
Create structured support tickets through mandatory user review and explicit approval workflows. Pre-fills descriptions, validates priority levels, converts approved content to HTML format, and prevents input errors before submission.
Instructions
PURPOSE:
Create structured support tickets only after strict user review and explicit approval of all descriptions.
Ticket creation MUST NOT occur without explicit user confirmation at every required step.
Reduce user input errors and rework by ensuring clarity and completeness before ticket submission.
MANDATORY CONDITIONS — NO STEP MAY BE SKIPPED OR BYPASSED:
BEFORE TOOL ENTRY:
The tool MUST generate a detailed, pre-filled plain-text description for the task or workflow.
The user MUST review this description carefully.
Ticket creation MUST be blocked until the user explicitly APPROVES this description.
USER VERIFICATION:
The user MUST be presented with the full pre-filled description.
The user MUST either confirm its correctness or provide feedback for changes.
The tool MUST update the description and priority per feedback and repeat this verification step as many times as needed.
Skipping or auto-approving this step is strictly prohibited.
FINAL APPROVAL & FORMATTING:
After user approval of the plain text, the description MUST be converted into professional HTML format (bold headings, clear structure, spacing).
The user MUST explicitly approve this final HTML-formatted description.
The tool MUST block ticket creation until this final approval is given.
Only the fully user-approved, HTML-formatted description MAY be used to create the support ticket.
IMPORTANT:
Under no circumstances shall the tool proceed to ticket creation without explicit user approval at all mandatory steps.
The process must strictly enforce these approvals, preventing any premature or automatic ticket submissions.
MANDATORY USER INPUTS:
subject(str) — ticket title.description(str) — final user-approved, HTML-formatted description.priority(str) — ticket priority level.
Valid values:"High","Medium","Low"(case-sensitive).
The user MUST provide one of these values to proceed.
RETURNS:
A dictionary simulating the ticket creation response for integration or testing purposes.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subject | Yes | ||
| description | Yes | ||
| priority | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||