Documentation Index

Fetch the complete documentation index at: https://aiagenttr.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​

CLAUDE.md

​

Project Overview

• All content is in Turkish (UTF-8 encoding)
• 15+ comprehensive documentation articles covering all platform features
• Two reference documents for form fields and validation rules
• 29 real platform screenshots
• Three main navigation tabs: Kullanım Kılavuzu (User Guide), Referans (Reference), AI Araçları (AI Tools)

​

Development Commands

​

Local Development

# Install Mintlify CLI globally (requires Node.js v19+)
npm i -g mint

# Start local development server at http://localhost:3000
mint dev

# Start on custom port
mint dev --port 3333

# Update CLI to latest version
mint update

# Validate links in documentation
mint broken-links

​

Deployment

​

Architecture & Content Structure

​

Configuration

• docs.json: Main configuration file controlling site theme, navigation, colors, and global settings
  • Theme colors: primary (#16A34A), light (#07C983), dark (#15803D)
  • Turkish navigation labels
  • Three main tabs: “Kullanım Kılavuzu”, “Referans”, “AI Araçları”
  • Contextual menu options include copy, view, ChatGPT, Claude, Perplexity, and Cursor integrations
  • Global anchors: Ana Sayfa (https://aiagenttr.com), Platform (https://platform.aiagenttr.com)
  • Support email placeholder: info@aiagenttr.com
  • Social media placeholders: Twitter/X, GitHub, LinkedIn

​

Content Organization

• getting-started/: Platform introduction, API key setup, dashboard, organization settings (4 files)
• voice-ai-agents/: AI agent creation, advanced configuration, tools, knowledge base, structured outputs, voice/transcript settings (6 files)
• customer-management/: Customer addition, bulk import, interactions, search/filtering (4 files)
• campaigns/: Campaign creation, execution tracking, analytics, call lists, DNC management (5 files)
• call-monitoring/: Call recordings and call analysis (2 files)
• phone-numbers/: SIP trunk setup and phone number management (1 file)
• pipeline-management/: Introduction, pipeline stages, ticket creation, ticket details (4 files)
• analytics/: Dashboard metrics, call statistics, campaign analytics (3 files)
• troubleshooting/: General issues, API connection issues, error codes reference, call errors (4 files)
• billing-credits/: Credit management, subscription plans, billing operations, payment methods (4 files)
• organization-management/: Organization creation, settings, user invitations, multi-org, API key management (5 files)

• reference/: Form fields reference and required fields table (2 files)

• ai-tools/: Mintlify integration guides for Cursor, Claude Code, and Windsurf (3 files - preserved from template for reference)

• images/: 29 real platform screenshots covering all major features
• logo/: Light and dark mode logos (need AI Agent TR branding)
• favicon.svg: Favicon (needs AI Agent TR branding)

​

Key Files

• index.mdx: Homepage with platform overview and feature cards
• quickstart.mdx: 3-step quickstart guide (account setup, AI agent creation, test call)

• docs.json: Navigation structure and theme settings (Turkish labels)
• CLAUDE.md: This file

• Template files (essentials/, api-reference/, original index.mdx) have been removed
• All content migrated from /Users/ugurgokdere/Developer/ai-call-center-platform-new/knowledge_base

​

Content Authoring

​

MDX Files

---
title: "Türkçe Başlık"
description: "Türkçe açıklama"
---

Content here in Turkish...

​

Mintlify Components

• <Card>, <CardGroup>: Feature highlights and navigation cards
• <Tabs>, <Tab>: Alternative views and options
• <Accordion>, <AccordionGroup>: FAQ sections and collapsible content
• <Steps>, <Step>: Step-by-step guides (heavily used throughout)

• <Info>: General information
• <Tip>: Best practices and recommendations
• <Note>: Important notes
• <Warning>: Warnings and critical information

• <Frame>: Image containers with placeholders

​

Platform Screenshots

<Frame>
  <img src="/images/page-name.png" alt="Türkçe açıklama" />
</Frame>

• /images/dashboard-overview.png — Kontrol Paneli ana sayfası
• /images/agent-create-form.png — Agent oluşturma formu
• /images/customer-create-form.png — Müşteri oluşturma formu (üst kısım)
• /images/customer-create-form-2.png — Müşteri oluşturma formu (kaydırılmış alt kısım)
• /images/campaign-create-form-3.png — Kampanya formu (haftalık takvim)

​

Navigation

{
  "tabs": [
    {
      "tab": "Kullanım Kılavuzu",
      "groups": [
        {
          "group": "Başlangıç",
          "pages": ["index", "quickstart", "getting-started/...", ...]
        },
        {
          "group": "Sesli Yapay Zeka Ajanlar",
          "pages": ["voice-ai-agents/..."]
        },
        // ... more groups
      ]
    },
    {
      "tab": "Referans",
      "groups": [...]
    },
    {
      "tab": "AI Araçları",
      "groups": [...]
    }
  ]
}

1. Create the MDX file in the appropriate directory with Turkish frontmatter
2. Add the file path (without .mdx extension) to the relevant group in docs.json
3. Ensure internal links use the format /category/filename

​

Internal Links

[Link text](/getting-started/platform-introduction)
[Another link](/voice-ai-agents/create-agent)

​

Platform-Specific Terminology

​

Turkish Terms

• AI Agent: Sesli yapay zeka asistanı
• Pipeline: İş akışı sistemi
• Ticket: Müşteri kaydı
• Stage: Aşama
• Campaign: Kampanya
• SIP Trunk: Telefon altyapısı
• E.164 Format: Uluslararası telefon numarası formatı (+905301234567)

​

Key Platform Concepts

• Voice AI assistants for automated calling
• Configurable with greeting messages, system prompts, and knowledge bases
• Can be assigned to pipelines
• Support escalation/forwarding to human agents

• Sales Pipeline: Lead → Qualified → Proposal → Negotiation → Won/Lost
• Service Pipeline: New → In Progress → Waiting → Resolved → Closed
• Tickets move through stages
• Drag-and-drop interface

• Automated outbound calling
• Requires: AI Agent, phone number, call list
• Configurable: concurrent calls, delay between calls, working hours

• VoIP infrastructure for phone calls
• Protocols: UDP, TCP, TLS, TLS/SRTP
• Gateways for redundancy

• E.164 phone format: +[country code][area code][number]
• Form validation rules documented in /reference/form-fields.mdx

​

Important Notes

​

CRITICAL: API Provider Confidentiality

• The voice AI provider is an internal implementation detail and MUST NEVER be exposed to customers
• All references to specific voice AI provider names have been removed from customer-facing documentation
• Use generic terms: “Platform API”, “API bağlantısı”, “AI servisi”, “ses altyapısı”
• API key setup is automatic - customers do not manually configure API keys
• NEW (Dec 30, 2025): Default API keys are automatically set when an organization is created
  • Users are redirected directly to dashboard after organization creation
  • No separate API key setup screen is shown
  • API configuration is handled automatically in the backend using internal voice AI credentials
• Documentation reflects automatic setup, not manual entry

​

Language and Encoding

• All content is in Turkish - preserve exact Turkish characters (ç, ğ, ı, ö, ş, ü)
• UTF-8 encoding is critical
• Test with Turkish text search to ensure proper encoding

​

Branding

• Logo and favicon need to be replaced with AI Agent TR branded versions
• Current files are placeholders from Mintlify template
• Maintain dual-mode support (light/dark)

​

Placeholders

• Replace all placeholder images with actual screenshots ✅ (29 screenshots captured March 2026)
• Update logo files (/logo/light.svg, /logo/dark.svg)
• Update favicon (/favicon.svg)
• Verify social media URLs in docs.json (Twitter/X, GitHub, LinkedIn)
• Confirm support email in navbar

​

Coming Soon Pages

• analytics/coming-soon.mdx
• troubleshooting/coming-soon.mdx

​

Migration Source

​

Screenshot Capture Technique

​

Prerequisites

• macOS with Screen Recording permission granted to the terminal app
• Chrome browser with Claude MCP extension installed
• Swift compiler (comes with Xcode Command Line Tools)

​

Step 1: Get Chrome CG Window ID

// Save as /tmp/get_chrome_window.swift
import CoreGraphics
import Foundation

let windowList = CGWindowListCopyWindowInfo(.optionOnScreenOnly, kCGNullWindowID) as! [[String: Any]]
for window in windowList {
    let ownerName = window["kCGWindowOwnerName"] as? String ?? ""
    let windowName = window["kCGWindowName"] as? String ?? ""
    let windowNumber = window["kCGWindowNumber"] as? Int ?? 0
    let layer = window["kCGWindowLayer"] as? Int ?? -1
    if ownerName.contains("Chrome") && layer == 0 && !windowName.isEmpty {
        print("\(windowNumber)|\(windowName)")
    }
}

​

Step 2: Navigate via Chrome MCP

​

Step 3: Capture Chrome Window Only

CHROME_WID=3694  # from Step 1
screencapture -x -l${CHROME_WID} docs/images/page-name.png

​

Step 4: For Scrollable Pages

​

Key Notes

• Window ID changes when Chrome restarts - re-run the Swift helper
• Grant Screen Recording permission in System Settings > Privacy & Security
• Grant Accessibility permission if using AppleScript to position Chrome
• screencapture -R (region) may fail but -l (window) works reliably
• Python Quartz module may not be available; Swift is more reliable on macOS

​

Troubleshooting

​

General Mintlify Issues

1. Remove CLI: npm remove -g mint
2. Upgrade to Node v19+
3. Reinstall: npm i -g mint

​

Turkish Character Issues

1. Verify file encoding is UTF-8
2. Check browser rendering settings
3. Ensure Mintlify version is up to date

​

Link Validation

• Broken internal links
• Missing pages
• Incorrect path references

​

Image Issues

​

Testing Checklist

• Run mint dev and verify all pages load
• Test navigation between all tabs and groups
• Verify Turkish content renders correctly
• Check all internal links work
• Run mint broken-links to validate
• Test search functionality with Turkish keywords
• Verify mobile responsiveness
• Check that coming-soon pages display properly
• Confirm contextual menu options work
• Test global anchor links (Ana Sayfa, Platform)

​

Future Enhancements

• Analytics documentation content
• Troubleshooting documentation content
• Video tutorials (if needed)
• API documentation (if platform exposes public APIs)
• Multi-language support (if international expansion)

​

Mintlify documentation

​

Working relationship

• You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
• ALWAYS ask for clarification rather than making assumptions
• NEVER lie, guess, or make up information

​

Project context

• Format: MDX files with YAML frontmatter
• Config: docs.json for navigation, theme, settings
• Components: Mintlify components

​

Content strategy

• Document just enough for user success - not too much, not too little
• Prioritize accuracy and usability of information
• Make content evergreen when possible
• Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
• Check existing patterns for consistency
• Start by making the smallest reasonable changes

​

Frontmatter requirements for pages

• title: Clear, descriptive page title
• description: Concise summary for SEO/navigation

​

Writing standards

• Second-person voice (“you”)
• Prerequisites at start of procedural content
• Test all code examples before publishing
• Match style and formatting of existing pages
• Include both basic and advanced use cases
• Language tags on all code blocks
• Alt text on all images
• Relative paths for internal links

​

Git workflow

• NEVER use —no-verify when committing
• Ask how to handle uncommitted changes before starting
• Create a new branch when no clear branch exists for changes
• Commit frequently throughout development
• NEVER skip or disable pre-commit hooks

​

Do not

• Skip frontmatter on any MDX file
• Use absolute URLs for internal links
• Include untested code examples
• Make assumptions - always ask for clarification