NOCK
Widget

AI Enhancement

Enable AI-assisted follow-up questions so widget tickets arrive with clearer reproduction details and customer context.

AI Enhancement helps reporters turn short feedback into more useful tickets. When the feature is enabled, the widget can ask one to three focused follow-up questions before the user submits.

Configure it in Settings > AI.

What users see

When a user opens the widget, they write a title, optional description, and choose a category. If AI is available, the form shows a Refine with AI card.

When the user clicks it, NOCK sends the draft report to the AI endpoint and returns targeted questions. The user can answer what they can, skip what they do not know, and submit the ticket normally.

If the report already looks complete, the widget tells the user they are good to send.

Enable AI

Open Settings > AI

Select a project and go to Settings > AI.

Enable AI Enhancement

Turn on Enable AI Enhancement.

Optionally add a prompt

Use Custom Prompt to give NOCK project-specific instructions. The prompt can be up to 2000 characters.

Save AI

Click Save AI. The AI card appears for new widget sessions when your plan has remaining AI usage.

Plan limits

AI usage follows the workspace billing plan:

PlanAI enhancements / month
Lite10
Plus50
Growth500
Scale2,000

When the limit is exhausted, core ticket submission still works. The AI refinement step pauses until the next billing period or a plan upgrade.

Data sent to AI

For refinement, NOCK sends the draft ticket fields needed to ask useful follow-up questions:

FieldPurpose
TitleUnderstand the core issue or request.
DescriptionUse existing context to avoid redundant questions.
CategoryTailor questions to bug, feature, feedback, or your custom category.
Custom promptApply project-specific instructions you configured.

The user's answers are stored with the ticket as AI follow-up Q&A.

Warning

Do not ask users to put passwords, payment details, private keys, or other secrets into feedback. AI Enhancement improves ticket clarity; it is not a secure intake flow for sensitive credentials.

On this page