During open enrollment, people paste plan summaries into Claude and ChatGPT because the PDF is what they were emailed and Workday feels slower. The PDF is not their election. It has no idea which dependents they added Tuesday, and once it is in the chat it is no longer protected by Workday’s domains.
Kiweely Bridge (coming next) is the alternative the product pages describe: the employee asks in Claude, ChatGPT, or Gemini, signed in as themselves, and the answer comes from Workday under that sign-in.
What Workday already uses to show benefits
FAQ: Terminations is explicit that benefit visibility is domain security, not a vibe. For a terminated worker who should still see benefits and pay, Workday points administrators at Terminee as Self plus Self-Service: Benefits, Self Service: Benefits and Pay Hub, and Self-Service: Compensation. The longer list of domains that let someone see another person’s benefit data includes Self-Service: Benefit Elections and Worker Data: Benefit Elections. Active employees use the same style of self-service domains for their own elections. If the domain is not granted, Workday does not return the data, in the UI or through a user-delegated call.
That is the whole product boundary. Bridge does not ship a benefit-plan library. It calls the tenant. A medical summary that exists only as a PDF in a mailbox is not a Workday row unless someone loaded it into a report or document the worker can already open. This design does not “read the enrollment booklet” from a shared drive.
Paste versus a live question
| PDF in the chat | Question through Bridge (coming next) | |
|---|---|---|
| Whose data | PDF in the chatWhoever was in the file, often a whole plan chart | Question through Bridge (coming next)The signed-in worker’s Workday data, plus anyone their role already allows |
| Freshness | PDF in the chatThe day the file was exported | Question through Bridge (coming next)The tenant at the time of the call |
| Dependents and coverage dates | PDF in the chatFrozen | Question through Bridge (coming next)Whatever Workday returns for that worker now |
| A coworker’s election | PDF in the chatIn the file if someone exported it | Question through Bridge (coming next)Denied unless that sign-in can already see it |
| Changing an election | PDF in the chatThe model can only talk | Question through Bridge (coming next)Read-only unless you enable the task. An enabled write stops for a browser card showing now and after |
| What gets stored by the connector | PDF in the chatYou handed the file to the assistant | Question through Bridge (coming next)Bridge streams the response in memory and does not write Workday records, prompts, or answers to disk, logs, or a database |
The assistant vendor still sees the redacted tool result, or it cannot answer. Say that in the rollout note. The improvement on the Workday side is that you stopped exporting the population to make one person whole.
Questions that fit, and questions that do not
Fit, when the worker’s domains include their elections:
- Which plans am I enrolled in?
- Who are my covered dependents?
- What is the coverage begin date Workday has on this election?
- Did my enrollment event submit, or is it still in progress? That one is a business process, visible to the people who can already see the event.
Do not fit this connector:
- “Compare every plan in the booklet and tell me which is best.” The booklet is not the election, and Bridge does not become a benefits advisor because the model is articulate.
- “Change my coverage to the family plan” as a sentence that should just happen. If you enable the write, the worker still confirms now and after in the browser. If you do not enable it, the task is not on the tool list.
- Reopening the window for one employee after it closes. That is an administrator action in Workday, not a chat shortcut. Keep it with the people who already have that business process.
Open enrollment week is also a load week. Many employees will ask at once, and those calls share the tenant with everything else. Workday throttles overloaded REST and report calls. A question about one worker’s elections is a smaller call than a report of every election in the company. Prefer the first.
What to tell employees
Sign in on Workday when the assistant asks. Ask about your own elections. Do not upload the plan PDF or a spreadsheet of dependents. If the answer disagrees with a mailer, Workday is the record you can open yourself. If you want to change an election, finish the confirmation in the browser card, not in the chat thread.
Administrators: test as Employee as Self, as a contingent worker if they enroll, and as Terminee as Self if alumni still have an event. Confirm a test user cannot see a coworker’s Worker Data: Benefit Elections. Then publish. The company price does not go up because the questions are about benefits. The published bands are $499, $1,499, and $3,999 per month by licensed employees, unlimited calls, sandboxes included. Bridge is coming next.
Register interest before the next enrollment window if you want this path. It is not switched on today.
Frequently asked questions
Does the assistant need the plan documents to answer?
It needs the worker’s Workday data. Plan documents explain the design of a benefit. Elections say what this person chose. Mixing them in one upload is how a stale PDF overrides the tenant.
Can ChatGPT enroll someone because they typed “yes”?
Not on the Bridge design. Writes are off until an admin enables them, and an enabled write waits for an out-of-band browser approval. The chat message is not the approval.