Audience: Admins, compliance owners, and operators in India evaluating/using Outbound Auto Dialer.
Goal: Understand availability, meet TRAI requirements, request activation, and (if approved) run a compliant outbound program.

Table of contents

• What is the Outbound Auto Dialer?
  
  
• Is the feature available to everyone?
  
  
• TRAI compliance at a glance
  
  
• Allowed vs. not allowed
  
  
• Prerequisites (evidence you must provide)
  
  
• Request access (step-by-step)
  
  
• If approved: run a compliant campaign
  
  
• Expected results & where to verify
  
  
• Troubleshooting & common denial reasons
  
  
• FAQs
  
  
• Support
  
  

What is the Outbound Auto Dialer?

The Outbound Auto Dialer places automated outbound calls to customers to play a recorded message (e.g., reminders, service alerts) or bridge to a live agent after answer—primarily for time-sensitive, consented, non-marketing updates.

Alt-text (Figure 1): Screenshot of “Outbound Dialer” card showing status Disabled with “Request Access” button.
Caption (Figure 1): The dialer is off by default and requires compliance approval.

Is the feature available to everyone?

No. It’s disabled by default for all accounts in India. Activation depends on TRAI compliance and internal approval.

TRAI compliance at a glance

Non-compliant robocalls/bulk IVR may lead to number blocking, blacklist, and account restrictions. Only consented, purpose-limited communications are eligible. (This article is informational, not legal advice.)

Allowed vs. not allowed

Prerequisites (evidence you must provide)

Prepare the following with your request:

• Opt-in proof (any of): web form screenshot + log, double-opt-in SMS logs, IVR recording snippet, CRM consent field export.
  
  
• Purpose statement: e.g., “utility outage alerts for existing customers only.”
  
  
• Target audience: customer segment/size; sample CSV with hashed numbers acceptable.
  
  
• Quiet hours policy (e.g., 9:00–18:00, Mon–Fri).
  
  
• Opt-out mechanism wording (DTMF “9” or reply STOP equivalent for future channels).
  
  
• Caller ID (CLI) to be displayed and your recording disclosure if applicable.
  

Sample consent text (copy-paste)

“I agree to receive automated service calls from about my account and service status. I can opt out anytime.”

Request access (step-by-step)

1. Contact your Account Manager or email support@myoperator.co.
   
   
2. Include the following (copy-paste template):
   
   

Subject: Request: Outbound Auto Dialer activation (Account )

Purpose: (e.g., outage alerts for existing customers)

Audience size: (e.g., 8,200)

Consent evidence: (links/screenshots/logs)

Quiet hours: (e.g., 09:00–18:00 IST, Mon–Fri)

Opt-out mechanism: (e.g., DTMF 9 → Do Not Call list)

Caller ID: (+91-XXXXXXXXXX)

Start date & expected volume: (e.g., 2K/day)

Point of contact: (name, phone, email)

3. Internal review: Compliance team validates consent, purpose, and risk.
   
   
4. Agreement: You’ll receive a UCC Agreement for e-signature.
   
   
5. Outcome: If approved, the dialer is enabled for the approved use only; otherwise you’ll receive remediation guidance.
   
   

If approved: run a compliant campaign

Upload audience (consented only)

phone,name,consent_date,purpose

+919812345678,Ananya Singh,2024-07-12,Outage Alerts

+919876543210,Rahul Mehta,2024-07-13,Appt Confirm

1. Create campaign → Transactional type → select Caller ID and quiet hours.
   
   
2. Audio: upload ≤25s message that states your brand and purpose, ends with opt-out cue (“Press 9 to opt out”).
   
   
3. Routing: choose agent-bridge after answer (optional), set max abandon rate (e.g., ≤3%).
   
   
4. Retries: at most 2 attempts, ≥10 min apart; stop on answer.
   
   
5. Suppression: enable DND/NCPR, internal Do-Not-Call, and previous opt-outs.
   
   
6. Launch and monitor delivery, connect, abandon, complaint metrics in Reports.
   
   

Expected results & where to verify

• Where to check: Reports → Outbound and Compliance → Suppression/Complaints.
  
  
• Healthy baselines (adjust to your use case):
  
  
• Delivery rate ≥ 95%
  
  
• Connect rate 15–35%
  
  
• Abandon rate ≤ 3% (if agent-bridge)
  
  
• Complaint rate ≤ 0.01%
  
  
• Audit trail: export consent logs, campaign config, audio hash, and call outcomes for audits.
  

Troubleshooting & common denial reasons

• Denied: Insufficient consent → Provide clearer opt-in artifacts or limit to existing customers.
  
  
• Denied: Purpose = marketing → Switch to WhatsApp/SMS templates with opt-in; voice promo not permitted.
  
  
• High complaints/labels → Shorten audio, improve identification, pause campaign, re-verify consent.
  
  
• Calls during quiet hours → Adjust schedule to local time zones.
  
  
• API usage flagged → Outgoing API cannot be used for bulk prerecorded voice without explicit approval.
  
  

FAQs

Can I use prerecorded audio?
Only for approved transactional purposes with consent and identification; otherwise prohibited.

Can I call prospects (non-customers)?
No. Only opted-in recipients for the stated service purpose.

Will MyOperator provide a list?
No. You are responsible for lawful data collection and consent record-keeping.

Is agent-bridge allowed?
Yes, when approved and staffed; keep abandon rates within limits and announce the brand at answer.

Support

Questions on eligibility or activation? Contact your Account Manager or email support@myoperator.co with Account ID, purpose, audience size, consent evidence, desired start date, and a contact person.