Configure services, staffing, commercial work and gradual autonomy.
Native Jobs keeps a customer's request, agreed service, appointment, work evidence and next action together. It supports work at your business and visits to a customer's location. Availability depends on the capabilities enabled for your workspace; this is a controlled pilot.
Platform admins decide whether Jobs is available to a workspace. Tenant admins can enable or hide it in Workspace modules once it is available. Hiding removes clutter and keeps records; it does not cancel existing work. Use Pause all agent work on jobs to stop autonomous follow-through, or the workspace module lockout to block access.
AI setup proposals and autonomous operations have separate feature access and AI-spend entries. Platform admins choose their models, reasoning effort and execution budgets in Billing Defaults → Native Jobs AI, and configure pricing through shared billing/model rates. Shared task-run, messaging and map charges follow the workspace's plan. Disabling Jobs AI leaves manual work available; a held run states the reason and waits for review. A run checks its budget between model/tool rounds; an in-flight provider call may finish first.
AI setup prepares an unpublished proposal. Review the changed sections, apply it to the form, and use Undo AI proposal before further edits to restore the preceding form values. Publishing is a separate action. A stale proposal cannot overwrite newer edits. Published messages, payments and verified physical work have correction or recovery actions; they are not erased by an undo button.
Open Jobs → Operating settings. Choose Take requests to begin without defining staff, equipment or work steps. A request records what the customer needs and their preferred time. It promises neither an appointment nor a price.
Describe your operation and use Draft my setup for a proposal. Review its assumptions before publishing. You can manage requests yourself, select an operations task agent, or use Create a Jobs operations agent if your role can manage agents. Configure its sender before allowing customer messages.
To confirm bookings, add operating hours, a location, a service duration and an approved capacity rule. Simple rules can remain your permanent setup. A shared resource prevents two services from using the same capacity at once. Arrival limits, daily intake limits and simultaneous work capacity are separate controls. Date exceptions replace that day's normal hours; an empty exception means closed.
Use the shared personnel records for staff and their verified skills. A person does not need a product login. A linked workspace user also brings their Calendar commitments into availability checks.
Duty Schedule distinguishes productive shifts, on-call coverage, both, and absence. On-call coverage alone does not make a technician available for job work. A service can use fixed hours or productive roster shifts. Required qualifications must cover the work interval. Leave removes overlapping availability, including on-call coverage.
One-step services need no workflow diagram. More detailed services can specify dependencies, parallel work, handoffs, different people or an independent checker. Labor, equipment and occupied space can have different intervals. A bay can remain occupied until work finishes or the customer collects the vehicle. Staff record actual starts, completions, resource releases and required checks; elapsed time is not evidence of completion.
Calendar shows linked job allocations and productive shifts. Change a job's reservation in Jobs. A working shift describes availability; it is not an additional busy meeting.
Jobs → Needs you and the shared AI Inbox show decisions and unresolved obligations. The assigned agent can gather details, use feasible plans, communicate through configured channels, wait for a reply or deadline, and continue after relevant customer events. Chat, voice, SMS, supported messengers, email, task agents and MCP use the same guarded Jobs tools.
Set each supported agent action to Allowed, Ask first or Never. Approvals apply to the current job version. Take over pauses further agent work on that job. Uncertain message or payment outcomes require reconciliation; the system does not blindly repeat them or silently switch communication channels.
Record an absence, equipment outage or work delay when it happens. Existing promises remain visible while the system checks affected work. Unpinned drop-offs can be repaired within their agreed arrival and ready-by window. Changing a customer promise requires agreement. Started work and verified evidence constrain replanning.
A mobile service needs an agreed address, a base, qualified named crew, vehicle, driving-distance limit and travel buffer. Enable Job maps and accept its lookup price before using road-duration estimates.
The first routing model reserves the crew and vehicle from departure through return to base. It checks both directions and refreshes estimates near the visit. A team member verifies the return; finishing work does not automatically release the crew. This model does not promise optimized multi-stop routes or offline evidence recovery.
Linked follow-up visits keep separate agreements and reservations. Recurring requests create new unconfirmed requests: they do not inherit an old quote, appointment or payment authorization.
Optional commercial settings connect Jobs to service products, tax rules and shared sales orders in Products & inventory. Configuring this requires the relevant inventory permission. Prepare one or more service options, show the total including tax, and record explicit customer acceptance. Signed-in customers can also accept in their enabled customer portal. Estimate acceptance does not reserve an appointment.
The accepted option creates a shared order. Changed prices or taxes are held for review instead of silently changing the customer's accepted amount. Preparing an invoice after verified completion creates a linked draft invoice through the shared order. Its document and accounting controls remain on that order.
When payment collection is activated for the workspace, an authorized agent or team member can prepare a link using the tenant's own Stripe account. A queued link is not money received. Provider receipts update the shared order; a pending refund is not a completed refund. Staff commercial actions require permission to manage shared orders. The accountable owner must retain the required permissions for queued operations to proceed.
Without commercial settings, Record payment remains a record of independently verified money received; it does not charge anyone. Practice commercial operations are explicitly simulated and do not create real financial records or move money.
The customer portal shows the customer's own jobs, estimates and payment links. A request to change an appointment leaves the standing commitment in place until a replacement is checked and agreed.
Jobs reports completed work, promise adherence, unresolved communications, commercial reconciliation and staff-recorded administrative minutes. These are observations, not a claim of time saved.
For one-step services, optional duration learning uses verified productive time, at least 20 comparable samples, a separate five-sample check and the owner's bounds. Each adjustment is limited to 10%; accepted jobs keep their recipe. An optional assignment preference favors less-booked resources among feasible alternatives. Neither learning nor optimization can grant qualifications, waive checks or widen autonomy.