> ## Documentation Index
> Fetch the complete documentation index at: https://help.cloudtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Why a call shows as "rejected" after ringing for only a second

> Why a call can briefly show as rejected, and how to check it wasn't lost.

> [!NOTE]
>
> If your CloudTalk app shows an incoming call as "rejected" after ringing for only a second, and the call doesn't appear in your history, this article explains what can cause it and how an admin can help.

**User level:** Admin

***

## Symptoms

You may notice one or more of the following:

* An inbound call rings on your device for less than a second, then shows as "rejected" or disappears

* The call does not appear in your personal call history, or appears as missed

* The caller stayed connected and was answered by a colleague

* It happens intermittently, not on every call

* It is not related to your internet connection or the caller's network

## Root Cause

A call that rings for only a moment and then shows as "rejected" is usually not a dropped call. The call stays connected and is handled by another agent. Common reasons your device shows it as rejected:

* Normal call routing between agents, where a call is offered to one agent and then moved to the next depending on the group's ringing strategy, and the skipped agent briefly sees a "rejected" status

* Your call-visibility setting, which can cause a call answered by a colleague not to appear in your personal history

## Step-by-Step Solution

### Confirm the call was not actually lost

Check whether the call was answered by another agent (for example in Analytics or with an admin who can see all calls). If the caller was connected and handled, the "rejected" status on your device reflects the call being routed elsewhere, not a dropped call.

### Confirm the agent's status

Make sure the agent's status is **Online** (not Away or Offline) when calls come in, so the queue routes calls to their device.

### Review the group's ringing strategy

Open the group settings and review the ringing strategy so it matches how you expect calls to be distributed between agents.

### Check your call-visibility setting

If the concern is that the call is missing from your history rather than being rejected, this depends on your call-visibility setting.

On a user's profile (**Users > \[user] > Edit > Advanced**), the **Global settings for visibility of calls and recordings** section controls this:

* When **The visibility of calls** is set to **All calls**, you can see calls across the account.

* When it is set to the more limited option, you see only your own calls plus missed calls from your assigned groups and numbers, so a call answered by a colleague may not appear in your history.

An admin can review or change this in **Users > \[user] > Edit > Advanced**.

![](https://mintcdn.com/cloudtalk/8FCfL6QWpEnHvO8c/images/help-center/articles/16255848/2c9e62bc2c0c-screenshot-2026-08-07-at-16-04-10.png?fit=max\&auto=format\&n=8FCfL6QWpEnHvO8c\&q=85\&s=2c74363ef683c2b577f933cb969e3a99)

### When to Contact CloudTalk Support

Reach out to [Support](https://support.cloudtalk.io/hc/en-us/requests/new?ticket_form_id=26305535257884) if calls continue to show as rejected after checking the above.

To speed up the investigation, include:

* The date, time, and timezone of a specific affected call

* The caller's number and the agent (or extension) it rang on

* Whether the call was answered by another agent

* The group (queue) involved

***

*Need help or have a question?* Just reach out through our [Support portal](https://support.cloudtalk.io/hc/en-us/requests/new?ticket_form_id=26305535257884) we're here for you.


## Related topics

- [Mobile App Not Receiving Calls](https://help.cloudtalk.io/en/articles/13130761-mobile-app-not-receiving-calls.md)
- [Call Log](https://help.cloudtalk.io/en/articles/10682286-call-log.md)
- [Outbound Calls Not Connecting](https://help.cloudtalk.io/en/articles/12867313-outbound-calls-not-connecting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.