Interview Signal for RPO: running a client's interviews in the client's own format

RPO teams use Interview Signal on a Team account to run each client's interviews in the client's own shape: an admin builds one submittal template per client from that client's write-up format, recruiters save each requisition as a role with the client's job description, required questions and scorecard areas, and every screen ends in a write-up in that template. Nothing joins the client's Zoom, Microsoft Teams or Google Meet meeting, because the app captures audio on the recruiter's computer. As of October 2026 Team costs $59 per seat per month, or $49 billed yearly, with a three-seat minimum; there is no ATS integration, so notes go into the client's system by copy and paste. This describes version 0.9.10.

How does an RPO team set up a client program?

1. Agree the ground rules with the client first: whether an AI note taker may be used on its candidates' calls, the notice wording, and where the interview record must live. The RPO note taker guide has a per-client policy grid.
2. Build the client's template. In the web account, an admin opens "Templates", presses "Duplicate and edit" on the closest built-in, rewrites the headings, order and fixed wording to match the client's format, names it after the client program, and presses "Save template". Only admins can do this. See submittal templates for every placeholder.
3. Save each requisition as a role. Put the client or program in the "Role title", paste the client's job description, and type the intake notes into "What the client actually wants". Choose the client's template under "Submittal template", and the program's "Interview language" if it runs outside English.
4. Mirror the client's interview guide. Generate the kit, then add each question the client requires with "Add a question" and tick "Must ask" on the ones it insists on; questions you add or reword are kept when you regenerate. Rename the scorecard areas to the client's competencies, set each "Weight" from 1 to 3, and fill the rubric lines.
5. Press "Save role". "Role saved. Every recruiter on the team sees it." Every recruiter on the program now asks the same questions against the same rubric.

What does the client see, and what stays with the RPO?

The covering note from "Email to client" signs off with the email address the recruiter signs in with, and an {{interviewer}} placeholder in a template fills with it too, so check both if a program runs under the client's name. The security page lists every subprocessor, and a data processing agreement is available on request.

How do notes get into the client's ATS?

The Bullhorn and JobAdder notes, the CSV row and the covering email take availability and pay from bold "Available" and "Compensation" labels near the top of the submittal. None of the built-in templates has a bold "Compensation" label, so if a client wants pay in the note, give its template one or type it in. "Add CSV row" appends to one submittals.csv per computer, which has a "Role" column but no client column, another reason to put the client in the role title. Details in exports.

How does a delivery lead keep quality consistent?

• The coaching report. The web account's "Coaching" tab shows, for the week before, each recruiter's interviews, must-asks covered, follow-ups used, scorecard completeness and average length. It is per recruiter across the account, not per client, and counts an interview only once its submittal has been copied or exported. See the coaching report guide.
• The home screen. Each role reads as a pipeline, such as "4 interviewed · best 8.4 · 1 sent" (an example), and admins can switch the week line between "Mine" and "Team". Press / to search by candidate, role or client.
• "To finish". Unnamed, unscored and unsent interviews wait on each recruiter's home screen; an unsent one stays for seven days.
• Panels. Several interviewers can split one candidate's questions, but a join code works only for people signed in to the same account, so a client's hiring manager needs a seat on the RPO's account to join. Only questions marked as asked are shared, not scores, and never transcripts. See panel interviews.

What happens when a recruiter rolls off a program?

An admin removes the seat under "Members" and the recruiter is signed out within about a minute; seats are named to one email address, and a seat can go to someone new by removing one person and inviting another. Their interviews stay on their computer, because Interview Signal never held a copy, so make pasting the write-up into the client's ATS part of finishing every screen. Seats can be added mid-month, charged pro rata. See the Team plan guide.

What does Interview Signal not do for RPO?

• No ATS integration, including with a client's enterprise system; everything is pasted or attached.
• No per-client separation inside an account. Everyone on it sees every role and template, and reporting is per recruiter.
• Templates are text. No client logo or letterhead, and admin work happens in the web browser.
• Desktop only, on Windows 10 or 11 or macOS 13 or newer; phone screens must run through the computer; no video.
• In person, the scorecard needs you: quotes cannot be verified, so areas come back "Probe further" and scores above 5 are capped until you add your own. See in-person interviews.
• A newer product with few public reviews; pilot it on one program, with the client's approval.

Which plan fits an RPO?

Team: as of October 2026, $59 per seat per month, or $49 per seat per month billed yearly ($588 per seat), with a minimum of three seats and unlimited interviews. A seat is one recruiter who runs interviews. The annual plan is one invoice, paid by card; for purchase orders or other terms, the pricing page says to write to [email protected]. For the RPO model itself, see what is recruitment process outsourcing; to see the app first, watch the walkthrough on the Try it page and download the app.