Skip to main content
The way you write AIP instructions directly impacts how Cevro handles conversations. Clear, explicit instructions lead to consistent behavior. Vague instructions lead to inconsistent results.

​
Be Explicit About Data

Don’t assume Cevro knows what values mean. Spell it out: Vague: 
Check if the withdrawal is pending.
Explicit: 
Check @withdrawalStatus.

Look for withdrawals where status is "pending" or "processing".

If found:
- Share the withdrawal amount and request date
- Explain: pending = submitted, processing = being reviewed

​
Include Decision Branches

Real conversations branch. Your instructions should too: 
If player provides a transaction ID:
- Look up that specific transaction
- Provide detailed status

If no transaction ID:
- List recent withdrawals from @recentTransactions
- Ask which one they mean

​
Define When to Escalate

Don’t leave escalation to chance. Be specific: 
Escalate if:
- Withdrawal has been pending more than 7 days
- Player reports a discrepancy between their records and system data
- Request requires manual override or exception

​
Use Separators for Sections

When instructions get long, use --- to separate distinct sections: 
Check @playerBalance for available funds.

---

If sufficient:
- Confirm withdrawal is possible
- Explain processing time

---

If insufficient:
- Explain the shortfall
- Suggest deposit options

​
Provide Examples for Ambiguous Cases

When a concept could be misinterpreted, show an example: 
When checking the player's bonus balance, reference bonus_balance, not wallet_balance.

Example:
wallet_balance: 100
bonus_balance: 0
Result: Player has 0 bonus balance (wallet balance is separate)

​
Mark Critical Instructions

Use “IMPORTANT:” to highlight must-follow rules: 
IMPORTANT: Never share account balance information before verifying the player's identity.

Check @playerBalance after authentication completes.

​
Test and Iterate

  1. Save your AIP (draft mode)
  2. Test in the Preview widget or Playground
  3. Review how Cevro interprets your instructions
  4. Refine based on actual behavior
If results don’t match expectations, the instructions likely need clarification. Cevro follows instructions literally—if something’s not working, make it more explicit.