CONTACT-CENTER OPERATIONS & IT
Answers about the signals around your integrations.
Clear answers for contact-center operations and IT teams investigating API reachability, sync freshness, and what Mendrook can see.
What does a failed API reachability check tell my team?
Mendrook checks the configured public HTTP or HTTPS health endpoint. A 2xx response is recorded as a success; a non-2xx response is an HTTP failure. Connection errors, timeouts, and targets that cannot be checked are recorded as failure types. The check records its result, elapsed time, and HTTP status when one is returned. This helps locate an endpoint problem, but it does not identify the underlying cause or prove that every part of a contact-center service is healthy.
How does Mendrook identify a stale sync?
A freshness check looks for a source status and last-sync time in the configured status endpoint. It recognizes the x-sync-status and x-last-sync-at response headers, or supported status and sync-time fields in JSON. A sync timestamp more than 15 minutes old is classified as stale; source statuses such as delayed, failed, or unhealthy are also stale. If the endpoint is unavailable or does not provide readable freshness metadata, the result is unreadable rather than assumed fresh.
What operational metadata does Mendrook monitor?
The monitoring view is based on integration identity and health signals: check time and outcome, HTTP or failure status, response time when available, sync source status and last-sync time, plus incident and action history. These signals help an operator see which configured connection or sync needs attention and review the recovery context their team has approved.
Does Mendrook ingest call recordings, transcripts, or conversation content?
No. Mendrook’s integration checks do not request or use call recordings, transcripts, or customer-conversation content. Reachability response bodies are discarded. Freshness checks use only recognized status and sync-time metadata from the configured source and discard the remaining response data.
Does a successful reachability check mean the whole contact center is healthy?
No. A successful result means the configured health endpoint returned a 2xx response when checked. It does not independently verify every contact-center service, carrier, network path, or call. Use the endpoint result alongside the monitoring and diagnostics your team already uses for those systems.
A CLOSER LOOK