# Call Logs

Reviewing historical interactions is executed natively inside the **Call Logs** search grid interface.

---

## Record Database Query Map

The flowchart below traces out how user filters locate specific records:

```mermaid
graph TD
    %% Filter
    subgraph SearchControls["Interface Query Bar"]
        InputSource["Enter Source string<br/>(e.g., '9001')"]
        SelectDate["Set Date Fences<br/>(e.g., Last 7 Days)"]
    end

    %% Store
    subgraph RecordsLedger["Historical Database tier"]
        DbStore[("Call Data Ledger DB<br/>(Stores CDR Rows)")]
    end

    %% Table Grid
    subgraph OutcomesGrid["Search Results Table"]
        RowCdr["Call Record Row<br/>(Details duration & hangup reason)"]
    end

    %% Links
    InputSource --> RecordsLedger
    SelectDate --> RecordsLedger
    RecordsLedger ==>|"Fetch Sorted Matrix"| OutcomesGrid

    %% Tailored Style System
    classDef srcToken fill:#0f172a,stroke:#38bdf8,stroke-width:2px,color:#fff,rx:6px,ry:6px;
    classDef ledToken fill:#312e81,stroke:#ec4899,stroke-width:2px,color:#fff,rx:6px,ry:6px;
    classDef gridToken fill:#1e293b,stroke:#a855f7,stroke-width:2px,color:#fff,rx:6px,ry:6px;

    class SearchControls,InputSource,SelectDate srcToken;
    class RecordsLedger,DbStore ledToken;
    class OutcomesGrid,RowCdr gridToken;
```

---

## Log Filtering rules

### 1. Status Disposition Sorting
Filter grid listings directly by standard completion descriptors (`Answered`, `Busy`, `Failed`) to locate dropoff issues quickly.

### 2. Detailed Duration Tracking
Search rows expose precise connection lifespans alongside billable seconds metrics to simplify customer auditing.