AI Agent for Office Automation

# PROJECT REQUIREMENT: SOLARSEА AI BUSINESS AUTOMATION AGENT

**Company:** SolarSea Electrotech Solutions Pvt. Ltd.
**Location:** Pune, Maharashtra, India
**Deployment:** Office Windows Computer
**Expected Volume:** 100–300 PM Surya Ghar registrations/month and 5–20 MSEDCL applications/day.

## 1. Project Overview

SolarSea Electrotech Solutions Pvt. Ltd. wants to develop an AI-powered business automation agent that operates government portals through a web browser and automates repetitive administrative work associated with rooftop solar installations.

The system should function like a virtual office assistant that reads customer documents, fills online forms, manages verification workflows, tracks applications and communicates with customers.

The initial deployment will run on our office Windows computer, with the option to expand to multiple users later.

## 2. Main Requirements

### A. PM Surya Ghar Portal Automation

Official portal: https://www.pmsuryaghar.gov.in/

The agent should:

* Open and navigate the official portal.
* Assist with customer registration and application forms.
* Enter customer details and electricity consumer information.
* Identify mandatory fields and validation errors.
* Upload supporting documents where permitted.
* Handle OTP and CAPTCHA checkpoints through authorized verification.
* Resume the workflow after verification.
* Record application numbers, status and submission receipts.
* Track pending applications and required follow-ups.

### B. MSEDCL Application Automation

Official portal: https://wss.mahadiscom.in/wss/wss

Automate the following workflows wherever the portal permits:

1. New electricity connection applications.
2. Sanctioned-load enhancement applications.
3. Load reduction applications.

The agent should enter applicant details, premises information, consumer number, existing and proposed load, and other required fields.

It should validate entries, identify missing documents, upload files where supported and record application references.

The agent must check the actual portal workflow before implementation and pause when manual verification or authorization is necessary.

### C. AI Document Processing

The system should accept electricity bills, identity/address documents, PDFs and photographs.

It should extract relevant information, including:

* Customer name and address.
* Electricity consumer number.
* Sanctioned load and tariff category.
* Billing information.
* Other fields required by the selected application.

The extracted information must be presented for verification. Missing or conflicting information must be flagged rather than guessed.

### D. Dedicated Mobile-Number Management

SolarSea wants to investigate a system providing a separate, dedicated mobile number for each authorized PM Surya Ghar registration.

**Target number retention: At least 90 days per customer registration.**

Expected volume: 100–300 new registrations per month.

The developer must:

* Investigate legitimate Indian mobile-number and virtual-number providers.
* Confirm whether the official portal permits company-managed numbers.
* Verify that numbers can receive the required OTPs.
* Confirm exclusive number assignment and 90-day retention.
* Compare physical SIMs with suitable virtual-number services.
* Develop a number inventory linked to customer and application records.
* Track activation, assignment, expiry, renewal and release dates.
* Prevent accidental reassignment while applications depend on a number.
* Provide expiry alerts and an audit trail.

Do not procure numbers in bulk before successfully testing a small batch. Shared public SMS inboxes and number arrangements that compromise account security are not acceptable.

### E. OTP and Verification Workflow

The system should:

* Detect when OTP verification is required.
* Identify the registered destination where permitted.
* Notify the authorized operator when verification is pending.
* Integrate with approved SMS services where feasible.
* Pause and resume the browser workflow.
* Record verification status without retaining OTPs in ordinary logs or databases.

The customer must authorize the registration arrangement and retain appropriate access to their account. The system must respect official portal rules and must not bypass CAPTCHA, authentication or other security controls.

### F. AI Calling and Customer Follow-ups

Provide an optional AI voice agent supporting Marathi, Hindi and English, subject to provider capabilities.

Features should include:

* Outbound lead calls and inbound customer support.
* Collection of missing application information.
* Document reminders.
* Quotation follow-ups.
* Application-status updates.
* Site-visit scheduling.
* Escalation to a human employee.

Calling and messaging must comply with applicable Indian telecom, consent and privacy requirements.

### G. Customer Dashboard

Develop a dashboard showing:

* Customer details and documents.
* PM Surya Ghar registration status.
* MSEDCL application status.
* Assigned mobile number and retention deadline.
* Pending OTP verification.
* Missing documents.
* Applications awaiting review.
* Submitted applications and reference numbers.
* Failed applications and required corrections.
* Upcoming follow-ups and expiry alerts.

Provide Start, Pause, Resume, Review, Approve Submission and Retry controls.

The system must maintain an application history and support Excel/PDF report exports.

## 3. Technical Requirements

The developer may propose an alternative architecture, but should evaluate:

| Component | Preferred technology |
| ------------------- | ---------------------------------------------------------- |
| Operating system | Windows 10/11, subject to support |
| Backend | Python |
| Browser automation | Playwright |
| AI integration | OpenAI API |
| Dashboard | Streamlit or React |
| Database | SQLite for prototype; PostgreSQL for multi-user deployment |
| Document processing | PDF extraction and OCR |
| Notifications | Approved SMS, email and WhatsApp integrations |
| Storage | Secure local storage or approved cloud storage |

The application should recover from common browser errors, detect unexpected portal changes, prevent duplicate submissions and capture screenshots when workflows fail.

## 4. Security and Human Approval

The system must include:

* Secure staff authentication and role-based access.
* Encryption and restricted access to customer documents.
* Secure handling of portal credentials.
* Audit logs for application changes and submissions.
* Customer authorization records.
* Secure backups and recovery procedures.
* Configurable document-retention policies.

Human approval must be required before final submission involving customer declarations, payments or legally significant actions.

The agent must pause when it encounters CAPTCHA, OTP verification, missing information, conflicting details or an uncertain submission result.

## 5. Implementation Phases

**Phase 1 — Feasibility:** Inspect the actual government portals, document their workflows, verify automation restrictions and investigate number providers.

**Phase 2 — Prototype:** Build the customer database, document reader, dashboard and one MSEDCL form-filling workflow.

**Phase 3 — Portal automation:** Add remaining MSEDCL workflows and PM Surya Ghar registration/application assistance.

**Phase 4 — Advanced features:** Add number management, OTP workflow, AI calling, notifications and reporting.

**Phase 5 — Testing and deployment:** Test security, application accuracy, duplicate prevention, recovery and office installation.

## 6. Required Deliverables

The developer must provide:

1. Working Windows application and installation instructions.
2. Complete source code.
3. Customer database and dashboard.
4. Browser automation workflows.
5. Document extraction module.
6. Number inventory and retention management.
7. OTP verification workflow.
8. Application tracking and reports.
9. Administrator and user manuals.
10. Testing and security documentation.
11. Backup and recovery instructions.
12. Third-party service and recurring-cost estimates.
13. Maintenance and support proposal.
14. Source-code ownership and intellectual-property transfer as agreed in the contract.

## 7. Acceptance Criteria

The project will be accepted when the agreed workflows can:

* Extract and validate customer information.
* Fill the relevant government portal forms.
* Handle required verification checkpoints.
* Submit applications after authorization.
* Verify and record application references.
* Prevent duplicate submissions.
* Track dedicated-number assignments and retention dates.
* Resume interrupted workflows.
* Export reports and maintain an audit trail.

The developer must demonstrate working functionality on the actual portals before final acceptance.

## 8. Commercial Proposal

Please quote separately for:

**Option 1:** Core system — document processing, customer database, dashboard, MSEDCL automation and PM Surya Ghar assistance.

**Option 2:** Complete system — all core features plus dedicated-number integration, OTP workflow, AI calling, WhatsApp and advanced reporting.

Include development cost, timeline, API charges, mobile-number service costs, maintenance charges, assumptions and milestone-based payment terms.
#Final Objective
Build a reliable SolarSea AI office assistant that automates repetitive customer-registration, electricity-connection, load-enhancement and solar-application activities while maintaining customer authorization, data security and human oversight sensitivity.