Writing guidance
Guidance rules tell your AI agent how to handle customer scenarios. Each rule has four parts:
- Title — Short name (e.g., "WISMO: Regional delivery timeframes")
- Description — WHEN to trigger: the topic or customer situation
- Instructions — HOW to handle it: specific scenarios and conditions
- Status — disabled, testing (playground only), or enabled (live)
Writing descriptions
The description defines WHEN this guidance triggers. It can be broad—specific scenarios go in the instructions.
Examples:
- "Customer inquiries about order location, delivery status, shipping updates, tracking information, or asking 'where
is my order'"
- "Customer wants to return an order or item"
- "Customer reports product arrived damaged, broken, or defective"
Writing instructions
Instructions tell the AI HOW to handle the situation. Break them into scenarios with clear conditions.
Example: WISMO with regional timeframes
Title: WISMO: Regional delivery timeframes
Description: Customer inquiries about order location, delivery status, shipping updates, tracking information, or asking
variations of 'where is my order/package/shipment.' Includes questions about delivery timing, order progress, or
shipping delays.
Instructions:
Scenario 1: No tracking available yet
Trigger: Customer asks for tracking and no tracking number is available
IF order created less than 2 business days ago:
- Inform tracking will be available once dispatched, usually within 24 hours
- Processing can take up to 3 business days during busy periods
- Advise customer to check back later
IF order created more than 2 business days ago:
- Apologize for the shipping delay
- Escalate to an agent
Scenario 2: Tracking available, not delivered
Trigger: Order has tracking but not yet delivered
Delivery timeframes by region:
- USA: 5-9 business days
- Canada: 5-9 business days
- UK: 5-7 business days
- Australia: 5-9 business days
- Other countries: 10-15 business days
Calculate expected delivery using order date plus regional timeframe.
IF order is on time:
- Share tracking information
- Assure: "We're closely monitoring every shipment to make sure it arrives safely."
IF order is behind by less than 2 business days:
- Advise customer to wait an additional 2 days due to possible delays
IF order is delayed by more than 2 business days:
- Escalate to an agent
Scenario 3: Marked delivered, not received
Trigger: Customer reports order marked delivered but not received
Ask customer to verify:
- Neighbor, roommate, or doorman accepting package
- Shipping address is correct
- Carrier contacted for delivery details
- Package left in discreet location
Next steps:
- Ask customer to wait 2 business days after posted delivery date
- Share tracking info and shipping address
- If verification done and 2+ days since marked delivered, escalate to agent
Example: Damaged item reports
Title: Damaged or defective item reports
Description: Customer reports product arrived damaged, broken, defective, or not as described
Instructions:
Check if customer has an order
- No match → Ask for order number and checkout email
If multiple items: Ask which specific item was damaged
Request photo(s) of damaged item(s) for assessment
Review damage policy and explain options:
"We stand behind the quality of our products. If your item arrived damaged:
- Report within 7 days of delivery for fastest resolution
- Replacement ships within 1-2 business days at no cost
- Full refunds available if replacement isn't preferred
- Keep the damaged item - no need to return unless requested"
Example: Influencer collaboration
Title: Influencer collaboration requests
Description: Customer inquires about partnerships, collaborations, sponsorships, influencer opportunities, or brand
partnerships
Instructions:
Step 1: Initial response
- Thank customer for their interest in partnering
- Express enthusiasm about potential partnership
- Ask about collaboration details: rates, content requirements, deliverables
Step 2: Assess partnership type
IF customer proposes paid partnership:
- Explain current partnership model available
- Outline affiliate program terms:
- Commission rate: [INSERT PERCENTAGE]
- Product allocation: [INSERT DETAILS]
- Content requirements: [INSERT DELIVERABLES]
Step 3A: Customer agrees to affiliate terms
IF customer agrees:
- Collect: name, email, phone, shipping address
- Label conversation: [INSERT LABEL]
Step 3B: Customer declines
IF customer declines:
- Thank them for their time
- Express openness to future partnerships
- Label conversation: [INSERT LABEL]
Key principles
1. Use scenarios for different situations
Don't handle everything in one block. Break into Scenario 1, Scenario 2, etc.
2. Include specific timeframes and thresholds
"2 business days", "5-9 business days", "within 7 days" — not "soon" or "quickly"
3. Define clear escalation rules
Be specific: "delayed by more than 2 business days" not just "if there's a problem"
4. Tell the AI what to DO, not what to SAY
- Good: "Apologize for the delay and share tracking"
- Bad: "Say: Dear customer, we sincerely apologize..."
5. Reference actions naturally
- "Escalate to an agent"
- "Resolve the conversation"
- "Leave private note about shipping damage"
- "Label conversation: [tag name]"
6. Include verification steps when needed
- "Request photo of damaged item"
- "Ask for order number and checkout email"
- "Confirm with customer it's the correct order"
Common mistakes
Missing scenarios Not covering different situations (tracking available vs not). Fix: Break into separate scenarios with
triggers.
Vague thresholds Using "if delayed" instead of specific timeframes. Fix: "Delayed by more than 2 business days"
No escalation rules AI doesn't know when to hand over to a human. Fix: Define specific conditions for escalation.
Over-scripting Writing full customer messages instead of instructions. Fix: Write instructions, not scripts.
Overriding defaults Trying to change automatic behaviors like pending status. These can't be changed via guidance. See
AI agent capabilities and actions for details.
Testing guidance
1. Set status to "testing" (active only in playground)
2. Simulate real conversations in playground
3. Test each scenario path
4. Adjust and re-test
5. Set to "enabled" when ready