Solutions / Recruiting and staffing / Turning portal requisition alerts into one owned job order

Turning portal requisition alerts into one owned job order

A requisition posted in SAP Fieldglass reaches a supplier as a notification, and the distribution tier the agency sits in decides how long it holds the posting before a second tier is released into it. Whoever opens the shared mailbox first retypes the title, the not to exceed rate and the worksite into Bullhorn, or nobody does and the posting closes unworked. JobDiva sells a spider that logs into supported portals for exactly this reason. Where no connector exists the alert itself is the only structured thing that arrives, and it is parseable.


Context / recruiting and staffing Why this one is worth doing here

The parser reads the resume, then somebody corrects the employment dates it merged, which is most of the time it was supposed to save.

Resumes arrive in every format that has ever existed, including scans with no text layer and designed templates in two columns that get read in the wrong order. Parsing is nearly always a third-party component, and its characteristic failure is employment history: dates written as ranges with words in them produce merged employers and wrong tenure.

Systems this usually touches

  • SAP Fieldglass
  • JobDiva
  • Bullhorn
  • Outlook

When this is the wrong thing to build

Pick something else if requisitions already arrive through a connector your vendor maintains, or if one coordinator watches a single portal all day. Value here scales with the number of separate portals and shared mailboxes in play, and one well behaved feed does not justify the build.

The constraint that shapes it

This is the sector where the boundary is sharpest, and it is worth stating plainly: rejection is the regulated act, not enrichment. More on how this sector works.

The same shape elsewhere / Intake and routing 12 sectors run it

Something arrives from anywhere. It becomes one record with one owner. Read what this shape is, or start from one of these.

Real estate
Turning portal leads into one shape a person can work
Real estate
Turning an after hours maintenance call into one work order
Law firms
Entering a new client once instead of four times
Law firms
Filing client email to the matter instead of the inbox
Field services
Booking a service call without a person typing it
Field services
Sorting a return visit into callback or new work
What people ask about this 5 of them
  • How do I get Fieldglass job postings into Bullhorn without retyping them?
  • What decides how quickly a second tier supplier sees a requisition?
  • Can requisition emails from a VMS become job orders automatically?
  • How do I stop two recruiters working the same VMS requisition?
  • Which VMS portals can be read without a supplier side integration?

Back to recruiting and staffing, or see how this is priced and scoped.