Skip to main content

Testing the Documentation Portal

Escalation Email Testing​

The escalation flow sends support emails via Azure Communication Services to support@vibebrowser.app, which forwards to the support team via Cloudflare Email Routing.

Test via API (curl)​

curl -X POST "https://docs.vibebrowser.app/api/escalate" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "your-email@example.com",
    "message": "Test escalation",
    "transcript": [
      {"role": "user", "content": "Test question"},
      {"role": "assistant", "content": "Test response"}
    ],
    "pageUrl": "https://docs.vibebrowser.app/"
  }'

Expected response:

{
  "success": true,
  "ticketId": "MJS64RG9-31IW",
  "messageId": "MJS64RG9-31IW",
  "message": "Your message has been sent to our support team. We'll respond to your email shortly."
}

Test via UI​

  1. Go to https://docs.vibebrowser.app
  2. Click the chat widget button (bottom right)
  3. Click "Talk to a human"
  4. Fill in your email and optional context
  5. Click "Send to Support"
  6. Verify success message with ticket ID

Verify Email Delivery​

Emails are sent from noreply@vibebrowser.app to support@vibebrowser.app and forwarded via Cloudflare to dzianisvv+vibe@gmail.com.

Check inbox for email with subject: [Docs Support #TICKET_ID] New request from user@email.com

Chat API Testing​

curl -X POST "https://docs.vibebrowser.app/api/chat" \
  -H "Content-Type: application/json" \
  -d '{"messages":[{"role":"user","content":"How do I configure my API key?"}]}'

Health Check​

curl "https://docs.vibebrowser.app/api/health"

Email Routing Configuration​

To configure or update Cloudflare email forwarding rules:

export CLOUDFLARE_API_TOKEN="your_token"  # Needs "Email Routing Rules > Edit" permission
./configureCloudflareEmailForwarding.sh

Required token permissions:

  • Zone > Email Routing Rules > Edit (NOT "Email Routing Addresses")
  • Zone Resources: vibebrowser.app

Deployment​

cd services/docusarus

# Full deployment
./deploy.sh

# Skip steps if resources exist
./deploy.sh --skip-resources --skip-build --skip-index