# calling_not_configured

- HTTP status: 422
- Retry: No
- Execution: not started
- Admin needed: yes

**Calling not set up.** The workspace cannot place calls until a telephony account is connected and a phone number is assigned to an agent for outbound calls. `details.reason` says which step is missing.

## What it means

The API returns HTTP 422 with `error.code` set to `calling_not_configured`. The default message is: "Calling is not set up for this workspace yet."

## Common causes

- `no_telephony_account`: no telephony account is connected.
- `no_phone_number`: no phone number has been added.
- `no_outbound_assignment`: no number is assigned to an agent for outbound calls.
- `not_enabled`: outbound calling has not been enabled for the workspace.

## How to identify it

Check the response status (`422`) and `error.code` (`calling_not_configured`). Branch on `error.code`, not on the message text: messages can be reworded, codes do not change within v1. Log `error.request_id` (also sent as the `X-Request-Id` header) so support can find the request.

## How to fix it

- Finish calling setup in the console (Numbers), then retry.

## Retry guidance

Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.

## Did anything happen?

This request was refused before any call was placed and before anything was charged.

## Idempotency

Nothing was done and the refusal is not stored under the Idempotency-Key. Fix the cause, then send the same request (with the same key if you sent one).

## Who can fix it

A workspace administrator usually has to act, in the RelationsAI console.

## When to contact support

If `details.reason` is `not_enabled`, write to [support@relationsai.com](mailto:support@relationsai.com). See [Support](/resources/support) for what to include (the `request_id`, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).

## Example error response

```json
{
  "error": {
    "code": "calling_not_configured",
    "message": "Calling is not set up for this workspace yet.",
    "details": {
      "reason": "no_outbound_assignment"
    },
    "request_id": "req_jfrwwfk6gd2a7vpxhhiwwztf",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/calling_not_configured"
  }
}
```

## Operations that can return this error

- [`POST /calls`](/api/calls#place-a-call): Place a call
- [`POST /campaigns/{campaign_id}/start`](/api/campaigns#start-a-campaign): Start a campaign
- [`POST /campaigns/{campaign_id}/resume`](/api/campaigns#resume-a-campaign): Resume a campaign

See all codes in the [error-code reference](/fundamentals/error-codes).