How is the OBD campaign different from Click ‘O’ Call in MyOperator?
Quick answer
- Click ‘O’ Call = one-to-one, agent-initiated bridge for instant conversations.
- OBD (Outbound Dialer) = one-to-many, automated calls triggered by a campaign schedule or API. Pick Click ‘O’ Call for urgent, personal follow-ups; choose OBD for bulk, consistent outreach with optional key-press transfers.
When should I use this guide?
Read this if you need to decide which outbound feature best fits your use case (sales follow-up, reminders, marketing, surveys, OTP) and you have access to the MyOperator Web Dashboard or OBD API.
1. Feature overview
Outbound Campaign = placing outbound calls to customers. It is of 2 types:
- IVR-based
- Automated IVR menu drives the call flow.
- Use cases:
- Auto-connect customers to Sales for a new-policy briefing.
- Broadcast policy updates without live agent interaction.
- Peer-to-Peer
- System instantly bridges an agent with a specific customer.
- Use case: targeted OBD call linking a customer directly to their Account Manager.
2. Prerequisites & roles
Role | Click ‘O’ Call | OBD |
|---|---|---|
Admin | Enable feature, set policies | Create campaigns, manage API keys |
Manager | Initiate calls, view logs | Start/monitor campaigns |
Call Agent | Initiate from records | View results; (start if permitted) |
General requirements
- Valid +91 phone numbers and calling credits.
- Browser pop-up permission (Click ‘O’ Call).
- API key & webhook (OBD).
- Consent for outreach; respect DND & quiet hours.
Prerequisites for Campaign Run:
- Opt-in proof is required.
- Management approval is necessary to run the campaign from the OBD panel.
Watch the video walkthrough
Alt text: Video demo
3. Side-by-side comparison
Aspect | Click ‘O’ Call | OBD |
|---|---|---|
Primary goal | 1-to-1 live talk | 1-to-many automated outreach |
Trigger | Manual click | API |
Throughput | One call per click | Bulk, concurrent (plan-based) |
Personalisation | Live agent context | IVR/TTS; transfer on DTMF |
Reporting | Per-call activity | Campaign KPIs (attempts, connects, DTMF) |
Best for | Demos, escalations, hot leads | Payment reminders, promos, surveys |
Setup effort | Minutes | Moderate (audio, routing, schedule) |
Compliance | Manual consent | Opt-in list, quiet-hour rules |
4. Decision guide
- Need a personal call right now with one customer? → Click ‘O’ Call
- Need to reach hundreds+ with a consistent message? → OBD
Still unsure? Use OBD if:
- Automation via API is required.
- Key-press routing is okay.
- Agents shouldn’t join every call.
5. Real-world scenarios
Scenario | Volume | Urgency | Integration | Best pick |
|---|---|---|---|---|
Sales rep calls a hot lead | 1 | Immediate | CRM | Click ‘O’ Call |
Payment reminders | 1 000+ | Scheduled | ERP / API | OBD |
Webinar follow-up | 50–200 | 24 h | CSV | OBD (route to agents) |
Escalated support ticket | 1 | Immediate | None | Click ‘O’ Call |
6. How to place a Click ‘O’ Call
- MyOperator panel → Call logs → open the Contact record.
- Click Click ‘O’ Call.
- Select caller ID if prompted → Start.
- Agent and customer are bridged; talk live.
- Add notes/disposition on hang-up.
Alt text: click on the call button and call will get initiated
Alt text: pop for the successful call initiation
7. How to launch an OBD campaign
A. API (dynamic)
Steps to create Campaign on the Panel:
- Dashboard → Outbound › Campaigns › Create.
- Select the campaign type: Peer-to-Peer or IVR-based.
- Name the campaign, upload audio or select TTS.
- Set schedule, retries, quiet hours, and concurrency.
- For IVR-based, fill the time and days of the campaign, then create the IVR.
- Use the three-dot menu to adjust settings (e.g., select the fixed DID). Save changes.
Alt text: Click on call section under the left menu of the panel
Alt text: Click on Create new option at top right side of the screen.
Alt text: Select the type of campaign you want to create from Peer to Peer or IVR-based.
Alt text: Enter the required details in the form like Name, time, and days as per the requirement. And save it.
Alt text: select the fix DID as shown in the screenshot and save the changes.
You are done with the campaign. Now, to run the campaign, you need to hit the API.
curl --location 'https://obd-api.myoperator.co/obd-api-v1' \
--header 'x-api-key: oomfKA3I2K6TCJYistHyb7sDf0l0F6c8AZro5DJh' \
--header 'Content-Type: application/json' \
--data '{
"company_id": "606455f68ed4f652",
"secret_token": "22b397cab9b1f38d8ad78617861eaf7132c707b5cb30d17b275a1356c7cfd14a",
"type": "1",
"number": "+919810496768",
"number_2": "+917703980159",
"public_ivr_id": "68749ed88306c330"
}'
8. Validation & expected outcomes
Metric | Click ‘O’ Call | OBD |
|---|---|---|
Success signal | Call shows in the activity log | Dashboard shows attempts/connects |
Recording/notes | Yes | Optional (transfer leg) |
Webhook | n/a | JSON result to callback URL |
9. Troubleshooting
Symptom | Likely cause | Fix |
|---|---|---|
Click ‘O’ Call button is greyed | Missing permission/credits | Ask owner for permission |
Click ‘O’ Call rings the agent only | Customer number invalid | Verify number/carrier route |
OBD campaign won’t start | Future schedule or no audio | Start now; upload audio or enable TTS |
High OBD “unanswered” | Throttling too high | Reduce CPS; call during local hours |
Still blocked? Email support@myoperator.com with campaign ID (if OBD), time window, and sample numbers.
Keywords: OBD vs Click ‘O’ Call, outbound dialer, automated calls, one-to-one bridge, DTMF transfer, campaign dialer, call throttling, quiet hours, E.164
Updated on: 12/01/2026