Tutorials Prompt Engineering Tutorial
Structured Responses — Complete Guide
Structured Responses — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Prompt Engineering Tutorial on Toolliyo Academy.
On this page
Prompt Engineering Tutorial · Lesson 17 of 100
Structured Responses
Prompts → Apps
Prompts · 1 — Basics · ~6 min · Module 2: Basic Prompting Techniques
What is this?
Structured responses mean the model fills a defined shape: fields, enums, or nested objects — not free prose. They feed APIs and dashboards reliably.
Why should you care?
PromptVerse ticket analyzer stores structured JSON in Mongo for filters and SLA dashboards.
See it live — copy this example
Copy the prompt into ChatGPT, Claude, or your LLM API playground and compare outputs.
Respond with JSON only:
{
"intent": "refund|technical|sales",
"urgency": 1-5,
"entities": {"order_id": string|null},
"needs_human": boolean
}
Message: "Refund for order OV-9921, app crashes on export"
What happened?
- Schema lists enums and types.
- Downstream code validates intent and urgency without NLP parsing of paragraphs.
Practice next
- Pick 4 fields your API needs.
- Prompt for JSON only.
- Validate with JSON.parse in Node.
- Add nullable fields explicitly.
- Require entities.order_id pattern OV-\d+.
Remember
Schema in prompt aligns with code. Validate after generation. Retry with error feedback on parse fail.
Ticket enrichment
CRM webhook needs intent + urgency.
Outcome: Structured JSON lands in Salesforce custom fields.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!