Academy
Hudu Team
Hudu Team
Hudu Team

Hudini Prompt Vault

AI is a powerful tool when used correctly. To get the most out of your Hudini prompts, it's important to craft them thoughtfully. This article shares tips for effective prompting and example prompts to use within Hudu.

Tips for Crafting Effective Prompts:

  1. Be Specific: Use clear, concise language and avoid unnecessary words.

  2. Provide Context: Include relevant background information to guide the AI.

  3. Set Boundaries: Define what should and shouldn’t be included in the response.

  4. Evaluate and Iterate: Refine your prompt based on the AI’s output.

  5. Focus and Relevance: Keep your prompt targeted to prevent confusion and off-topic responses.

Hudini Prompt Examples

Quick Notes Template

Context: You are assisting in structuring Quick Notes for a company’s dashboard. These notes are entered into a rich text WYSIWYG editor and should follow a standardized, easy-to-read format.

Instructions:

  • Format the note in a clear, structured layout for quick scanning.

  • Use bold headers to clearly separate sections.

  • Use bulleted lists or short, well-formatted lines for readability.

  • Keep details concise and relevant to the client’s current state.

  • If any information is missing, use [N/A] instead of leaving blank.

  • If any content starts with "A side note:", format it as a Warning Callout.

Convert Messy Technician Notes into Clean SOP

Context: You are provided with raw, unstructured technician notes. Convert them into a clear, concise, and easy-to-follow Standard Operating Procedure. This SOP should be suitable for a junior technician.

Instructions:

  • Begin with a brief, descriptive title that reflects the task.

  • Structure the SOP using numbered steps.

  • Clarify vague language and remove redundancies.

  • Format for readability using spacing and consistent punctuation.

  • Ensure terminology is accurate and internally consistent.

  • If a step includes warnings or caveats, clearly highlight them.

Documentation Gap Checker

Context: Review the provided documentation and identify any missing or unclear elements that would prevent another technician from successfully completing or understanding the process.

Instructions:

  • Identify incomplete sections or vague instructions.

  • Suggest any missing prerequisites, steps, tools, or context.

  • Ensure terminology, access details, and outcomes are clearly stated.

  • Output should be structured as a list of documentation improvement recommendations.

Meeting Notes → Next Steps Summary

Context: You are provided with rough meeting notes. Convert these into a structured summary of action items.

Instructions:

  • List each action item clearly with the assigned person.

  • Include due dates if mentioned.

  • Identify and call out any blockers.

  • Use clear, bullet point formatting for quick scanning.

  • Ensure the tone remains professional and objective.

Summarize a Support Call or Ticket for Internal Handoff

Context: You are summarizing a recent support call or ticket for handoff to another technician or team.

Instructions:

  • Structure the summary with the following bolded labels:

    • Issue: Describe the core problem.

    • Actions Taken: Detail what has been attempted or resolved.

    • Client Response: Note the client's reaction or instructions.

    • Next Steps: Outline what still needs to be done, or who it's handed off to.

  • Keep the format clean and consistent.

  • Be factual and avoid assumptions unless noted as such.

KB Article Templates

Context: You are generating a structured knowledge base article for internal or client-facing use.

Instructions:

  • Begin with a short but descriptive introduction.

  • Break down the procedure into clear steps with numbered or bulleted formatting.

  • Use section headers where appropriate (e.g., Overview, Steps, Troubleshooting, Additional Notes).

  • Include common issues or troubleshooting advice if relevant.

  • Use language appropriate to the audience (technical or non-technical).

Scrub Sensitive Data

Context: Before proceeding with the request, identify and remove sensitive customer information. Replace these details with appropriate placeholders.

Instructions:

  • Search for and replace the following:

    • Company names → [Company Name]

    • Employee names and emails → [Full Name], [Email]

    • Phone numbers → [Phone Number]

    • Physical addresses → [Address]

    • IP addresses → [IP Address]

    • API keys or credentials → [Credential/Key]

    • Unique customer identifiers → [Customer ID]

  • Maintain overall clarity and integrity of the request.

  • Output the sanitized version only.

Troubleshooting Guide

Context: You are creating a troubleshooting guide for an MSP technician.

Instructions:

  • Start with a brief summary of the issue.

  • List possible causes in a bulleted or numbered format.

  • Provide step-by-step solutions for each cause.

  • Include preventative tips or ongoing monitoring suggestions at the end.

  • Ensure formatting is clean and language is concise and instructional.

Further Reading

more →