Describe the process. Your AI Office runs it.
Describe a business process in one sentence. Your AI project manager designs it as a step graph you can see and edit, builds every form, table, approval and automation it needs, and then routes every case through it — with every approval routed through your reporting tree.
- 1
Request leave
Requester · Form · anyone in the company
- 2
Policy check
System · Automation · no credits
- 32 waiting
Manager approval
Manager · Requester's reporting head
- 4
Revise request
Requester · Same form, prefilled
- 5
More than 3 days?
System · Branch
- 6
HR review
HR · Head of HR
- 7
Approved
System · Calendar blocked · HR told
Built from one sentence: “employees request leave, their manager approves, HR reviews anything over three days, and an approved leave blocks the calendar.”
You already own the parts. Nobody has time to assemble them.
Every company runs on forms, spreadsheets, approvals by email and somebody chasing. Workflows turn “we have the parts” into “we described the process and it runs”.
How it runs today
- A form in one tool, a spreadsheet in another, the approval in an email thread.
- Who approves what lives in somebody’s head, and breaks the week they leave.
- Nobody can answer “where is my request” without asking three people.
- Exceptions are handled by remembering them.
- Building an internal process means a project, a budget and a quarter.
How it runs with Qik Office
- One sentence produces the forms, the tables, the approvals and the automations.
- Approvals resolve from your reporting tree, departments and job titles.
- Every requester sees their own case and the step it is sitting on.
- Exceptions are steps on the map, with an SLA and somewhere to escalate.
- Changing the process is a sentence and a diff you approve.
From a sentence to a running process
The agent reads your office first — the rooms you own, your people, your reporting heads, departments and policies — then designs against what is already there.
Describe it
Type the process the way you would explain it to a new joiner. No builder, no node palette, no expression language.
Review the design
A map comes back: every step, who acts, what data it touches, what happens next per outcome — and the few choices that are yours to make.
Approve and build
The agent creates the tables, forms, views, approvals, automations and timers inside the room that owns the workflow. Nothing is a black box.
Watch it run
The same map becomes the dashboard: live counts per step, the oldest case waiting, anything past its SLA.
Ten kinds of step, and the edges between them
A workflow is a graph, not a checklist. Steps can run side by side, wait for a date, branch on a value, or send a case back to where it came from.
Start
A form, a message, a meeting decision, a schedule or an event opens a case.
Human
A person fills a form, completes a to-do, uploads a file or acknowledges in chat.
Approve
One approver or several, with an SLA and an escalation if nobody answers.
Do
The agent does the work — writes the row, sends the mail, books the calendar.
Branch
A condition on the case decides which way it goes. Loops are allowed.
Parallel
Several departments work at the same time on the same case.
Join
Wait for all of them — or the ones that matter — before carrying on.
Wait
Pause until a date on the record, or for a set time, then resume.
Notify
Tell a person, a room or a customer — notification, email or chat.
End
Close the case with a named outcome that reporting can count.
Approvals follow your org chart, not a list of names
Your AI Office already knows who reports to whom, which department somebody sits in and what title they hold. A workflow points at that structure instead of copying it, so a process written today still routes correctly after a reorganization.
A title nobody holds stops the case for attention rather than quietly sending it to the wrong person — a wrong approval is worse than a late one.
The requester's manager
Walked from your reporting tree at the moment the step activates — never a name in a design.
One level up
Used for escalation: if the manager has not answered in time, it goes to their manager.
The head of a department
Resolved from the department the workflow names — Finance, Legal, HR.
Whoever holds a title
"IT Head" routes to whoever holds that designation today, not to the person who held it when it was written.
A person on the record
Any people column on the case — the budget owner, the account manager, the assigned engineer.
The requester
Sends a step back to whoever started the case, prefilled with what they already submitted.
Several people at once
Any of them, all of them, a count of them, or one after another in order.
Their delegate, if away
If the person the rule resolves to is out of office today, it goes to their delegate instead.
One approver, or five in the right order
Any, all, or a count
Any one of the heads can release it, or all of them must, or three out of five — the resolution is part of the design.
One after another
Sequential approvals stop at the first rejection, so nobody reviews something that is already dead.
A deadline and a way up
An SLA marks a step late; an escalation window moves it to the next level automatically.
Send it back, not just away
“Changes requested” hands the same form back to the requester, prefilled, and returns it to the same approver.
The decision is data
An approval is also a column on the record, so it can be filtered, grouped, counted and reported on like anything else.
Anyone can start a process. Nobody gets access to the data.
A workflow lives at company level; its data lives in one room. Its forms travel to exactly the people it covers — an employee in Sales requests leave without ever joining the HR room.
Four ways to identify a submitter
Anonymous, email capture, signed in, or employees of this company only — chosen per form, changeable later.
Every submission has a status
“My submissions” shows each case the person started, the step it is on and who it is waiting for.
Actors are reached where they are
Queue, notification and email for people outside the room; room chat for people inside it.
The map is the monitor
The design you approved is the dashboard you run the process on. Each step carries a live count and the age of the oldest case sitting on it, so a bottleneck is a number on a node rather than a report somebody has to build.
- Every case has a timeline: who acted, when, what they decided, what it created.
- Cases can be viewed as a board by step, and moved by an owner when reality demands it — recorded, never silent.
- Anything with no designed answer lands in the owner’s queue as needing attention.
- Case outcomes feed business intelligence, so cycle times and rejection rates are just questions you ask.
Approve leave · Priya S
Leave request · 2 days
Confirm delivery · 3 monitors
Purchase request · step 5
Revise your expense claim
Expense claim · changes requested
Sign off exit checklist · R. Nair
Employee exit · joined
Built for people who have to answer for it
A process that changes without a record is a liability. Every design, every revision and every decision inside a case is attributable.
Every change is a diff you approve
Say what should change; the agent redesigns the affected steps and shows what it added, changed and removed before anything is touched.
Versions, and cases that respect them
Each design is versioned. Cases already open finish on the version they started on, so a revision never rewrites history mid-flight.
Workflow admins, appointed
Only appointed workflow admins design, edit, pause or archive. Company owners and admins hold it implicitly.
A named owner, a real identity
Each workflow runs under an owner, and everything it does is done as that person. Ownership transfers cleanly, with a health check.
Enabled per company
Workflows are switched on for your office deliberately, and every service enforces it independently — the UI, the API and the agent.
Costs you can see before you commit
The design states which steps need the agent to reason and which are pure tool work, so the running cost is on the card you approve.
Any process you describe, eleven templates to start
Your AI project manager builds any custom process you can describe. For a head start, each template is a full design — the ask, the approvals and what happens after — ready to use as it is or shape to your company.
What enterprises ask first
No. Employees see the form, and under it the status of everything they have submitted. Approvers see the approval in their queue. Only members of the room that owns the workflow see the underlying tables, and only as the table permissions already allow.
A step can carry an SLA. Past it, the case is flagged; past the escalation window, it moves up a level. An outcome nobody designed for stops the case for attention in the owner's queue — it is never silently dropped.
Say what should change in a sentence, or edit it on the canvas. The agent redesigns the affected steps, edits the tables, forms and automations itself, and shows a diff — added, changed, removed — for you to approve. Cases already open keep the version they started on.
No. Every step leaves ordinary artifacts in ordinary apps — rows in tables, approvals in the approvals app, tasks, minutes, reminders, calendar entries. Turn a workflow off and everything it produced is still there, still exportable.
Building and testing a workflow is free on every plan, and it goes live with AI Office Pro or Enterprise. Designing it costs agent credits like any other command. At runtime, steps the agent can do with tools alone consume nothing; steps that need the agent to reason cost one agent run per case. The design tells you which is which before you approve it.
Workflow admins, appointed the way policy admins are. Company owners and admins are workflow admins implicitly. The workflow itself runs under a named owner, and ownership can be transferred.
Describe the process you keep chasing
Leave, expenses, purchases, onboarding, contracts, complaints — pick the one that costs your managers the most time this month, and watch it come back as a working process you can approve. Build it free on any plan, and go live with AI Office Pro.
Explore the rest of the platform
Every part of Qik Office shares the same rooms, the same people and the same permissions — so the work one part produces is immediately usable by the next.