How can MyOperator clients purchase DIDs from multiple locations for outgoing calls?

How can MyOperator clients purchase DIDs from multiple locations for outgoing calls?

⚡Quick answer -

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?

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. 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. Who must approve the primary use-case?

Role

Name

Area

Sales

Mihir

Revenue

Support

Garima

CS Ops

Enterprise Business Group

Nitin

EBG

SAP & Channel

Ashish

Partner Mgmt

Tech Support will not process any ticket lacking these approvals.

3. Prerequisites & evidence checklist

Item

Mandatory?

Attach to Jira?

HOD-signed email or PDF approval from the four approvers

✅

✅

Client BAN (Billing Account Number)

✅

✅

Business type (LLP, Pvt Ltd, Govt, etc.)

✅

In description

Purpose paragraph (why outbound calls are needed)

✅

In description

Front-end screenshot: page where contacts are captured

✅

📎

Back-end / DB screenshot showing the same contact record

✅

📎

OTP / DCA consent flow description

✅

In description

Nature of services offered

✅

In description

Signed MyOperator Outgoing-Calls Agreement

⬜ (provided later)

📎

4. Step-by-step process

image.png

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

Detailed actions

  1. Secure approval:
    1. 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.
  5. DID group activation
    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 MyOperator panel, go to Manage -> DIDs -> Add DID

image.png

Alt text: Adding DIDs for multiple locations after verification

5. Sample Jira ticket payload

{
"clientName": "Acme Pvt Ltd",
"BAN": "BAN-987654",
"businessType": "Pvt Ltd",
"primaryUseCase": "Customer-support callbacks for e-commerce orders across India.",
"purposeOfOutgoingCalls": "Transactional order updates and delivery confirmations to registered customers.",
"natureOfServices": "Online retail of consumer electronics.",
"frontEndURL": "https://acme.com/contact-us",
"otpDCAFlow": "Contact number is verified via SMS OTP before being stored in CRM. Consent text: 'I agree to receive transactional calls from Acme.'",
"requestedLocations": ["Delhi", "Mumbai", "Bengaluru"]
}

6. 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.

7. Compliance reminders (TRAI, DND, DCA)

  1. Transactional-only: Feature must never be used for promotional calls.
  2. DND-safe: Transactional calls to DND numbers are allowed only if the Called Party has provided explicit, recent (< 6 months) consent.
  3. Digital Consent Acquisition (DCA): OTP or equivalent verification must be logged and stored.
  4. Zero-tolerance: Any breach suspends outgoing calls immediately; legal action may follow against the onboarding owner.

8. Glossary

Term

Meaning

DID

Direct-Inward Dialing number used for outbound calls.

DND

“Do Not Disturb” registry for blocking unsolicited calls.

UCC

Unsolicited Commercial Communication; promotional in nature.

TRAI

Telecom Regulatory Authority of India.

DCA

Digital Consent Acquisition—OTP-based consent capture.

BAN

Billing Account Number assigned to the client.

Keywords: purchase DIDs in different locations, MyOperator outgoing calls, multi-location DID process, TRAI DND compliance, Jira ticket template