Case studyProfessional Services10 min read

PravaasOS: how an immigration consultancy stopped losing files in WhatsApp and started telling applicants the truth about their status

A multi-branch study-abroad and immigration consultancy was running thousands of applications through spreadsheets, shared drives and counsellors' phones. We built PravaasOS: a case management system, an applicant app, AI document checks and a counsellor workspace — 25 features that turned every application into a tracked, auditable file.

25
Features shipped
3
Apps & platforms
7
Team members
18
Weeks to rollout
PravaasOS applicant app and counsellor case dashboard
PravaasOS: every application a tracked file, every applicant informed.
01

A lost passport scan and a missed intake

PravaasOS's director told us the story that convinced her to rebuild the business's operations. A student's passport scan had been sent to a counsellor on WhatsApp, forwarded to a documentation executive, and then lost when that executive changed phones. The student's application missed the university's deadline and the whole intake was lost.

The consultancy had grown to several branches across the Tricity and nearby towns. Each counsellor ran their own spreadsheet, documents lived in shared drives with inconsistent folder names, and applicants — anxious about the biggest decision of their lives — called several times a week to ask where things stood.

“Every applicant's future sits in a file. We were keeping those files in WhatsApp.”

— PravaasOS's director
02

Following applications through a branch

We spent a week across two branches. A typical application passed through a counsellor, a documentation executive, an application filer and sometimes a finance executive for loans and fee payments. Each hand-off was a WhatsApp message or a verbal instruction.

The busiest periods — just before university intake deadlines — were when mistakes clustered. Documents with expired validity, mismatched names between passport and transcripts, and missing financial proofs were caught late, often by the university or the visa office rather than by the consultancy.

Where applications went wrong
  • Documents lost or duplicated across chats and drives
  • Name and date mismatches caught too late
  • No shared view of deadlines across branches
  • Applicants with no visibility, calling for updates
Team collaborating with laptops and notes
Mapping the hand-offs between counsellor, documentation and filing teams.
03

Designing a case file

At the centre of PravaasOS is the case: one applicant, one destination, one pathway — study, work or visit — with a checklist of documents and steps specific to that pathway. Counsellors configure the pathway once; the system generates the checklist, deadlines and reminders.

The applicant app shows the same case in plain language: what has been done, what is needed from them and what happens next. It deliberately never promises outcomes or timelines that depend on universities or visa authorities; it shows the consultancy's own steps and the dates it controls.

04

The team

A focused team with an AI engineer dedicated to document checks, the feature most likely to prevent the costly mistakes the director described.

1
Engagement lead

Branch discovery, pathway configuration and rollout timing.

1
Product designer

Case file design and applicant-facing language.

2
Full-stack engineers

Counsellor workspace, pathways engine and manager console.

1
Mobile engineer

Applicant app and document capture.

1
AI engineer

Document OCR, field extraction and consistency checks.

1
QA engineer

Pathway scenarios, permissions and data migration checks.

7 people in total, working as one team.

05

Decisions that mattered

Immigration files contain passports, financial statements and academic records, so data protection shaped several of these decisions.

01

One generic checklist or pathway-specific ones?

  • One checklist for everyone
  • Configurable pathways by destination and visa type

Our call: Configurable pathways by destination and visa type. Requirements differ sharply by destination and pathway. Configurable pathways let managers update requirements without developers when rules change.

02

How much should the applicant app promise?

  • Estimated visa decision dates
  • Only steps and dates the consultancy controls

Our call: Only steps and dates the consultancy controls. Decision timelines depend on universities and authorities. Showing only what the consultancy controls kept the app honest and avoided false expectations.

03

AI verification or AI checks?

  • AI declares documents valid
  • AI flags inconsistencies for staff to resolve

Our call: AI flags inconsistencies for staff to resolve. Staff remain accountable for every file. AI finds mismatches and expiries quickly; documentation executives decide what to do about them.

04

How to protect sensitive documents?

  • Shared drive with folder permissions
  • Encrypted storage with branch- and role-based access and full access logs

Our call: Encrypted storage with branch- and role-based access and full access logs. Passports and financial statements demand strict controls. Access is limited to the people working on a case, and every view is logged.

06

The 25 features

Everything that shipped across the counsellor workspace, applicant app and manager console.

Case management
One applicant, one file.
  • 01Case pipeline

    Every case by stage, counsellor and branch.

  • 02Configurable pathways

    Checklists and steps by destination and visa type.

  • 03Deadline tracking

    Intake and filing deadlines with early warnings.

  • 04Hand-off workflow

    Clear transfer between counselling, documentation and filing.

  • 05Case notes and history

    Every call, meeting and decision on the timeline.

Documents
Collected once, checked early.
  • 06Document requests

    Specific requests sent to applicants with due dates.

  • 07OCR field extraction

    Names, dates and numbers read from uploaded documents.

  • 08Consistency checks

    Name and date mismatches across documents flagged.

  • 09Expiry alerts

    Passports, tests and statements nearing expiry flagged.

  • 10Secure document vault

    Encrypted storage with per-case access.

Applicant app
Honest status, in plain language.
  • 11Case timeline

    What is done, what is needed and what is next.

  • 12Document upload

    Guided capture with quality checks.

  • 13Appointment booking

    Book counselling and document sessions.

  • 14Fee payments

    Consultancy fees paid online with receipts.

  • 15WhatsApp updates

    Key status changes delivered on WhatsApp.

Leads and branches
Running a multi-branch consultancy.
  • 16Enquiry CRM

    Leads from walk-ins, website and social media.

  • 17Counsellor workload view

    Active cases per counsellor for fair allocation.

  • 18Branch dashboards

    Enquiries, conversions and cases by stage per branch.

  • 19Commission and partner tracking

    Partner institution commissions tracked per case.

  • 20Management reports

    Performance across branches and pathways.

Controls
Protecting sensitive data.
  • 21Role- and branch-based access

    Staff see only the cases they work on.

  • 22Access audit log

    Every document view and download recorded.

  • 23Data retention rules

    Documents deleted after the retention period.

  • 24Consent records

    Applicant consent captured and stored.

  • 25Two-factor staff login

    Strong authentication for all staff accounts.

PravaasOS AI document check results
Document checks: mismatches and expiries caught before the application is filed.
07

Rollout between intakes

Timing mattered: we launched between intake seasons, when counsellors had time to learn. The pilot branch migrated its active cases first, with every document re-uploaded and checked. Branch by branch, the remaining offices followed, each after a hands-on session run by the pilot branch's lead counsellor.

  1. Weeks 1–2
    Discovery

    A week across two branches; hand-offs and failure points mapped.

  2. Weeks 3–4
    Design

    Case file, pathways and applicant app prototyped.

  3. Weeks 5–12
    Build

    Workspace, applicant app, document checks and CRM.

  4. Weeks 13–15
    Pilot branch

    Active cases migrated and re-checked.

  5. Weeks 16–18
    All branches

    Branch-by-branch rollout between intake seasons.

08

What we learned

Catching mistakes early is the whole value. Document checks that flag a name mismatch on day one prevent a rejected application months later.

Honest status beats optimistic status. Applicants trusted the app because it showed only what the consultancy controlled, instead of guessing at outcomes it could not promise.

Built with
  • Next.js
  • React Native
  • NestJS
  • PostgreSQL
  • Document OCR and LLM checks
  • WhatsApp Business API
  • AWS Mumbai
CTA Background

Building something like PravaasOS?

Bring the problem as it actually is, constraints included. You will get a straight answer on whether we are the right team.

View Our Work
AI-First Engineering
Secure & Scalable
Built to Deliver Impact
More case studies