Skip to main content
Test your templates with real data before running full jobs to catch issues early.

​
Why Test First

  • ✅ Verify prompt produces good output
  • ✅ Check quality flags for issues
  • ✅ See cost estimates
  • ✅ Catch variable problems
  • ✅ Iterate quickly without wasting usage
Template tests count toward your monthly usage! Each test consumes 1 row of your allowance.

​
How to Test a Template

1

Open the Template

Go to Templates and click on the template you want to test
2

Select a Test File

Choose a file from your uploaded CSVs to use as test data
3

Click Test

Click the Test button
4

Review Results

See generated output, quality flags, token usage, and cost
5

Iterate if Needed

Adjust your prompt and test again until satisfied

​
What You’ll See in Test Results

FieldDescription
Generated OutputThe AI’s response for the test row
Quality FlagsAny issues detected (too short, forbidden word, etc.)
Token UsageInput and output tokens consumed
CostEstimated cost for this generation
Input DataThe row data that was used
Built PromptThe final prompt sent to the AI (with variables filled)

​
Testing Unsaved Templates

You can test a template before saving it:
  1. Fill in the template form (name, prompt, etc.)
  2. Select a test file
  3. Click Test
  4. Review results
  5. Then save if satisfied
This lets you iterate on your prompt without creating multiple saved versions.

​
Interpreting Test Results

​
Good Results

  • ✅ Output is relevant and personalized
  • ✅ No quality flags (or only minor ones)
  • ✅ Length is appropriate
  • ✅ Matches your intended tone

​
Warning Signs

  • ⚠️ Output is too generic
  • ⚠️ Quality flags present
  • ⚠️ AI ignored your instructions
  • ⚠️ Variables didn’t resolve correctly

​
What to Do If Results Are Poor

Add more specific instructions. Include examples. Reference more data columns.
Add explicit length constraints: “Keep under 100 characters” or “Write 2-3 sentences”
Make instructions clearer. Put them at the end of the prompt. Use “IMPORTANT:” prefix.
Check that column names match exactly. View your file to verify column names.
The AI might not follow forbidden words perfectly. Make the prohibition clearer in your prompt too.

​
Testing Multiple Rows

The test feature runs on sample rows from your file. This gives you a representative output without processing the entire file.
If testing consistently produces good results, you can confidently run a full job.

​
Cost of Testing

Each test:
  • Uses 1 row of your monthly allowance
  • Consumes tokens (billed if BYOK)
  • Counts toward usage tracking
Recommendation: Test 3-5 times to iterate, then run a small batch (10-20 rows) as a final verification before processing thousands.