⚡Quick answer –

Expect two charges per DID: a one-time setup fee of Rs 1,000 and a monthly rental of Rs 200. Taxes are additional. Buying in bulk, choosing vanity numbers, or purchasing mid-cycle can change the total—see details below.

–By default, every new MyOperator account receives just one or two DID groups. To unlock additional locations, the Account Manager (AM) must secure cross-functional approval (Sales, Support, EBG, SAP / Channel), raise a Jira ticket with specific evidence (front-end & back-end screenshots, consent workflow, business use-case), route the MyOperator Outgoing-Calls Agreement for signature, and let Tech Support validate everything. Only after these steps will Tech Support expose extra DID groups in the client’s panel.

When should I use this guide?

Read on if you want to:

(a) budget for a new DID,

(b) Compare single vs. bulk purchases, or

(c) understand proration, renewals, and edge-case fees before clicking “Confirm” in the dashboard.

Use it if you are onboarding a brand-new client or an existing client requesting more outbound call locations, and you need to:

• understand mandatory approvals,

• know exactly what to attach to the Jira ticket, or

• Brief the customer on TRAI/DND compliance before enabling the feature.

1. DID Pricing (Single & Bulk)

1.1 Price components

Note: If deleting the existing DID and then purchasing a new one, 1000 one-time cost only

(For example – Changing a purchased DID from Noida to Bangalore isn’t free—you must buy a new Bangalore DID, billed at ᠭ1,000 + GST.)

1.2 Cost calculator

Single DID, Month 1: Rs 1,000 setup + Rs 200 rental = Rs 1,200 (+ taxes)

Bulk (n DIDs), Month 1: (Rs 1,000 + Rs 200) × n = Rs 1,200 × n (+ taxes)

From Month 2 onward: Rs 200 × n (+ taxes)

Copy-paste formula:

1.3 Where to see the price before you buy

Dashboard → Manage → DIDs → Add New.

Filter by region/prefix and select a number.

Review the setup fee, rental, and tax line on the confirmation pop-up.

Click Confirm only if the total matches your budget.

1.4 Billing & renewals

• Setup fee is charged once at purchase; rental is billed every month.

• First-month rental may be prorated if your account bills on calendar months.

• Releasing a DID stops future rental; the current billing period is not refunded

• Invoices/receipts: Dashboard → Billing → Invoices.

1.5 Edge cases—when prices change

• Compliance/KYC: Some regions need documents; fees appear only after approval.

• Vanity or premium numbers: Higher setup and/or rental fees apply.

• Bulk-purchase discounts: Available for large orders—request a quote.

• Port-in vs. buy: Porting an existing number follows a separate fee table.

• Usage charges: Call minutes, recordings, and add-ons are billed separately.

1.6 Examples

1.7 Troubleshooting

Common questions:

• “Price for my region is blank.” → Number out of stock or KYC pending—open a ticket.

• “Charged but DID inactive.” → Check Provisioning status; attach invoice in ticket.

• “Invoice higher than expected.” → Review taxes, proration, or add-ons.

2. Purchasing DIDs from Multiple Locations

2.1 Default behaviour (one-location limit)

Newly-created clients see only 1–2 DID groups in their panel and can dial transactional calls—even to DND numbers—without location choice.

No other location DIDs groups are shown until the procedure in this FAQ is completed.

2.2 Who must approve the primary use-case?

Tech Support will not process any ticket lacking these approvals.

2.3 Prerequisites & evidence checklist

2.4 Step-by-step process

Alt-text: “Workflow from client request to DID activation.”

DETAILED ACTIONS

1. Secure approval: Obtain written “+1” from Mihir (Sales), Garima (Support), Nitin (EBG), and Ashish (SAP and Channel).
2. Raise a Jira ticket
1. Use component: Outgoing DID | New Location
2. Paste the JSON payload (see next section) in the description.
3. Attach the two screenshots (front-end & back-end).
3. Tech Support validation
1. Checks completeness & TRAI alignment.
2. Sends the Outgoing-Calls Agreement PDF to AM.
4. Agreement execution
1. AM emails client agreement
2. Client e-signs; AM re-uploads the PDF to the same Jira ticket.

2.5 DID group activation & expected outcome

1. Tech Support confirms signatures.

2. Makes additional DID groups visible in the client’s panel.

3. Jira is resolved; AM notifies the client.

Expected outcome: Client can now select DIDs from the newly approved locations in their MyOperator dashboard.

• After verification, from the MyOperator panel, go to Manage → DIDs → Add DID

Alt text: Adding DIDs for multiple locations after verification

2.6 Sample Jira ticket payload

2.7 What if the request is rejected?

The ticket will be declined if:

• Any of the four approvals is missing or unclear.

• Screenshots do not match each other (front-end vs back-end).

• The consent flow is older than 6 months or lacks OTP/DCA proof.

• The client intends to use the feature for promotional or UCC calling.

Clients failing compliance will keep only the default DID group, and outbound calling may be suspended entirely for repeated breaches.

2.8 Compliance reminders (TRAI, DND, DCA)

• Transactional-only: Feature must never be used for promotional calls.

• DND-safe: Transactional calls to DND numbers are allowed only if the Called Party has provided explicit, recent (< 6 months) consent.

• Digital Consent Acquisition (DCA): OTP or equivalent verification must be logged and stored.

• Zero-tolerance: Any breach suspends outgoing calls immediately; legal action may follow against the onboarding owner.

2.9 Glossary

Keywords - MyOperator DID pricing, setup fee, monthly rental, bulk DID cost, DID taxes, purchase DIDs in different locations, MyOperator outgoing calls, multi-location DID process, TRAI DND compliance, Jira ticket template