# Calling in India (/guides/india-calling)

This page explains the rules CallMitra applies when it dials Indian numbers, and what stays **your** responsibility. Read it before you launch a campaign.

<Callout type="warn" title="Compliance is shared">
CallMitra enforces the calling window and do-not-call list you configure. It does **not** check the TRAI NCPR (DND) registry or DLT registrations for you. You are responsible for consent, for scrubbing your lists against the registry where the rules require it, and for setting hours that follow TRAI rules.
</Callout>

## Phone number formats [#phone-number-formats]

Store and send numbers in **E.164**: `+` followed by the country code and the number, with no spaces, for example `+919876543210`.

| Where | What CallMitra does |
| --- | --- |
| Leads created or updated with the API | Normalised to E.164: a bare 10-digit number becomes `+91…`; a number CallMitra cannot read is refused with `422` [`invalid_phone_number`](/errors/invalid_phone_number). See [Leads](/guides/leads#phone-numbers). |
| CSV and bulk lead imports | Numbers without a country code are treated as Indian (`+91`). A leading `0` or `00`, spaces and Excel's `.0` are cleaned up. |
| Dialing a lead | Separators are removed, then: 11 digits starting with `0` lose the `0`; 12 digits starting with `91` get a `+`; **10 digits starting with 6–9 become `+91…`**; anything else gets a `+` in front. |
| Your own phone numbers (caller IDs) | Must be E.164. CallMitra adds the `+` but never adds `+91` for you. |
| Do-not-call list | Accepts Indian mobile numbers only. |

<Callout type="warn">
Because a bare 10-digit number starting with 6–9 is dialed as an Indian mobile, always include the country code for numbers outside India.
</Callout>

CallMitra matches a caller or a do-not-call entry to your leads by the **last 10 digits** of the number, so `+91 98765 43210` and `09876543210` are the same person.

## Calling window [#calling-window]

Every campaign has its own calling window. Outside it, CallMitra does not start new automatic calls.

| Setting (in `settings`) | Default | Meaning |
| --- | --- | --- |
| `dialTimezone` | `Asia/Kolkata` | IANA time zone for the window and the daily limit. An unknown name falls back to UTC. |
| `dialWindowStart` | `10:00` | First minute calls may start (`HH:MM`, inclusive). |
| `dialWindowEnd` | `17:00` | Calls stop starting at this time (`HH:MM`, exclusive). `23:59` or `24:00` means midnight. |
| `dialDaysOfWeek` | every day | Days calls may start: `0` = Monday … `6` = Sunday. |

Send them in `settings` when you [create a campaign](/api-reference/campaigns/createCampaign) or [update it](/api-reference/campaigns/updateCampaign) (inside `campaignData.settings` with [create-with-leads](/api-reference/campaigns/createCampaignWithLeads)):

```json
{
  "name": "EMI reminders, November",
  "agentId": "AGENT_ID",
  "settings": {
    "dialTimezone": "Asia/Kolkata",
    "dialWindowStart": "10:00",
    "dialWindowEnd": "19:00",
    "dialDaysOfWeek": [0, 1, 2, 3, 4, 5]
  }
}
```

- A window can cross midnight (for example `22:00`–`06:00`), so double-check the values you send.
- A lead whose turn comes outside the window **waits**: CallMitra schedules it for the next time the window opens. It is never skipped because of the window.
- Callbacks a caller asks for are moved into the window too.
- There is no holiday calendar. Remove dates you should not call with `dialDaysOfWeek` or pause the campaign.

<Callout title="TRAI hours">
CallMitra does not force a 9:00–21:00 window. The console warns you when a window starts before 9:00 or ends after 21:00, but the campaign follows the hours you set. Keep commercial calls inside the hours the rules allow.
</Callout>

**Calls that ignore the window.** A manual call runs immediately, whatever the window says: a [direct call](/api-reference/calls/createCall), [`POST /api/v1/instant/call-now`](/api-reference/calls/callNow), [`POST /api/v1/leads/{lead_id}/call-now`](/api-reference/calls/callLeadNow) and the console's "Call now". Do-not-call is still enforced. Use them only for calls the person expects, such as an immediate callback request.

Check where a campaign stands with [`GET /campaigns/{campaign_id}/dial-status`](/api-reference/campaigns/getCampaignDialStatus): `inDialWindow`, `nextWindowOpenAt`, `skipReason` (`outside_window`, `outside_date_range`, `daily_cap`, `auto_dial_paused`, `first_call_delay`, `no_eligible_leads`, `inactive`) and a readable `lastErrorMessage`.

## Do-not-call [#do-not-call]

A lead on the do-not-call list (`dncOptOut: true`) is never dialed automatically.

**How a number gets on the list:**

- You add it: [`POST /api/v1/leads/dnc`](/api-reference/do-not-call/addDoNotCall) with `phones` (comma- or newline-separated Indian mobiles) and an optional `reason`, or bulk-update leads with [`POST /api/v1/leads/bulk`](/api-reference/leads/bulkLeadAction) and `action: "dnc"`. A number without a lead gets a new lead so the block sticks.
- The person asks during a call: if the caller says phrases such as "do not call", "stop calling", "remove me", "unsubscribe" or "opt out", or the post-call analysis classifies the call as an opt-out, the lead is marked do-not-call automatically.
- The carrier reports the number does not exist (marked with reason `invalid_number`; editing the lead's phone clears it).
- A data-erasure request.

The AI agent can add a number to the list but can never remove one. Remove a number yourself with `DELETE /api/v1/leads/dnc/{lead_id}`; read the list with `GET /api/v1/leads/dnc`. Adding and removing need a key whose user is a workspace manager.

**What it blocks:**

- Automatic dialing skips every lead whose number matches a do-not-call entry anywhere in your workspace (last 10 digits).
- A manual or direct call to a do-not-call number answers `409` [`number_on_dnc`](/errors/number_on_dnc).
- Pending callbacks for the lead are cancelled, and new ones are refused.
- Retries stop for calls that ended as an opt-out or a wrong number.

## Retries and daily limits [#retries-and-daily-limits]

| Setting (in `settings`) | Default | Meaning |
| --- | --- | --- |
| `retryAttempts` | `3` | Maximum attempts per lead, 0–10 (`0` means a single attempt). |
| `callInterval` | `7200000` (2 h) | Milliseconds between attempts, and the wait after no answer. |
| `retryIntervalNoAnswerMs` | not set | Wait after no answer, if different from `callInterval`. |
| `retryIntervalBusyMs` | `1800000` (30 min) | Wait after a busy line. |
| `maxCallsPerDay` | `50` | Calls this campaign may start per day in its time zone. |
| `maxConcurrentCalls` | 2 × the campaign's numbers | Live calls at once for this campaign (1–500). Accepted by the API but not yet listed in the reference schema. |
| `pacingSeconds` | `5` | Pause between dialing rounds. Accepted by the API but not yet listed in the reference schema. |

The daily limit is per campaign; a manual call on that campaign once it is reached answers `429` [`campaign_daily_cap_reached`](/errors/campaign_daily_cap_reached). Each phone number also has its own limit of simultaneous calls (by default 50 for Plivo numbers and 2 for others; see [Indian carriers](/guides/indian-carriers#limits)). See [Run a campaign](/guides/campaigns).

## Caller ID series [#caller-id-series]

Indian regulations reserve number series for commercial calling (140 for promotional and 1600 for service and transactional calls). When a campaign starts with a caller ID outside these series, the start response includes a warning. CallMitra never blocks the call for it: choosing the right numbers for your use case is up to you and your carrier. See [Indian carriers](/guides/indian-carriers).

## Recording notice and AI disclosure [#recording-notice-and-ai-disclosure]

These are agent settings, on by default:

- **Call recording** with a **recording notice**: the agent says a short notice in the call's language (for example "This call is being recorded.") before its greeting. The notice plays only when recording is on.
- **AI disclosure**: if the caller seems to believe they are talking to a person, the agent says once that it is an AI assistant. Asked directly, it always answers honestly.

CallMitra does not record consent for outbound calls. Keep your own record of how each person agreed to be called.