Full-featured OBD Business Dialer System

OBD Calling App + Web Admin Panel – Full Source Code Required

I need a developer to build a complete OBD (Outbound Dialer) Calling System for business use.

The project must include:

- Android App
- Web Admin Panel
- Backend/API
- Database
- OBD/Cloud Telephony API Integration
- IVR/DTMF Response System
- Lead & Customer Management
- Telecaller Module
- Complete Reports
- Notifications
- Full editable source code

Main Requirement

Admin should be able to upload customer mobile numbers through Excel/CSV and run automated outbound voice-call campaigns.

The system should:

- Automatically call uploaded customers through an approved OBD/cloud telephony provider
- Play prerecorded voice messages
- Detect answered, busy, no-answer and failed calls
- Capture call duration
- Capture customer keypad/DTMF responses
- Generate interested/callback leads
- Assign leads to telecallers
- Maintain complete customer history
- Generate campaign and call reports

User Roles

Required roles:

- Super Admin
- Admin
- Team Leader
- Telecaller

Role-based permissions are required.

Web Admin Dashboard

Dashboard should show:

- Total campaigns
- Running campaigns
- Completed campaigns
- Total numbers
- Calls attempted
- Answered
- No Answer
- Busy
- Failed
- Interested customers
- Callback requests
- Total call duration
- Telecaller leads
- Campaign-wise performance

Customer Management

Customer details:

- Name
- Mobile Number
- Alternate Number
- Address
- PIN Code
- District
- State
- Product/Service
- Lead Source
- Campaign
- Language
- Status
- Remarks
- Assigned Telecaller
- Created Date

Admin must be able to bulk upload customers using Excel/CSV.

System should detect:

- Duplicate numbers
- Invalid numbers
- Existing customers
- New customers

OBD Campaign Management

Admin should be able to:

- Create campaign
- Select customer list
- Select voice recording
- Select language
- Select calling CLI/provider
- Schedule campaign
- Start campaign
- Pause campaign
- Resume campaign
- Stop campaign
- Configure retry attempts
- Configure retry interval
- View live campaign status

Campaign statuses:

- Draft
- Scheduled
- Running
- Paused
- Completed
- Cancelled

Voice Message

Admin should be able to:

- Upload prerecorded audio
- Preview audio
- Select recording for campaign
- Maintain multiple language recordings
- Replace/archive recordings

IVR / Keypad Response

Interactive OBD is required.

Example:

“Press 1 if interested.

Press 2 for callback.

Press 3 if not interested.

Press 9 to repeat the message.”

The system must automatically save the customer's key press.

Admin should be able to configure what each key means.

Multi-Level IVR

Where supported by the OBD provider, support multi-level IVR.

Example:

Press 1 – English
Press 2 – Bengali
Press 3 – Hindi

Then customer can select another option.

All responses must be stored.

Live Agent Transfer

Where supported by the selected telephony provider:

If customer presses a configured key, the call should be transferable/bridged to an available telecaller.

Track:

- Customer Number
- Campaign
- Key Pressed
- Agent Assigned
- Transfer Time
- Connected/Not Connected
- Agent Call Duration
- Final Disposition

Lead Generation

If customer presses Interested or Callback:

Automatically create a lead and send it to Admin/TL/Telecaller.

Lead should contain:

- Customer details
- Campaign
- OBD call date/time
- Key pressed
- Call status
- Previous history

Telecaller Module

Telecaller should see:

- New interested leads
- Callback requests
- Today's callbacks
- Follow-ups
- Pending leads
- Completed leads

Telecaller should be able to:

- Call customer
- Add remarks
- Select disposition
- Schedule follow-up
- Update customer status

Example dispositions:

- Interested
- Not Interested
- Callback
- Follow-up
- No Answer
- Busy
- Wrong Number
- Converted
- Other

Admin should be able to manage disposition options.

OBD Call Data

Store all available information returned by the OBD provider:

- Call ID
- Customer Number
- Campaign
- Calling CLI
- Call Date
- Start Time
- Answer Time
- End Time
- Ring Duration
- Connected Duration
- Total Duration
- Call Status
- Hang-up Reason
- DTMF Key Press
- IVR Path
- Provider Call ID

Retry System

Admin should configure automatic retry for statuses such as:

- Busy
- No Answer
- Network Failure

Options:

- Maximum retries
- Retry interval
- Retry status selection
- Stop retry after successful answer

Customer History

Every customer must have a permanent activity timeline including:

- Campaign assignment
- OBD call attempts
- Call results
- Voice message
- Key presses
- IVR responses
- Agent transfer
- Telecaller assignment
- Remarks
- Follow-ups
- Status changes
- Conversion

Old history must never disappear.

Reports

Required reports:

Campaign Report

- Total numbers
- Calls attempted
- Answered
- Busy
- No Answer
- Failed
- Interested
- Callback
- Not Interested

Call Report

- Customer Number
- Campaign
- Call ID
- Date/Time
- Duration
- Status
- DTMF response

IVR Report

- Press 1 count
- Press 2 count
- Press 3 count
- Other responses

Telecaller Report

- Leads assigned
- Calls
- Follow-ups
- Interested
- Converted
- Pending

Reports should be exportable to Excel/CSV, and PDF where required.

Notifications

Notifications required for:

- New interested lead
- Callback request
- Lead assignment
- Follow-up reminder
- Campaign completion/failure

OBD Provider Integration

The system should integrate with a legitimate OBD/cloud telephony provider.

Very important:

Do not permanently hard-code the complete system to only one provider.

Create a proper API integration layer so another provider can be integrated later.

Provider integration may include:

- API URL
- API authentication
- API Key
- CLI
- Campaign API
- Call Status Webhook
- DTMF Webhook
- Call Reports

API secrets must remain on the secure backend and must not be exposed inside the Android APK.

Android App

Android App should provide:

- Login
- Dashboard
- Interested Leads
- Callback Leads
- Customer Details
- Customer History
- Follow-Ups
- Notifications
- Calling
- Reports
- Profile

Large OBD campaigns should run through the backend/cloud telephony system and should NOT depend on keeping one mobile phone continuously running.

Security

Required:

- Secure login
- Password hashing
- Role permissions
- Secure APIs
- Database protection
- API credential protection
- Audit logs
- Backup facility

No hidden developer/admin access is allowed.

Telecom Compliance

The solution must use lawful and approved OBD/cloud telephony methods and comply with applicable Indian telecom/TRAI/DND requirements.

I do NOT want:

- Caller ID spoofing
- Hidden calling
- DND bypass
- Unauthorized SIM automation
- Illegal auto-dialing methods

Source Code & Ownership

I require:

- Complete Android source code
- Complete Web Admin source code
- Complete Backend/API source code
- Complete Database
- API integration source
- APK
- Play Store-ready AAB if applicable
- Build instructions
- Deployment documentation
- API documentation
- Database setup instructions

I require 100% ownership of the complete project and source code.

There must be:

- No developer-controlled account
- No hidden access
- No expiry
- No license lock
- No compulsory future payment to the developer

Third-party OBD/cloud calling charges should be clearly disclosed before project award.

Before Bidding Please Confirm

Please answer:

1. Have you developed an OBD/Outbound Dialer before?
2. Which Indian OBD/cloud telephony providers have you integrated?
3. Can you support prerecorded automated calls?
4. Can you capture Press 1 / Press 2 / Press 3 responses?
5. Can you support multi-level IVR?
6. Can interested customers automatically become telecaller leads?
7. Can customer calls be transferred to live agents where supported?
8. Can you provide campaign-wise call reports?
9. Can you provide Excel bulk upload?
10. Can the OBD provider be changed later?
11. Will you provide Android + Web + Backend + Database source code?
12. Will I receive 100% ownership?
13. What third-party monthly/per-minute charges will apply?
14. What is your total development price and delivery time?

Do not bid unless you can deliver the complete working system with full editable source code.