All details are fictional. The example checklist is chosen for the scenario, not a visa requirement list or a claim of support for a particular immigration route.
The proposed workflow
Capture the starting information
A fictional student applicant has supplied an intake answer and an academic transcript through the consultancy’s existing process.
Proposed action: The proposed case record would keep each fact linked to the answer or document it came from. Staff would confirm uncertain details.
Follow a team-approved checklist
For this example, the team wants an academic transcript and an offer letter. The offer letter has not arrived.
Proposed action: The proposed checklist would show the transcript as received and the offer letter as missing. Received would stay separate from reviewed.
Ask for a clearer copy
The transcript image is too blurred to read the completion date reliably.
Proposed action: A counsellor would mark it as needing a clearer copy and send a follow-up through the team’s agreed channel. Automated reminders are planned.
Resolve a conflicting detail
The intake answer says the course ended in June; the replacement transcript says July.
Proposed action: The proposed review queue would retain both sources. A counsellor would confirm the date and record the reason for the accepted value.
Review the handoff
The clearer transcript is reviewed, but the offer letter is still missing.
Proposed action: The proposed readiness view would explain what is outstanding, who owns the next step, and why the file is not ready for professional review.
What works today
Available means released. Discussed means agreed in conversation. Planned means not released. On small screens, scroll the table to see all columns.
| Capability | Status | What to expect and who does the work |
|---|---|---|
| Pilot requests and invitations | Available | Request a pilot, receive an invitation after approval, and sign in. An invitation does not yet open an applicant workspace. Staff responsibility: Ankan reviews requests and discusses fit with the team. |
| Workflow and pilot scoping | Discussed with your team | Choose one workflow and agree how information would enter and leave MatterZero. This is a conversation, not an automated onboarding service. Staff responsibility: Your team explains its current process; we agree responsibilities before starting. |
| Applicant intake and document uploads | Planned | The case workspace, intake forms, uploads, and document checklist are not available yet. No voice intake or language support is currently released. Staff responsibility: Continue using your existing intake and document process. |
| Source comparison and review queues | Planned | Linking facts to document pages or intake answers, flagging disagreements, and recording reviewer decisions are product designs under development. Staff responsibility: Counsellors and authorized professionals remain responsible for review. |
| Reminders and channel connections | Planned | MatterZero does not currently send applicant reminders or sync WhatsApp, email, or a CRM. Channels and supported languages must be agreed and demonstrated before use. Staff responsibility: Your team continues sending follow-ups through its existing channels. |
| Readiness, ownership, and handoff | Planned | Case readiness, task owners, overdue work, workload views, and export/import are not released. Tracking after file preparation is outside the current proposed scope. Staff responsibility: Agree an export and exit arrangement before starting a pilot; no export feature is promised today. |
Choose the first workflow together
Indian immigration consultancies are our initial audience. Student intake is one scenario to discuss, not a finalized product specialization. Our O-1A field notes describe a different preparation workflow; they do not establish support for student visa processing.
Before building a pilot around your team, we need to understand where information arrives, who enters it, who follows up, and what professional review requires.