Suspected false answer supervision (FAS) on a route

FAS is when a call is answered by the network rather than the person you called - you get billed for a "conversation" that never happened. We actively monitor for it, and we want your reports.

How FAS shows up in your data

• Uniform durations: clusters of calls to one destination with suspiciously similar billed durations, often short.
• Answer with no audio, or answer followed by ringback (the call "answers" and then you hear ringing - the give-away that supervision was faked upstream).
• Answer-seizure ratios that look too good: a destination suddenly "answering" nearly every call is not a quality improvement.
• Customer complaints of being billed for calls the far end never received.

What we do about it

Our monitoring profiles answer patterns and durations per destination, and routes showing FAS signatures are pulled from the mix while we investigate. Confirmed FAS traffic is disputed with the supplier and credited per the terms of your agreement - FAS is a billing-integrity issue, not a quality preference.

How to report it

1. CDR extract for the suspect calls: called number, connect time, duration, release cause.
2. Call out the pattern you see (identical durations, answer-then-ringback, and so on).
3. Note whether your own customer reported it - end-user complaints are strong corroboration.

Send it marked for the carrier desk as suspected fraud. FAS reports jump the queue, and the dispute window in your agreement applies from the traffic date - so report early even if you are still gathering examples.