Communications and AI operations¶
The Monitoring and Diagnostics area in General Administration contains several read-only histories. Each represents a different layer of a communication or AI workflow.
| Question | Use |
|---|---|
| What decision and access outcome occurred during a Virtual Agent interaction? | Virtual Agent Call Audit |
| Was an outbound directory, concierge, or Remote Guard phone route claimed and connected by the phone provider? | Phone Call Logs |
| Was an SMS queued, sent, delivered, rejected, or blocked, and what consent state was recorded? | SMS Audit |
| What happened across the Remote Guard call, operator, device, Immix, provider, and event timeline? | Remote Guard Diagnostics |
| How did the portal AI route a request, what capability ran, and was a query blocked or unsuccessful? | AI Chat Events |
These histories overlap by design. One visitor-assistance interaction can produce a Virtual Agent call, Remote Guard escalation, phone-provider route, AllBox activity, access-control event, and health event. Use call IDs, provider IDs, device IDs, event times, sites, and AllBoxes to correlate them.
Evidence boundaries¶
- Requested or queued means work was recorded, not that it completed.
- Accepted, sent, or connected describes a specific processing stage, not necessarily human receipt or the intended physical result.
- Access Granted means the workflow recorded a grant; verify the access-control transaction and physical outcome.
- A successful AI event means the request completed in its recorded mode; review scope and returned-row information before treating the answer as complete.
- A blank field means that value was not recorded in that history row. It is not automatically an error.
All screens are read-only. Correct policies, contact data, phone or SMS configuration, AllBox settings, access-control mapping, or AI permissions through their normal administration workflows.
Protect sensitive data¶
Communication histories can contain phone numbers, message content, call summaries, recording references, visitor context, provider identifiers, AI prompts and responses, and technical payloads. Export or share only what is required, use approved storage and support channels, and follow the organization's retention and privacy requirements.