Paradox vs Screened: applications, screening and scheduling
The deciding question is whether you need help getting applicants into interviews or help reviewing the applications already there.
· 10 min read

A store needs applicants to finish a short application and book time with its manager. An office hiring team already has 240 unread CVs. Both ask for better screening, but they are buying help with different work.
Put Paradox on the shortlist when you need conversational applications and scheduling. Compare an ATS screening add-on when your application process works but CV review or repeated first calls do not. You may need both; first establish which delay each would remove.
Compare the two purchases as different jobs: an end-to-end frontline hiring platform versus a narrower screening add-on. We build Screened, and a narrower screening product will not suit every frontline hiring problem.
What Paradox’s text-to-apply workflow does
Paradox’s Conversational Apply product page describes applications started through a keyword or QR code, channels including SMS and WhatsApp, screening against configured requirements and returning information to an existing system.
For a Singapore rollout using WhatsApp, ask to see that channel with your proposed ATS, country and account configuration. A demonstration over SMS does not establish how your WhatsApp application, reminders and replies will work.
Conversational application collection starts before there is a completed application to review. Keep that task separate from assessing the CVs already in your ATS.
Paradox can connect to an existing ATS or supply its own Conversational ATS, available through Workday. This is not a simple choice between replacing your ATS and keeping it.
Ask which arrangement the proposal includes. That determines what you must set up, which system holds the hiring record and what you would need to move if you leave.
Compare the work you would buy
Before reviewing a complete candidate journey, separate the two purchases:
| Buying question | Paradox conversational application route | Screened screening add-on |
|---|---|---|
| Where does the change begin? | When a person finds a role and starts the application conversation. | When an application needs CV assessment or a selected applicant needs a first interview. |
| What should the demonstration prove? | The application reaches the right location and a suitable manager appointment can be arranged. | The reviewer receives accurate, useful evidence for the right job and can act on it. |
| What remains a separate question? | Whether the configured questions assess the experience this role requires. | How applicants apply by text and how later human interviews are scheduled. |
This compares the proposed workflows, not the full feature lists of either company. Paradox’s Chat to Apply guide explicitly distinguishes a basic screening conversation from a complete integrated application. Ask which version is in the quote.
For the store vacancy, follow a candidate from the poster or job ad through the application, shift clarification and manager booking. For the office vacancy, follow an existing application through CV review, any necessary experience questions and the manager’s next decision.
Neither route is mandatory for that job category. A store role may need a practical exercise; an office role may need only a short call. The comparison should show which work the purchase changes, not prescribe extra stages.
Checking availability is different from assessing experience
“Can you work the advertised opening shift?” and “Tell me how you investigated a customer problem” ask for different kinds of information.
The first establishes a practical condition. The second explores experience. A chat that collects several practical answers can be useful without being a detailed assessment of job performance.
For the store role, “Are you flexible?” leaves the candidate guessing. State the location, days and hours:
This vacancy covers Monday, Wednesday and Friday, 6.30 am–2.30 pm, at our Riverside store. Can you work all three shifts? Let us know which hours need discussing; you do not need to explain your personal circumstances.
These are example shifts, not a recommended roster. If the reply is “Monday and Friday, but not Wednesday,” the manager has a specific coverage question to resolve. A general yes to “flexible” would not reveal it.
For the support role, a useful first interview might ask how the applicant checked a disputed invoice, what they personally investigated and when they involved a specialist. A CV alone may not contain that detail.
Screened’s phone and browser interviews collect answers and follow-ups, then return a transcript, topic summaries and an assessment for your team to review. That does not establish a ready-made text-to-apply or WhatsApp application route. Any messaging capability in your proposal needs its own demonstration.
Find out where people are actually getting stuck
Start with a group of applicants for one role and a defined period. Count people or applications consistently, and distinguish a conversation that started from an application that was completed.
If 100 people start one store application and 60 finish by the reporting date, 40 applications remain unfinished. That leaves 40 unfinished applications, not 40 qualified candidates lost. Their suitability and reasons for stopping are still unknown.
Some may have encountered a technical problem. Others may have discovered that the hours or location do not work for them. Some may return later. Speak to a small, appropriately contacted sample and inspect the relevant steps before choosing a fix.
Compare that with an office vacancy holding 300 completed applications, 240 unread. A better application page does not review those CVs. You need to fix the work after submission.
Before using any supplier’s completion rate in a business case, obtain the start and completion definitions, observation period and customer group. A larger completed-application pool still needs to produce suitable, attended interviews.
Compare your own before-and-after results only when the definitions and observation windows match. A more complete application can be helpful even if the final hiring rate does not change; a shorter application can also move missing work into the interview. Measure both.
Test the store manager’s phone, not just the recruiter’s laptop
The application may work beautifully while the local manager struggles to use the result.
Give a manager a controlled test application on the device they normally use. Ask them to find the candidate, confirm the vacancy, review the relevant answers and record a next step. Do not talk them through every tap: you need to see where the process is unclear.
Then change the person responsible for the test store. Does the new manager receive the necessary work? Does the former manager retain access they no longer need? Who can correct the assignment?
Paradox documents hiring-team configuration by location for Conversational ATS. That makes location ownership a specific capability to inspect, not merely a request for a “mobile-friendly” interface. Check the permissions and configuration included in your proposed deployment.
Location also has two meanings worth separating. Paradox’s job-posting location guide distinguishes advertising areas from the actual location used for candidate assignment. A candidate discovering a role through a nearby area should still be told where the work is.
Test with two stores that have similar job titles. Confirm that the candidate’s answers, appointment and manager notification all refer to the intended vacancy. A smooth conversation that books the wrong store is not a successful application.
Test bookings, reschedules and unavailable managers
A screening result and a booked interview are separate outcomes. Check the rule connecting them.
Paradox’s conversation-level auto-scheduling guide describes configuring screening actions that lead to interview scheduling. Review those conditions with the hiring owner rather than assuming every completed chat should trigger an appointment.
For a controlled test, use a candidate who meets the stated practical requirements, one whose answer needs clarification and one who cannot meet an essential condition. Confirm the expected next step for each before running the test.
Next, remove the manager’s available slots in the test. What does the candidate see, and who gets asked to help? A person unable to book any offered time should not disappear into a no-response category.
Reschedule one test appointment and cancel another. Inspect the candidate’s confirmation, the manager’s calendar and the application record. Each should describe the same plan.
For Screened or another first-interview tool, establish separately who schedules any later human interview. The fact that an AI conversation is available without a recruiter does not mean the manager’s calendar is coordinated automatically.
Check why texts stopped before closing an application
A candidate may want the job but not want further texts. Keep those decisions separate.
Paradox’s SMS unsubscribe documentation, updated in August 2026, distinguishes different forms of messaging opt-out and their scope. Its SMS guidance says customers should not change a candidate’s communication preferences without the candidate’s consent; candidates can resubscribe themselves or update their own preferences.
Test this with a team-controlled number. After opting out, inspect scheduled reminders and the candidate’s application status. Respect the communication preference; do not work around it by switching numbers or repeatedly using another channel to send the same unwanted message.
An unsubscribed status does not always mean the candidate chose to stop messages. The same Paradox guide says repeated delivery failures can cause a soft unsubscribe. Check the recorded cause before describing the candidate’s preference.
Use an agreed alternative contact route where one exists. Record a withdrawal when the candidate has actually withdrawn. Otherwise, keep their intention unconfirmed rather than turning a messaging status into a hiring decision.
Have the responsible colleague review your messaging, privacy and consent requirements for the countries involved. A default product setting is not a complete review of the employer’s obligations.
Two tools can work together, but not by accident
A company may need conversational applications for store hiring and a CV-screening workflow for professional roles. It may also want both capabilities for a particular vacancy.
Before combining them, name one owner for each outward action: application confirmation, interview invitation, reminder, cancellation and final outcome. Then name the system where that action is recorded.
Without that decision, one product can invite the candidate while another still treats them as waiting for review. A recruiter may resend a message that the candidate already received through a different route.
Use a test candidate to trace the complete round trip. Follow the original application into the screening tool, the returned assessment into the ATS and the final human decision into the candidate message. Check a retry and a second application as well as a straightforward completion.
Do not make candidates repeat practical answers simply because the systems do not pass them along. Where repetition is necessary to confirm a change, explain why you are asking again.
Price the workflow you will actually run
Give each supplier the same hiring volumes, locations, channels and tasks. Ask which parts of the demonstrated journey are included in the quote and which need another product, integration or custom work. A feature shown in a demonstration is not necessarily part of the package offered.
Keep the existing ATS charge in the comparison if you will retain it. Add setup, manager training, messaging or usage charges where applicable, and any contract overlap. Show first-year and continuing costs separately.
Count the work left with people: unanswered candidate questions, exceptions, report review and booking problems. For the store route, name who fixes a wrong-location booking. For the office route, name who reads the assessment and approves the next step. Those responsibilities belong beside the price, not in a list of issues to solve after purchase.
Choose the change that solves your hiring problem
For a store network where applicants struggle with forms, location routing and appointment booking, Paradox’s conversational application and scheduling scope deserves a serious look. For a team with a working ATS intake and a backlog of unread CVs or repetitive first calls, a focused screening workflow may address the immediate problem with less change.
A third answer is to fix the existing process: shorten an unnecessary form, clarify the advertised hours or give managers usable booking availability. Do that before paying to automate the same confusion.
End the comparison with a specific proposal: the hiring step to change, the systems to keep, the full cost and the colleague responsible when a candidate gets stuck. Support it with a test from first application to manager review.
For the store, success means the candidate reaches the right manager with the hours understood. For the office vacancy, it means the unread application becomes a checked recommendation. Buy for that result, not for another system that calls itself a screener.


