Permissioned shift calls: workflow and limits

Yes, an agency can ask its own roster about an open shift by automated call, on conditions the agency owns. The roster is the agency’s own workers, each with the worker’s permission to be called about shifts. The calls go out in windows the agency sets. Every call opens with an AI disclosure, asks one question, whether the worker can work a specific shift, and brings the answer back to a coordinator as a structured response. The call assigns nothing; the coordinator confirms the assignment.

What the workflow does not do matters as much as what it does, and this guide spends as much space on the limits as on the steps. Vocapable does not decide whether a given call is lawful, screens nobody against any registry, and connects to no payroll or ATS product. The agency runs the calling program, keeps the consent records behind it, and should confirm its obligations with its own counsel before the first batch. This guide is published by Vocapable, it is not legal advice, and the example batch below is illustrative. The fill shifts automatically page describes the workflow as it is sold.

Start with a roster you own

The Workforce workflow addresses your own workers and specific shifts. Import supported contact records for the people you already place, keep the calling permission for each one with the record, and group workers into a list that fits the shift: the forklift-certified, the people within reach of the site, the ones who said they want more hours. The permission is the worker’s, given to the agency; the agency attests to that calling basis when it imports the roster, and Vocapable does not verify it independently.

A purchased list is not a roster, and a successful configuration check is not permission to call anyone. Workers who withdraw permission come off the list: opt-out handling and an internal suppression list are part of the calling controls, so a worker who asks to stop being called is kept out of later batches. Recruiting strangers is a different workflow with different obligations, and Vocapable is preparing it as a separate pilot; the shift workflow is for people who already work through your agency.

Calling windows, local time and retries

Define the calling windows before the first batch, in the worker’s local time, and set retry limits and caps. Review contact information, local times, suppression and the calling policy that applies before each batch goes out. A 6 a.m. shift does not by itself make a 4:30 a.m. call acceptable; the window is whatever your workers agreed to and whatever applies where they live, and the agency is the one who confirms what that is.

The disclosure and the question

Every call opens with the AI disclosure: the agent identifies itself as AI and says why it is calling on your agency’s behalf. Then it reads the shift as you approved it, date, start time, location, job details and any requirements, so the worker can make an informed choice. Then it asks the one question the workflow exists for: can you work this shift?

The agent captures yes, no and tentative, and the reasons workers share. A worker who asks something outside the approved facts, the rate for that site, whether overtime is likely, gets a message to the coordinator rather than a guess. A worker who says stop calling is handled as an opt-out and suppressed. The call stays short because it is a question, not a conversation about the worker’s week.

Structured responses back to the coordinator

What the coordinator receives is a list, not a stack of voicemails. An illustrative Tuesday warehouse batch, with invented names:

Worker	Response	What the coordinator does with it
Jordan	Yes, available for the stated shift	Check requirements, confirm one assignment
Morgan	Tentative, needs to confirm transportation	Follow up before counting on it
Casey	No, already assigned elsewhere	Nothing now; the reason is useful next time
Two workers	No answer within the retry limit	Visible as not reached, not as a no

Tentative stays distinct from yes, and an unreached worker stays distinct from a refusal. The coordinator reviews the responses against the roster and the shift’s requirements, confirms one assignment, and tells the worker through the agency’s own process. The response record described on the outcomes page shows what each worker actually said.

Output by webhook, CSV and API

Responses reach your process three ways: configured signed webhooks when each call ends, CSV export, and API records. No named staffing-system connector exists, so your integration team maps the record fields to wherever assignments live. Confirm the integration the coordinator needs before launch rather than after the first batch; the record is only useful if it lands where the coordinator looks at 7 a.m.

The limits, plainly

• No shift is assigned by the call. A yes is a recorded response. The coordinator, or the agency’s staffing system, confirms the assignment, and a conversation does not itself make a staffing commitment.
• No payroll or ATS connector exists. Webhooks, CSV and the API are the routes out.
• Calls run on the agency’s own verified Twilio account. Carrier charges are billed by Twilio to the agency; Vocapable bills AI minutes and attempts separately, with the current figures on the pricing page.
• Vocapable performs no registry screening of any kind. The controls that run are the AI disclosure, opt-out handling, the internal suppression list, calling windows, retry limits and caps. None of them determines whether a call is lawful.
• The agency is responsible for lawful calling, for the consent record behind each number, and for the calling program it runs. The acceptable use policy sets what the service may be used for, and the trust page describes the controls without overstating them.
• The agent reads approved shift facts and records answers. It negotiates no rate, promises no hours, and makes no decision about anyone’s employment.

A first batch, illustrated

Pick one shift, a Tuesday 2 p.m. warehouse line that needs two more people, and a list of twelve workers who are certified for it and have given permission to be called about shifts. Set the window to 7 to 9 a.m. in their local time with two attempts. The agent calls, discloses that it is AI, reads the shift and asks the question. By 9 a.m. the coordinator has three yeses, two tentatives, four noes with reasons and three unreached, reviews them against the roster, confirms two assignments and tells those two workers directly. The third yes is told the shift is filled, by the coordinator, because the agent made no promise to anyone.

Then review the batch before expanding the list: the disclosure, the answer capture, the opt-out handling and the follow-up instructions. Start narrow enough to know whether the agent is doing a useful job, and keep the question of what the agency may lawfully do where it belongs, with the agency and its own counsel. The staffing industry page covers the inbound side of the same branch, where a worker’s callout and a client’s order reach a coordinator the same way: as a record a person acts on.