Inspect a company to diagnose an incident
A company reports a problem. The Platform Operator inspects its configuration, channel state, technical state and operational metadata to find the cause — without seeing any message, customer data or AI source.
When this happens: Platform Operator opens host administration — Companies — [Company] — Inspection.
Step by step
- 1
Open the company in host administration and selects the Inspection tab.
Starts an inspection session and shows the Configuration section: settings, features, working hours, routing mode, AI mode and per-channel enablement, users per role, the Owner's name.
- 2
Open the Channels section.
Lists each channel connection: type, masked identifier, state, last successful sync, last error code and redacted message.
- 3
Sees the company's WhatsApp number in state *Error* with token expired since yesterday, and opens Technical state.
EasyCRM shows migration version, background-job failures of the last 7 days, delivery-error counts and storage used.
- 4
Click Copy diagnostic summary and attaches it to the vendor's incident record.
When the Platform Operator leaves the tab, writes one entry to the company's audit trail listing the sections viewed.
Other paths
Operational metadata
Open Operational metadata: conversation counts by status and channel, messages per day, failed sends, unassigned backlog — aggregates only.
If something goes wrong
Company unreachable
At step 2 the company's database cannot be reached. EasyCRM shows the connection error and the configuration stored on the host side only.
Good to know
- Inspection is read-only.
- No message text, attachment, customer field, template body, internal note, AI instruction or AI source is ever returned — the response contracts contain none.
- One audit entry per inspection session, in the company's own trail.