A CRM that was born inside a visa consultancy.
Generic CRMs were built to sell software. Copilot was built by a team that answers visa clients every day and got tired of bending a sales tool to fit the job.
Where it came from
First a system built to order. Then a CRM built around the case.
The consultancy behind Copilot first commissioned a CRM of its own. It had a board, a WhatsApp robot logged in on a phone, and a deadline module nobody managed to configure in five months. Every change meant opening a ticket and waiting for a developer.
Copilot is the second attempt: an open CRM core reshaped around the visa case. The client card, the services catalog, official WhatsApp, deadlines the manager edits alone. The team that uses it every day is the team that decides what changes next.
What changes for you
The process is yours. The tool bends, not the team.
A generic CRM calls your client a deal and your visa type a product. Every field is a workaround and every stage a compromise. Copilot starts from the vocabulary of the job: service, applicant, stage, agent, deadline, follow-up.
When the consulate changes a requirement on Tuesday, the manager adds the field on Tuesday. When a new visa type starts selling, it becomes a service the same afternoon. No ticket, no developer, no waiting for a vendor's roadmap.
Who it is for
For the team that answers the client, not the software.
Copilot is for visa consultancies where the same few people sell, collect and follow the case, and where one lost message costs a client. It is not for teams that want to build software. It is for teams that want to answer faster.
It runs in the browser, at the desk and on the phone. Roles decide who sees what. The code is open, so nothing you put in gets locked in: export the CSV any day and take it with you.
