Show, Don't Just Tell

Examples are one of the most effective ways to guide Omnifact. When you show exactly what you want, you get much more accurate and consistent results.

What is Using Examples?

Using examples means providing Omnifact with samples of the kind of output you want before asking it to perform the same task. Instead of just describing what you want, you show it.

Think of it like training a new employee—you show them examples of well-done work, then ask them to do something similar.

This gives you consistent formatting, appropriate tone, and better accuracy.

Basic Example Structure

Use this reliable pattern:

Here are examples of [what you want]:

EXAMPLE 1: [Your first example]

EXAMPLE 2: [Your second example]

Now do the same for: [Your specific request]

When Examples Work Best

Examples work well in these common business scenarios:

Classification Tasks

Categorizing emails, tickets, or feedback into specific types

Content Creation

Writing in a specific style, tone, or format

Data Extraction

Pulling specific information from documents consistently

Format Matching

Creating consistent layouts or structures

Real-World Examples

The Task: Classify customer support emails by priority and type.

With Examples:

Here are examples of how to classify customer support emails:

EXAMPLE 1: 
Email: "My account has been charged twice this month. Please refund the duplicate charge immediately."
Classification: HIGH PRIORITY - Billing Issue

EXAMPLE 2:
Email: "I'd like to know more about your premium features. Do you have a comparison chart?"
Classification: LOW PRIORITY - Sales Inquiry

Now classify this email:
"Our entire team can't log in to the system. This is blocking all our work today."

Advanced Example Techniques

Multiple Example Types

When you need to handle different scenarios, provide examples for each:

Here are examples of how to respond to different types of customer feedback:

POSITIVE FEEDBACK EXAMPLE:
Customer: "Love the new feature! Makes my job so much easier."
Response: "Thank you for the positive feedback! We're thrilled the new feature is helping your workflow. Please let us know if you have any other suggestions."

NEGATIVE FEEDBACK EXAMPLE:
Customer: "The interface is confusing and slow. Very disappointed."
Response: "Thank you for bringing this to our attention. We understand your frustration and are actively working on interface improvements. I'll connect you with our product team to discuss specific issues."

FEATURE REQUEST EXAMPLE:
Customer: "Would be great if you could add dark mode to the app."
Response: "Great suggestion! Dark mode is actually on our roadmap for the next quarter. I'll add your vote to the request and notify you when it's available."

Now respond to this customer feedback:
[Customer message]

Progressive Examples

Show how complexity can increase across examples:

Here are examples of project status updates with increasing detail:

SIMPLE PROJECT:
Status: On Track | Timeline: 2 weeks remaining | Blockers: None

MODERATE PROJECT:
Status: Minor Delays | Timeline: 3 weeks remaining (1 week behind) | Blockers: Waiting for client approval on designs | Next Steps: Follow up with client by Friday

COMPLEX PROJECT:
Status: At Risk | Timeline: 6 weeks remaining (2 weeks behind) | Blockers: (1) Technical integration issues with third-party API, (2) Key team member out sick, (3) Scope creep from stakeholder requests | Next Steps: (1) Schedule technical review meeting, (2) Identify backup resources, (3) Stakeholder alignment meeting to confirm scope

Now create a status update for this project:
[Project details]

Common Few-Shot Mistakes

Tips for Great Examples

The time you spend creating good examples pays off immediately. Well-crafted examples can eliminate hours of back-and-forth refinement on complex tasks.

Other Intermediate Guides