“Count incomplete safety training by department, save the table, and send it to me.”
Report from training records, create a table, then deliver the table to one named recipient.
Tell Zip what you need in ordinary words. It can look through the company records and documents your account is allowed to use, work out figures in code, prepare a draft, or carry out supported tasks such as reminders, assignments, requests, and publishing.
It uses your workspace context and keeps a record of the steps it took.

One request. Relevant records. A visible result.
Find the people still working through onboarding. Count training completions by department. Draft a summary from approved information. Remind each person what they still owe. Give a new hire a task. Check the status of an HR request.
Zip brings those requests together in one conversation. It looks up the relevant records, asks for missing detail when it cannot safely choose, and reports what it found or did.
“Show training completion by department, save it as a table, and send it to me.”
It queries permitted records and calculates the counts in code. If the records cannot answer, it says what is missing.
Actions follow the user's ask-before-acting setting. Sensitive actions and broad outreach still require a confirmation.
The job keeps its steps and results. Zip says what worked, what failed, and what remains to do.
Zip can use the company roster and reporting lines, onboarding and training records, requests and sign-offs, uploaded knowledge, published documents, tables, and its own prior job results—subject to the access of the person asking.
When a request describes a group, Zip uses a rule against the current roster and task records. It does not ask the language model to invent the recipients or calculate a total.
Zip can search company knowledge, read a document, and draft from the information it finds. A document answer depends on the source material the company has supplied and published.
The available tools narrow by role, and the underlying action is checked again against the caller and company. An employee's access is different from an HR administrator's.
These are the current actions exposed to Zip. The available records and actions depend on the person's role and the modules configured for the company.
Locate permitted records, documents, people, spreadsheet tables, repeating jobs, requests, unsigned acknowledgements, recent completed actions, or product guidance. Results identify the item to inspect next rather than exposing a whole record in the search list.
Try: “Find my open requests.”
Read a document, inspect a record set's available fields, search company knowledge for relevant excerpts, or open one request and its history. The answer should come from the retrieved material.
Try: “What does our published handbook say about bereavement leave?”
Filter, group, count, sum, or average company records and uploaded spreadsheets with code. Zip can save the result as an editable Zipplee table for review and Excel download. It can also calculate arithmetic from numbers you provide.
Try: “Count completed safety training by department and make it a table.”
Write a private Document Studio draft, turn a report's tables into an editable table, or translate a document into a new draft for review. An employee can file an HR request in their own words; document authoring belongs to an HR seat.
Try: “Draft a summary of open onboarding tasks for managers.”
Revise one of your Document Studio drafts, pause a repeating job, or update an authorized request with a status, assignment, or reply. A request decision uses Approve instead.
Try: “Make the opening of my draft shorter and clearer.”
Set up a job to repeat daily, on weekdays, weekly, or monthly at a chosen local time. Zip reruns the goal against current records and reports the outcome. A scheduled job can be paused.
Try: “Every Monday at 8, remind people with overdue onboarding tasks.”
HR can place an announcement in the employee news feed, add a company key date, or publish a reviewed Document Studio draft to the employee Documents page. A published document can also be taken down.
Try: “Announce the open-enrollment dates and add the opening day to the calendar.”
Send a message or document to named people or a group resolved from company records. Group reminders can include each person's own outstanding items. A saved spreadsheet table can be sent to one named person per delivery.
Try: “Remind everyone with overdue onboarding tasks what they still need to do.”
Give a task to one person or a resolved group, with a due date. HR can also request a formal sign-off against a published document when signatures are what the request actually calls for.
Try: “Give the new hires a task to complete their I-9 by Friday.”
An authorized decision-maker can approve, decline, or return an employee request for changes. A person can record their own acknowledgement after they say they have read the assigned document.
Try: “Show the equipment requests waiting for my decision.”
Find a recent Zip action and request a reversal where the underlying action supports it. Zip reports what was pulled back and what cannot be retracted after delivery.
Try: “Undo that announcement.”
A single request can combine lookups, a calculated result, a draft, and a supported action. Each step uses the result of the one before it.
Report from training records, create a table, then deliver the table to one named recipient.
Set a repeating job that checks current requests and reports the result each week.
Find the document, translate its full text, and save a private draft for a human to check before publishing.
Resolve the manager's team and overdue tasks, preview the relevant outreach when approval is required, then report the delivery result.
HR and administrators: work across permitted company records, create and revise drafts, publish company information, send communications, run reports, and set up sign-off campaigns.
Managers: ask about their reporting team, send a team message or task, and decide requests they are authorized to handle.
Employees: ask about their own records and published company knowledge, file or withdraw a request, check its status, and acknowledge a document they have read.
Zip narrows its tools by role, and the action layer checks access again before reading or changing company data.
The ask-before-acting setting controls ordinary changes. Request decisions, sign-offs, messages involving money or percentages, and broad outreach require confirmation. When an approval is needed, Zip prepares a preview first.
Records and spreadsheet reports use code to filter, group, and calculate. Zip is instructed to say when the records do not contain an answer.
Zip's final summary is checked against its recorded tool results, so an unsupported claim of a completed action can be rejected.
The tool list narrows for an employee, and each underlying action checks the caller's role, company, and permitted reach again.
Each job keeps its steps and outcomes. Repeated identical action calls in the same job are keyed to avoid accidental duplicate sends.
Model calls count against the company's monthly AI budget. If it is reached, Zip pauses and tells the person rather than continuing to spend.
It can read permitted company records, uploaded documents, and published knowledge. An answer depends on the material available to the person asking; Zip should say when a source is missing.
Routine actions follow the person's ask-before-acting setting. Sensitive actions and broad outreach still require confirmation, and Zip previews an action when approval is needed.
You can decline a proposed action. A recent completed action can be reversed when that action supports undo; Zip reports when something cannot be taken back.
No. HR, managers, and employees have different access. Zip's tools and the underlying action checks use the caller's role and company scope.
Yes. Zip can schedule a supported goal daily, on weekdays, weekly, or monthly at a company-local time, and the job can be paused.
Ask from the records you already keep in Zipplee. Review the result, and let Zip carry out the supported next step.