Portals
A login that only shows things is a nicer way of waiting.
The weekly status call is not caused by a lack of visibility. It is caused by a client who has no way to give you an answer without writing an email — so the answer waits for the call, and the call becomes you reading a spreadsheet aloud.
- Client
- Northline Logistics
- Mode
- Agency · client requisition
- Bill / pay rate
- ₹1,85,000 / ₹1,42,000 per month
- Exclusivity
- Exclusive until 14 Nov
- Submission cap
- 5 · three used
- SLA to first shortlist
- 7 days
- Max notice period
- 60 days
What they can do, not just see
Four decisions, made in the product.
Your client shortlists a candidate. Rejects one — and cannot file that rejection without giving a reason. Asks for more information. Leaves a comment. Each one notifies the recruiter who owns the role, so the answer reaches a person rather than a dashboard.
The shortlist is wired to the masking: contact details stay hidden until they shortlist, so the decision and the disclosure are the same act.
- They pick the interview slot —
You post the windows that work; they choose one and the interview confirms. Two people on their side cannot pick different slots for the same interview.
- They score the interview —
A structured scorecard with an overall recommendation, refused on interviews that have not happened, and filed separately by each person on the account who sat in.
- Compare up to five, side by side —
Against the role's own mandatory and preferred requirements — showing which ones each candidate does not meet, which is the column a deck never has.
- Portal users have roles, and cost you nothing —
Admin, approver, reviewer — so a procurement contact and a hiring manager are not the same login with the same powers. And none of them is billed as a seat, so inviting four people from a client is a decision about their process rather than about your invoice.
The screen almost nobody else has
Your client signs off the invoice.
An agency's worst month is not a lost search. It is four placed candidates and an invoice nobody at the client will confirm, because confirming it is somebody's inbox problem and disputing it is a phone call they keep postponing.
So the invoice is an action in the portal. Approve or dispute, confirmed by a code sent to them, and the code is bound to that one invoice and that one action. A dispute has to carry a written reason.
- Client opens the invoicestep 1The placement behind it, the agreed fee, and the terms it was raised under.
- They press approve — or disputestep 2A code is emailed to them. It is tied to that one invoice and that one action, so a code minted to approve cannot be turned into a dispute.
- Approvedstep 3Recorded against their name, with the time. Your finance team is not chasing a confirmation email.
- Or disputed, in writingstep 4A dispute cannot be filed without a stated reason. Which means the disagreement starts as a sentence you can act on rather than a silence you have to interpret.
What they are allowed to know
Masked before anyone configures anything.
Salary hidden. Contact details hidden until they shortlist. Sub-vendor identity hidden. Those are the defaults, not a checklist you have to remember on the day you onboard a client.
And what the client sees was frozen when you submitted it — name, email and the resume they download are the submission-time snapshot. Editing a candidate's profile next month does not quietly rewrite what your client reviewed in September. The file they download is a redacted copy, not the original.
- Blind review, if you want it —
One setting anonymises the candidate and your own recruiters, for clients who want the shortlist judged without either name.
- You can see what they did —
An activity feed and a feedback log on the client record — useful four months later, when the question is who rejected whom and why.
The numbers, pointed the other way
Their analytics measure them.
The funnel and volumes for their roles, yes. But the metrics that change a relationship are the ones about the client: median days to their first response, median days to their first shortlist, and how many of your submissions are sitting unanswered right now.
They see those. You see the identical figures, computed once. Which turns you never send us anyone good into a conversation with two columns in it.
- A tracker report on a schedule —
Monday morning, Friday evening, or the first of the month — or off. It arrives as a workbook attached to the email, with the columns you chose, and you can override them for a one-off run.
- Messages against the thing they concern —
Threaded on the requisition or the submission, visible to the rest of your team when the owner is on leave, and notified by whichever channel that person chose — respecting their quiet hours.
Asked by every agency that has been burned
Scope, limits and the awkward ones.
›Can a client see another client's candidates?
No. Access is scoped to their own account, and a submission is visible only to the client it was made to.
›Can we hide salary and contact details?
They are hidden already. Salary is off by default, contact details stay hidden until the client shortlists that person, and a sub-vendor's identity is never shown. Blind review goes further and hides your recruiters too.
›Do portal users cost us seats?
No. Client, vendor and candidate portal users are excluded from the seat count — on the subscription page, in the seat-cap alerts, and in the bill itself. Charging a recruiter for inviting a client to look at their own shortlist would be a strange way to price a portal.
›Who do we invite, and what can they do?
You invite them, with a role — admin, approver or reviewer. A reviewer can read and comment; an approver can sign off the invoice.
›Can they browse past tracker reports in the portal?
No. Each report arrives as an attachment on the email. There is no client-facing archive of previous ones, and we would rather say that than let you promise it.
›Can the client approve the offer before it goes out?
Not today. There are settings that read as though they gate this; they are marked in the product as not yet enforced, and we are not going to demo them as though they are.
›What happens when a client disputes an invoice?
It is recorded against their name with the reason they wrote, and it lands on the invoice rather than in somebody's inbox. Which is the first time in most agencies that a dispute has a timestamp.
Book a demo
Log in as one of your clients.
The test is not whether it replaces your spreadsheet. It is whether your client would answer you in it.
- Reject a candidate and watch it refuse without a reason
- Shortlist one and see the contact details appear
- Put five candidates side by side against the role
- Approve an invoice and check the code is tied to that action
- Open their responsiveness numbers, then open yours