Oracle HCM for Spoke Phone
Overview
Recruiters using Oracle HCM have workflows, candidate records, and consent data all in one place. What Oracle doesn't support is two-way SMS — the channel candidates actually respond to. Outbound messages go out, but replies from candidates go nowhere. The recruiter never sees them. Spoke Phone connects to Oracle HCM so that when a candidate replies to an SMS, the recruiter sees it as a real conversation, attached to the right candidate record. Consent captured in Oracle controls who can be messaged and when. Opt-outs are written back to Oracle automatically. Staff changes in Oracle keep Spoke current without manual user management. Recruiters and field teams work from inside their existing workflow. Conversations stop disappearing.
Candidate replies that reach the recruiter, not a generic broadcast inbox
REPLIES THAT ACTUALLY REACH SOMEONE
Oracle HCM's native SMS add-on sends outbound messages, but candidate replies do not route back to the recruiter, they disappear. Spoke sits alongside Oracle and intercepts those replies, surfacing them to the right recruiter as a live conversation thread. The recruiter sees the candidate's message in context, can respond directly, and has a full record of the exchange, all without leaving their workflow.
Consent captured in Oracle controls who gets messaged and when
NO MESSAGE GOES OUT WITHOUT CONSENT
When a candidate completes a job application and gives SMS consent, that preference is stored in Oracle and synced automatically into Spoke. Recruiters only see candidates who have opted in. If a recruiter manually enters a number, Spoke checks Oracle before the message sends and blocks it if consent isn't on record. No manual checking. No compliance gap from someone messaging a candidate who never agreed to it.
Opt-outs captured in real time and written back to Oracle automatically
OPT-OUTS DON'T GET MISSED
When a candidate replies STOP at any point in a conversation, Spoke captures the opt-out immediately and updates the consent record in Oracle. The same fields that controlled whether the candidate appeared in Spoke are updated, so they won't appear again. Recruiters don't need to manually update Oracle. The compliance record stays accurate without anyone doing anything.
Open a candidate's message thread directly from the Oracle recruiter view
START A CONVERSATION WITHOUT SWITCHING TOOLS
A custom recruiter view inside Oracle displays candidates assigned to each recruiter: with name, role, application status, and a button to open a message thread. Clicking it launches Spoke directly into a new conversation for that candidate. Recruiters stay in Oracle for record-keeping and candidate management, and move into Spoke only when they need to send or respond to a message. No searching, no copy-pasting numbers.
Every call and SMS from field and mobile staff logged to the right Oracle record
MOBILE CONVERSATIONS IN THE SYSTEM
For field teams, retail staff, and recruiters working away from a desk, calls and messages happen on mobile, outside Oracle, outside any record. Spoke logs every call and SMS to the correct Oracle record automatically, regardless of device. Managers can see what was said, when, and by whom. Conversations that used to happen off-system stay visible and trackable.
Staff changes in Oracle update Spoke automatically — no manual user management
DIRECTORY STAYS CURRENT WITHOUT ADMIN WORK
When a new employee is added to Oracle HCM, Spoke provisions their account automatically with the correct title, number, and extension. When someone leaves, their access is removed. The sync runs continuously, so Spoke reflects the current state of the organization without anyone maintaining it separately. For large or fast-changing teams, this removes a recurring administrative burden and closes the access gap that manual provisioning creates.
