const { HexGrid, SiteNav, SiteFooter, PageShell, FAQList, CloseCTA, ConnectedFlow, Screen, contactHref, } = window.GS; const PhoneIcon = ({ size = 16 }) => ( ); const DocIcon = () => ( ); const PeopleIcon = () => ( ); const PersonIcon = () => ( ); const WAVE = [8, 14, 22, 12, 28, 18, 10, 34, 20, 40, 24, 32, 16, 36, 22, 28, 14, 24, 12, 18, 8, 14, 6, 10, 5, 8]; const CallDesk = () => (
Inbound Absence Call Example workflow
Incoming call · example
Worker absence report
Eastview · 07:00–15:00 shift
AI Voice Assistant
Voice conversation · Absence details collected
{[ ['Absence', 'Recorded', ], ['Cover', 'Outreach', ], ['Agency', 'Updated', ], ].map(([title, detail, icon]) => (
{icon} {title} {detail}
))}
Illustrative workflow; replacement confirmation depends on worker availability and the configured process.
); const Hero = () => (
); const manualSteps = [ ['01', 'Take the absence call', 'Collect the details while other work stops.'], ['02', 'Work out which booking is affected', 'Check the worker, shift and client details.'], ['03', 'Find possible replacement workers', 'Review availability, suitability and who can cover.'], ['04', 'Contact and chase for cover', 'Call, message and follow up until someone responds.'], ['05', 'Update the record and inform the client', 'Log the outcome and communicate what happens next.'], ]; const Problem = () => (
The problem

Your Consultants Should Be Making Placements. Not Managing Absence Calls.

When a worker reports an absence, your consultants can end up answering calls, identifying affected shifts, searching for replacement workers, chasing confirmations and updating clients.

That's time spent on administration instead of filling vacancies, developing client relationships and generating revenue.

The manual process

One Absence. Multiple Admin Tasks.

    {manualSteps.map(([n, title, text]) => (
  1. {n}
    {title}

    {text}

    2. ))}

The real cost is not just the absence. It's the consultant time used to manage everything around it.

); const Solution = () => (
The solution

A Recorded Workflow, With People Where the Decision Sits.

Handled Automatically

Capture & match

The system records the absence and matches it to the correct worker, shift and booking information.

Replacement outreach

Eligible replacement workers are contacted through the channels your agency has configured.

Record & route

Actions and outcomes are written back to the record, with exceptions passed on only when needed.

Routine handling is automated before anyone on your team needs to step in.

Your Team Stays in Control

The system handles the repetitive calls, replacement outreach and follow-ups. When a decision is needed, your consultant receives a clear summary and a simple approval request — rather than having to chase workers, make multiple calls or manually coordinate every step.

The system does the legwork. Your team makes the decisions.

Example approval Illustrative
Proposed replacement Available worker · Eastview · 07:00–15:00
); const stages = [ { n: '01', title: 'Notify', text: 'The worker reports the absence by phone or another channel the agency has set up.' }, { n: '02', title: 'Capture', text: 'Reason, timing and any questions you require are stored against the notification.' }, { n: '03', title: 'Identify', text: 'The relevant shift and worker record are checked from the information available to the system.' }, { n: '04', title: 'Search', text: 'Eligible replacement workers are identified using the rules and availability data you supply.' }, { n: '05', title: 'Contact', text: 'Those workers are contacted on the channels configured for that workflow.' }, { n: '06', title: 'Update', text: 'A confirmation, an open shift or an exception is recorded and routed to the right people.' }, ]; const How = () => (
How it works

From Notification to a Recorded Outcome.

Each stage can be adjusted. Contacting a replacement is not the same as filling the shift. If nobody suitable confirms, the shift stays open and a person takes the case.

); const capabilities = [ ['Inbound reporting', 'Workers can report an absence without waiting for a coordinator to pick up, on the number or channel you assign.'], ['Language support', 'Where the voice service supports it, a call can be handled in more than one language. That is configured per workflow, not assumed for every caller.'], ['Replacement coordination', 'Eligible workers are contacted from the shift and availability information the system can see.'], ['Configurable notifications', 'Managers, clients or coordinators can be notified at the points you choose.'], ['Audit record', 'The report, questions, contact attempts and outcome are kept together so the team can see what happened.'], ['Escalation', 'Unconfirmed cover, missing data or a rule that needs approval is passed to a member of staff with the context attached.'], ]; const weekMarks = ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun']; const markedDays = new Set(['Mon', 'Tue', 'Thu']); const InsightIcon = ({ d }) => ( ); const InsightDesk = () => (
Absence Intelligence Illustrative

Recurring absence patterns

Example marks for early shifts. Not a measured week.

  • Short-notice absences that repeat
  • Grouped by shift, site and day
  • Change across the records already kept

Shift and site

  • Shifts that keep needing emergency cover
  • Sites with repeated disruption
  • Hours that may need a stronger reserve
  • Shortages worth a planning review

Replacement

  • Cover requests started
  • Confirmed, still open, or with staff
  • Replies recorded against each request
  • Where a standby pool could help
Example operational insight
Repeated short-notice absences affecting early shifts at Client Site A.
Suggested response

Develop a dedicated standby worker pool and review shift-cover arrangements with the client.

An illustration of what can be read from the absence, shift, contact attempts and outcome already kept. Not a live analytics view, and not a client result. A named worker’s history would stay with authorised staff, and would not be treated as a conclusion about health or conduct.
); const partnerPoints = [ 'Identify problems before they become persistent client complaints.', 'Hold more informed client review meetings.', 'Recommend improved shift-cover arrangements.', 'Demonstrate attentiveness to operational challenges.', 'Build confidence in the agency’s management of temporary workforces.', ]; const Insights = () => (
Insights & intelligence

Turn Absence Data Into Stronger Client Relationships.

Every absence call creates valuable operational information. Identify recurring absence patterns, discover which shifts are repeatedly affected and understand where replacement cover is proving difficult.

Use those insights to address recurring problems with your clients, recommend practical improvements and demonstrate the value your agency provides.

  • Recurring disruption, visible by shift, site and day.
  • Cover that is repeatedly hard to confirm.
  • A practical change to recommend, not only a record of the call.

The client relationship strengthens when the conversation is about the pattern, and what to change, rather than the latest missed shift alone.

From Reactive Supplier to Proactive Recruitment Partner.

Give clients evidence of recurring staffing challenges and bring practical solutions to account reviews, instead of discussing individual missed shifts in isolation.

{partnerPoints.map((point) => (

{point}

))}

Client account summaries

Scoped with you

A periodic summary for an account review can be prepared from these records: trends over the period, the shifts affected most often, replacement outcomes, recurring bottlenecks, and the improvements you recommend. Producing that pack is part of the scope agreed with the agency. It is not an automated report already running, and it would not include a worker’s health detail.

); const Capabilities = () => (
Capabilities

What the System Is Built to Handle.

{capabilities.map(([title, text]) => (

{title}

{text}

))}
); const StatusPanel = () => (
Absence recorded
Eastview · 07:00–15:00 · today · reason captured
Replacement contact in progress
Eligible workers contacted · waiting for a confirmation
Escalation if nobody confirms
Coordinator receives the record and the contact attempts
 ); const exampleSteps = [ ['Call matched', 'Worker, shift and timing identified'], ['Cover workflow started', 'Eligible workers contacted'], ['Outcome recorded', 'Staff updated or escalation triggered'], ]; const Example = () => (
A realistic example

One Morning Absence, Handled From Call to Cover.

A worker calls before a morning shift and says they cannot attend. The system matches the absence to the correct booking, records the details and starts the next steps based on the agency’s configured process.

    {exampleSteps.map(([title, text]) => (
  • {title} — {text}
    • ))}
); const Benefits = () => (
Operational benefits

Clearer Handling of the Same Work.

{[ ['Less administrative handling', 'The first questions and the contact sequence do not all sit with a coordinator.'], ['More consistent recording', 'Reason, shift and outcome are stored in the same place each time.'], ['Quicker notification', 'The people who need to know can be told when the report arrives, not after a voicemail is found.'], ['Visibility of open cover', 'Outstanding shifts stay on a status list instead of in a personal notebook.'], ].map(([title, text]) => (

{title}

{text}

))}
Discuss Absence Management
); const Integrations = () => (
Integrations

Connected Where Access Exists.

Absence Management can be scoped against a worker database, a rota, an ATS or another operational tool. A connection is only promised once we have confirmed how that system can be reached.

Scheduling and the wider operational picture sit with Agency Operations. Absence Management is the workflow for the absence itself.

); const Audience = () => (
Who it is for

Shift-Based Recruitment Teams.

Agencies where a missed absence call becomes a missed shift.

{[ ['Industrial staffing', 'Temporary and site-based workers, with cover needed before a shift starts.'], ['Healthcare staffing', 'Care and clinical bookings where the client still needs to be informed.'], ['Logistics and driving', 'Early starts and depot shifts that cannot wait for the office to open.'], ['Other shift-based desks', 'Any recruitment operation that coordinates named workers against a rota.'], ].map(([title, text]) => (

{title}

{text}

))}
); const Pricing = () => (
Pricing

Scoped to the Operation, Not a Flat Rate.

Commercial terms depend on the shape of the workflow. We quote after a short discussion. There is no standard price list on this page.

{[ ['Workforce and volume', 'How many workers report absence, and how often the line is used.'], ['Integrations', 'Which rota, database or messaging tools need to be connected, and how access is granted.'], ['Workflow and support', 'Approval rules, escalation paths, languages and the level of ongoing support.'], ].map(([title, text]) => (

{title}

{text}

))}
); const faqs = [ ['Can workers report an absence outside office hours?', 'The reporting channel can stay available outside the hours you choose. What happens next — a contact sequence, a queued task, or an escalation — is part of the configuration.'], ['Does it already know our workers?', 'It uses the worker, shift and availability information you make available. It does not invent people who are not on that record.'], ['What if a person needs to approve the cover?', 'The workflow stops at that approval, shows the context, and waits. A replacement is not treated as confirmed until the rule you set has been met.'], ['Will it integrate with our rota or ATS?', 'Only where that system provides a usable route in. We confirm access before including a connection in the scope.'], ['Can our team still handle a case themselves?', 'Yes. Staff can review, take over or close a case. The report and the attempts remain on the record.'], ['How is it deployed?', 'Discovery, configuration, testing with your scenarios, then launch. The timetable is agreed from the scope. It is not the same length for every agency.'], ]; function AbsencePage() { return (
Questions

Absence Management Questions

 ); } ReactDOM.createRoot(document.getElementById('root')).render();