> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What steps is MyOperator taking to prevent call drops and improve call quality/call clarity?

⚡ Quick answer: MyOperator uses advanced network routing to steer calls through less congested telecom circles, with real-time health checks and automatic failover. If a route degrades, we auto-reroute.

---

## Overview: What we do automatically

We continually optimise call paths so your callers connect with clear audio and minimal failure.

* Advanced network routing: Our system scores telecom routes using live metrics (e.g., call completion, error codes, ring/no-answer ratio, post-dial delay) and prefers lower-congestion regions when beneficial.
* Dynamic re-routing: If a route crosses a risk threshold (e.g., rising failures in a specific circle), traffic is shifted to a healthier alternate—often in nearby circles.
* Provider diversity: Multiple upstream telecom partners allow failover if a provider or region experiences instability.
* Continuous health checks: Background probes and rolling windows of production traffic keep route quality current.

Result: Lower drop rates and clearer audio without any action from you.

---

## How automatic routing works (at a glance)

1. Ingest metrics from live traffic (success rate, error codes, post-dial delay).
2. Score routes by region/provider.
3. Pick the best path (initial preference may favour lower-congestion circles).
4. Auto-reroute if a path degrades beyond the threshold.
5. Monitor after the shift and revert when the original routes stabilise.

---

## Quality monitoring & incident response

* 24×7 monitoring: We track route health across circles and providers.
* Threshold-based alerts: Anomalies (e.g., elevated network errors) trigger automatic mitigation and on-call review.
* Provider coordination: We file tickets and collaborate with carriers when their segments are impaired.
* Post-incident tuning: We update routing weights/allow-lists and add guardrails for recurrence.

During widespread events

* We may temporarily pin traffic to alternates while providers recover.
* If customer impact is material, we share status updates via Support.

---

## What we cannot control (and why it matters)

Even with optimal routing, issues can originate at the device or last-mile network:

* Phone switched off / out of coverage
* Unstable Wi-Fi calling / VoLTE settings
* SIM/device faults or call-blocking/DND

These conditions manifest as not reachable, one-way audio, or dropped after ring. Combining our routing with good device/network hygiene yields the best results.

---

## When and how to escalate to Support

If problems persist after auto-routing (and any manual route switch you tried):

1. Collect 2–5 recent sample calls that illustrate the issue.
2. Email [support@myoperator.com](mailto:support@myoperator.com) with:

  * Date/time (with timezone) for each sample
  * Last 4 digits of the caller/callee
  * Observed symptom (drop, echo, no audio, unreachable)
  * Patterns (location, device, provider)

3. Our team will review the server logs and coordinate with the providers. We will update you with the next steps accordingly.