Debug Guide

Step 1: Reproduce

1. Call your agent
2. Try to trigger the misunderstanding
3. Note exactly what you say and how agent responds

Step 2: Review Transcript

1. Go to Conversations
2. Find the problem conversation
3. Read transcript carefully:
   • What did customer actually say?
   • What did transcription record?
   • What did agent respond with?

Step 3: Identify Issue Type

Step 1: Identify Wrong Information

Document what agent said, what correct information should be, and source of correct information.

Step 2: Locate Source in System

Step 3: Check Information Age

When was knowledge base last updated? If >3 months old, review all entries for accuracy.

Step 4: Test Fix

After updating, call agent immediately, ask the same question, verify correct answer.

Step 1: Measure Latency

Use stopwatch to measure time from your question to agent starts speaking.

• Normal: 1-2 seconds
• Acceptable: 2-3 seconds
• Problematic: >3 seconds

Step 2: Identify Bottleneck

Step 1: Check Connection Status

Integrations → Calendar: Status should show "Connected" (green). If red, click "Reconnect" and re-authorize.

Step 2: Test Integration

Step 3: Debug Permissions

Check Google Calendar or Outlook permissions. Permission level should be "Make changes to events" or "Full access to calendars".

Step 4: Debug Booking Logic

Create explicit test: Manually create calendar event for tomorrow at 2:00 PM, then try to book same time through agent. Agent should say "not available".

Step 5: Debug Time Zone Issues

Verify Ayra calendar integration time zone, your calendar time zone, and agent business hours time zone all match.

Step 1: Verify Integration Active

Integrations → CRM: Status should be "Connected" (green), Last sync should be recent (within last hour).

Step 2: Check Activity Log

Integrations → CRM → Activity Log: Look for failed attempts (red), click to see error details.

Step 3: Debug Field Mappings

Integrations → CRM → Field Mappings: All required fields must be mapped. Check if Ayra collects data for these fields.

Step 4: Debug Data Collection

Review conversation transcripts: Check Contact Information section for email, phone number, name. If data missing, agent didn't collect it.

Step 5: Debug Permissions

Check CRM API permissions. HubSpot needs crm.objects.contacts.write, Salesforce needs "Access and manage your data (api)".

Step 1: Test with cURL

Expected: JSON response with data. Errors: 401 (Invalid key), 403 (Insufficient permissions), 429 (Rate limited), 500 (Server error).

Step 2: Debug Authentication

Verify API key format: Live key (sk_live_...), Test key (sk_test_...). Check key permissions in Settings → API Keys.

Step 3: Debug Request Format

Validate JSON format, check Content-Type header is "application/json" for POST/PUT requests.

Step 4: Debug Rate Limiting

Check response headers: X-RateLimit-Remaining. If 0, wait until X-RateLimit-Reset time. Implement exponential backoff in your code.

Step 5: Debug Timeouts

Set appropriate timeouts (30-60 seconds). Test endpoint response time. If timing out, check network latency or reduce request size.