Smarter Agency Application Flow: Fewer Mix-ups, Cleaner Candidate Profiles

The details of how agencies submit applications on behalf of candidates might not sound like headline news, but when the flow breaks down, it creates real cleanup work for recruiting teams. Flo is the fastest shipping company in the legal talent industry, and part of what that means is staying close to the friction points that slow your day down, even the ones that seem small, and turning them around quickly.

The problem

Two related issues were showing up in agency-submitted applications, both coming from the same root cause: the application flow needed better guardrails to separate the agency contact from the candidate they were representing.

First, when an agency contact started an application and entered their own email address, the system could treat them like the candidate instead of routing them to the agency sign-in flow. That meant agencies could accidentally continue down the wrong path, which created confusion later for recruiting teams reviewing and tracking the submission.

Second, even when an agency contact was signed in correctly, they could still enter their own email address in the candidate email field. When that happened, the agency contact’s email could be saved to the candidate profile. Recruiting teams would then see the wrong email attached to the candidate record, making it harder to contact the actual candidate and creating messy data in the proces

What we shipped

We shipped two targeted improvements to the agency application flow.

• Automatic redirect to agency sign-in: When someone starts an application and enters an email address that matches an agency contact in Flo, the modal now recognizes it and redirects them to the agency sign-in flow. This check looks across Flo’s agency data, including agency contacts tied to any firm’s agency list and contacts in the unregistered agency contact database. No manual steps and fewer wrong-path submissions.
• Agency email omission on candidate profiles: Once signed in as an agency contact, if that contact enters their own email address in the candidate email field, the system now omits it instead of saving it. The candidate profile will show that no candidate email was provided, which is cleaner than showing the wrong address.

Why it matters

For recruiting teams, incorrect candidate data creates extra work. When an agency contact’s email ends up on a candidate profile, it can lead to bounced outreach, confusing communication chains, and time spent tracking down the right contact information. This update fixes the issue at the point of entry instead of leaving teams to clean it up later.

For agencies, the redirect makes the right path more obvious. It is easy to start in the wrong place if the system does not catch it, and a simple email entry mistake can create a messy submission record. This flow now helps agency contacts get routed correctly before that happens.

Clean data at the point of entry saves time everywhere downstream, and agency submissions are a place where that really matters. If you are seeing other spots in the agency workflow where mix-ups can happen, keep telling us. Specific feedback helps us keep tightening the flow.

If you want to see how Flo handles agency submissions alongside your broader recruiting workflow, you can book a demo and we will walk through it with you.