The short answer
Good visa agency software tracks every file and who it waits on, reads and cross-checks the papers, works through a bank statement row by row, drafts letters only from the evidence, gives clients a portal under your brand, limits what each staff member sees, and tells you where client data lives. Test each item on your own files before you buy.
Key takeaways
- Split the checklist into tracking, checking, drafting, client contact, team control and data, and score each part on your own files.
- A tool that only stores papers is a filing cabinet; ask whether it reads them and points each finding to a page.
- Bank statement reading is the hardest test: the software should rebuild the balances, find the salary and list every large credit.
- Drafts must be traceable to papers, approved by staff and then by the client, and never add a fact the file does not hold.
- Ask where client data is stored, who at the vendor can see it, when it is deleted and which AI models read it.
This visa agency software checklist is for owners comparing tools, whether you run five files a month or five hundred. A disclosure first: we make Visolv, one of the tools you might be comparing. The checklist below is the one we would want an agency to hold us to, and every item comes with a test you can run in a demo with your own papers.
It covers six areas: case tracking, paper checks, bank statement reading, letters and drafts, the client portal, and team roles with data protection. Languages and destination coverage close it out.
What should visa agency software actually do?
It should do four jobs: show where every file stands and who it is waiting on, read the papers and check them against each other, turn a checked file into drafts and an upload pack, and keep clients' personal data safe. A tool that does the first job only is a CRM. That is useful, but it will not catch the salary that differs between the job letter and the statement.
Vendors describe all four jobs in similar words, so words on a sales page tell you little. The only reliable test is a real file, ideally one you already filed and know well, with its weak points marked in advance. Bring that file to every demo and watch what each tool finds.
Case tracking: can you see every file's next step?
- Stages that match your work, from enquiry to decision, with the file's owner named at each stage.
- Who the file waits on and since when: the client, your caseworker, the visa centre or the embassy.
- Dates that bite: appointment dates, passport validity against the trip, residence permit expiry, and papers that will be too old by submission day.
- Late files flagged without anyone building a report, and reminders to clients who owe papers.
- Search by passport number or phone, so a returning client's old file and old refusal surface at once.
- Decisions recorded with reasons, so you can later see refusals by route, caseworker or source of the client.
Test: ask the vendor to load ten of your live files and show you, on one screen, which three need action today and why.
Paper checks: does it read the papers or just store them?
Many tools store uploads in folders and stop there. Reading means each paper becomes fields you can check: names, dates of birth, passport numbers, employers, salaries, balances, trip dates. Checking means those fields are compared across papers and against the application form, with every finding linked to the page it came from.
- Reads phone photos and scans, not just clean PDFs, including stamps and handwriting where they matter.
- Matches names across spelling variants, which matters for clients whose names are written in Arabic, Bangla, Hindi or other scripts at home.
- Compares trip dates with approved leave, and passport numbers on every paper that carries one.
- Flags papers that look edited from the file's own record, such as a bank statement produced in a word processor, and words the flag as a request for the original rather than an accusation.
- Notices when the same paper turns up in two different clients' files.
Test: bring a file with one mismatch you planted on purpose in a copy, such as a changed date on the form, and see whether the tool finds it without help. Our guide to spotting an edited bank statement explains what file metadata can and cannot show.
How should software read a bank statement?
Row by row, with the sums proved. The software should pull every transaction into a table, check that the opening balance plus credits minus debits equals each closing balance, find the salary or business income the other papers describe, and list every large or unusual credit that needs an explanation. A tool that only reads the final balance misses the questions an officer will ask.
Push it on the hard cases: a 300-row statement, a scanned statement with stamps across the figures, a statement in two currencies, a joint account. Ask what it does when the sums do not add up, because that is often the first sign a statement was rebuilt by hand. Then compare its output with your caseworker's own reading, using the method in our playbook on checking a bank statement for a visa file.
Letters and drafts: written from the papers?
A cover letter, itinerary or funds note drafted by software should say nothing the papers do not prove. Ask to click any sentence and see the paper and page behind it. Ask who approves the draft before it leaves the office, and whether the client sees and approves it too, because the applicant signs the form and answers for every word.
Watch for tools that write fluent, generic letters with confident claims about the applicant's plans. Officers read thousands of those. A shorter letter that ties each claim to a paper is worth more, which is the approach in our guide to a cover letter that matches the papers.
Client portal and messages
- Your brand, not the vendor's: your name, colours and number on every screen and message the client sees.
- Phone first: clients photograph papers on a phone, often on a weak connection, without installing an app or creating a password.
- A checklist per client, built from their route and situation, showing what is still missing.
- Approvals in the portal: the client reads and approves the cover letter and form answers before submission.
- Official messaging: if WhatsApp is offered, ask whether it runs on Meta's WhatsApp Business Platform or on an ordinary WhatsApp account on a staff member's phone. Our guide to WhatsApp for visa agencies explains the difference.
Team roles: who sees which client?
Every staff member should see only what their role needs. Look for separate roles for owner, admin, caseworker, branch and sub-agent, and test the boundaries: log in as a sub-agent and try to open another sub-agent's client. Ask for an activity log that shows who viewed, downloaded or changed each paper, and when.
Ask also how the price moves when you add staff. Per-seat pricing punishes the part-time reviewer who makes your files better; per-file pricing tracks your volume instead. Get the price in writing either way. Visolv does not charge for staff accounts, and each agency's per-file price is agreed on a short call; the pricing section explains how.
Where does the client data live, and who can see it?
Ask before anything else, because you hold passports, IDs and bank statements for every client. The questions: in which country are papers stored, who at the vendor can open them, when are they deleted after the decision, can you place a hold during an appeal, which AI models read them, and is client data used to train anything. Get the answers in the contract, not only in the demo.
Check them against the law where you work. The UAE's Federal Decree-Law No. 45 of 2021 sets rules on consent and on transferring personal data abroad (u.ae). If you handle EU residents' data, the GDPR expects a contract with any processor that covers, among other things, returning or deleting the data at the end.
Our own answers, so you can compare: Visolv stores papers in Bangladesh on the company's own servers, each agency sees only its own files, papers are deleted 90 days after the decision unless you place a legal hold, and every view, download and edit is logged. The AI reads papers with Anthropic's Claude models, and a person at your agency approves every file. If your rules require client data to stay inside your own country, that storage location matters, so raise it with us or any vendor early.
Languages and destinations: does it fit your clients?
Check three languages separately: the one your staff work in, the one your clients read in the portal, and the scripts on the papers themselves. Then ask which destinations the tool has checked against real submitted files, as opposed to rules typed from an embassy website.
Visolv's screens are in English and Bangla today. Its UK Standard Visitor pack was verified against a real file submitted through VFS in Dhaka; its other destination packs, including Schengen, Canada, Australia and US visitor visas, are marked draft until an analyst verifies them. Its checks were built on files from Bangladesh first, so an agency whose clients come from many countries should test it on those files before deciding.
The checklist on one page
| Area | Require | Red flag in the demo |
|---|---|---|
| Tracking | Stages, owner, who the file waits on, dates, late files | Status is a free-text field someone has to update |
| Paper reading | Fields from phone photos, each linked to its page | Papers sit in folders and nobody reads them |
| Cross-checks | Names, numbers, dates and money compared across papers and the form | Only checks that a file was uploaded |
| Bank statements | Every row, balances proved, salary found, large credits listed | Reads the closing balance and stops |
| Drafts | Each sentence tied to a paper; staff then client approve | Polished letters with facts the file does not hold |
| Client portal | Your brand, phone first, checklist, approvals | The vendor's logo on your client's screen |
| Roles | Owner, admin, caseworker, branch, sub-agent; an activity log | Everyone sees every file |
| Data | Storage country, deletion, holds, logs, AI models named in the contract | Vague answers, or nothing in writing |
| Coverage | Routes verified on real files; your staff's and clients' languages | Every country listed as supported, none verified |
How do you run a fair trial?
- Pick one route your team knows well and one caseworker to own the trial.
- Run ten or more new files through the tool and your usual process side by side.
- Before each file goes out, have a second person review it with your file check before submission, and note what the software caught that people missed, and the reverse.
- Count the time from first paper to a file ready to submit, with and without the tool.
- Decide on those numbers, not on the demo.
For how the pieces fit together in a working agency, read our buyer's guide to visa agency software, or see the file screens on how Visolv works. Whatever you choose, judge it on one result: whether your team, on its busiest week, catches more of what an officer will notice with the tool than without it.
Frequently asked questions
What is the difference between a visa CRM and visa agency software?
A visa CRM tracks enquiries, stages, payments and reminders: it tells you where a file stands. Visa agency software in the fuller sense also reads the papers, checks them against each other and the form, and produces the drafts and upload pack. Many agencies start with a CRM and find that the costly mistakes still happen inside the papers, which a CRM never opens.
Can visa software tell whether a bank statement is fake?
It can raise signals, not prove forgery. Useful signals include a statement produced in a word processor or phone PDF app, a file modified long after it was created, balances that do not add up row by row, and the same paper appearing in another client's file. Each signal is a reason to ask the client for the bank's own copy, never grounds to accuse them.
Should visa agency software use AI?
AI is useful for reading phone photos, pulling fields from papers and drafting from evidence, which is slow work for people. It should not make decisions. Ask the vendor which AI models read your clients' papers, whether client data is used for training, and where a person on your side approves each finding and draft before anything reaches the client or the visa centre.
How long should a visa software trial run?
Long enough to run at least ten real files on one route through the tool and your normal process side by side, which for most agencies means two to four weeks. Track what each method caught, how long files took and how clients used the portal. A trial on sample files the vendor provides tells you very little about your own clients.
What data questions should I ask a visa software vendor?
Ask in which country papers are stored, who at the vendor can open them, how long they are kept after the decision, whether you can place a legal hold, whether every view and download is logged, which AI models process them and whether client data trains anything. Ask for the answers in the contract, and check them against the data protection law where your agency works.
Does visa software need to support my clients' languages?
It needs to handle three things: the language your staff work in, the language your clients read in the portal, and the scripts on their papers, such as Arabic, Bangla or Hindi names and stamps. A tool that cannot match a name across scripts and spellings will either miss real mismatches or bury your team in false ones. Test it on your own clients' papers.
The Visolv team
Editorial team, PackMyCode Limited (Dhaka)
Visolv is software for visa agencies, made in Dhaka by PackMyCode Limited: an AI caseworker that reads and checks every paper in a client's file, writes the drafts and builds the upload pack under the agency's own brand. We write about what we see in real visa files from Bangladesh.
