Internal services & operations
Every internal request gets an owner and a visible next step.
Facilities, people operations, legal, security and shared services take requests through one front door. Each one names who owns it, what it needs, and when it is due.
Service Request
Internal operations and shared-services intake.
How it works
From the first message to a recorded outcome.
- 01
One request form, many teams
The starter Service Request asks for the area — Facilities, People operations, Legal, Security or General operations — the details and the location.
- 02
An owner and a date
Assign the request, set the due date, and keep internal discussion in notes the requester never sees.
- 03
A decision, on the record
Ask a manager to approve by email. They confirm with a code; the decision and their note stay with the request.
- 04
Close the loop
Reply to the requester, mark it complete, and keep the steps as a procedure for next time.
Lobby wayfinding signs before the open house
Submitted answers
- Request area
- Facilities
- Location
- Main office · lobby
Request Context
Looks for: the requested outcome, requester, affected team, owner, and due date.
Recommended Actions
Looks for: required information, approvals, dependencies, policy constraints, and handoffs.
The approver needs no account. They open a secure link and confirm with a six-digit code.
Only visible to your team
Wall is plaster over brick — using the long anchors from the dock supplies.Set up for this work
The Internal Services / Operations profile, out of the box.
A workspace set up with this profile starts with these defaults. Rename terms and switch modules on or off later; the review policy stays with the profile.
- A request is called
- Request
- Who asks · for whom
- Requester · Organization
- Owned by
- Assignee
- Time tracked by
- Requested due dates
- Starter form
- Service Request: Request area, Request details, Location
- AI review
- Suggested replies arrive as drafts for the team to send
- Knowledge filed as
- Procedure in Knowledge
The analysis is guided to look forRequest Context · Recommended Actions
- the requested outcome, requester, affected team, owner, and due date
- required information, approvals, dependencies, policy constraints, and handoffs
- ambiguity, blockers, organizational impact, and the next accountable action
Priority rises for
- employee safety, access, payroll, legal, or business-continuity impact
- a blocked team or time-sensitive organizational dependency
- a missed due date, approval bottleneck, or material operational delay
From the product’s profile instructions. The analysis can be wrong; your team decides.
What it won’t do
- Assist Engine manages the request; it is not an HR, legal or facilities management system.
- Collect only the information the service needs — avoid sensitive personal data in free text.
- Approvals record a decision; they do not change the request’s status on their own.
Try it with this team’s questions.
The sample runs in your browser. Nothing is submitted, and no account is needed.
