Muse test — Wendy’s, “Patty” — VENDOR NOT CONFIRMED AS PARADOX
- Company / site: Wendy’s — https://wendys-careers.com ; chat reached only via a job page’s “APPLY VIA CHATBOT” button, at https://wendys-careers.com/chat/shift-manager/213771/?jobID=47540&posting_id=213771
- Date / time: Friday, November 6, 2026, 10:23–10:37 a.m. EST (America/Toronto), runtime-measured
- Assistant: Patty, described on the site as “our virtual recruiting assistant”
- VENDOR VERDICT: Paradox NOT confirmed. No “Powered by Paradox” attribution and no “can make mistakes” line was visible anywhere in the widget (checked on the chat page and in an enlarged crop). Header shows only the Wendy’s logo; footer is only the message input and SEND button. The only vendor-like label seen was “JobChat Candidate”, shown above the visitor’s own messages. Nothing in this file is evidence about Paradox, and the session is excluded from the Paradox test tally. It is preserved because the brief (§3) requires the original target’s record to be kept, separate from any replacement.
- Role used: Shift Manager — Dublin, Ohio; Ref 2026-47540; $15.55–$21.75/hr; job code 47540. Posting: https://wendys-careers.com/job-search/posting/shift-manager/213771/ . The posting’s apply section reads: “Apply with Patty, our virtual recruiting assistant, in just 3 minutes. Get started by entering this job code: 47540.”
- Terms gate: Existed; accepted (answered “1”) in both sessions, per Nik’s authorisation. Patty’s terms message, verbatim: “Thanks for your interest in Wendy’s! Please review these terms to proceed: https://wendys-careers.com/privacy-policy/ Please select the number associated with your answer for the following questions Do you accept? 1. Yes 2. No”
- Personal information demanded: FIRST name, immediately after terms acceptance, before any question could be answered, in both sessions: “I can help you apply to that job. Go ahead and enter your FIRST name - not your last name. We’ll ask you that next.” No personal information was entered at any point; no application submitted; no account created; no CAPTCHA encountered.
- Conventional form route: Not discoverable. The posting’s only application controls were two “APPLY VIA CHATBOT” buttons; no regular form or alternative apply link on the posting, Job Search, or homepage.
- Evidence type: Verbatim transcripts (two sessions) from live browser session; no screenshot captured.
Session 1 (10:24–10:32 a.m.)
Patty: Hi! I’m Patty, your personal Wendy’s job assistant. Thank you for your interest in Wendy’s. Please provide the job code number on the screen in front of you. Tester (A, first attempt): What can you tell me about the Shift Manager role? Patty: I’m sorry that number doesn’t match the job you were looking at. Would you please check the number and enter again? Tester: 47540 Patty: (terms message, above) Tester: 1 Patty: I can help you apply to that job. Go ahead and enter your FIRST name - not your last name. We’ll ask you that next. Tester (A, second attempt): What can you tell me about the Shift Manager role? Patty: This doesn’t appear to be a name, can you check your input and try again? Tester (G): That didn’t answer my question. Can you explain what the role involves? Patty: NO reply — typing indicator for more than 5 minutes. Tester (decline, per Nik protocol, 10:29): I’d rather not share that yet — I have some questions about the role first. Tester (B, 10:31): What would I actually be doing day to day in that position? Patty: NO reply to the decline or to B. At ~10:32 the session ended with a dialog: “Session has ended. Please start a new chat session.” (Question C, being typed, was never sent in this session.)
Session 2 (10:32–10:37 a.m.)
Patty: (same greeting; job code 47540 entered; same terms message; “1” answered) Patty: I can help you apply to that job. Go ahead and enter your FIRST name - not your last name. We’ll ask you that next. Tester (decline): I’d rather not share that yet — I have some questions about the role first. Patty: This doesn’t appear to be a name, can you check your input and try again? Tester (C): Based on the role we were just discussing, what skills would help someone succeed? Patty: This doesn’t appear to be a name, can you check your input and try again? Tester (D): Can you explain that in simpler terms? Patty: This doesn’t appear to be a name, can you check your input and try again? Tester (E, 10:34): Can I apply using a regular application form instead of this chatbot? Patty: NO reply — typing indicator (~3 minutes by last observation). Tester (F, 10:35): Are you able to answer questions about this job, or are you mainly here to collect application information? Patty: NO reply — typing indicator still showing at the final observation, 10:37.
Outcome (observed)
- No question in either session received any information about the Shift Manager role, its duties, or its skills. Every input was processed as either a job-code entry or a first-name field entry; longer free-form questions (G, E, F) produced multi-minute typing stalls and, in Session 1, session termination.
- The polite refusal to provide a first name did not unlock question-answering: it was itself rejected as an invalid name (“This doesn’t appear to be a name…”).
- Scripted replies were near-instant (<5s); the stalls occurred only on the free-form follow-ups.
- Filed as the investigation’s clearest specimen of the pattern Nik named — a form field validator wearing a chat window — with the vendor unattributed: whatever Patty runs on, no visible evidence ties her to Paradox.