Workflows Directory
Find your team’s next superpower.
- Function: Customer support and service
- Function: Project and delivery
- Business situation: Growth & scaling
- Clear all filters
Results
46 workflow templates, showing 1 to 24
Appointment confirmation and no-show follow-up
The front desk gets tomorrow’s bookings from the appointment export with the practice’s approved script or message filled in for each, every reply recorded once staff have called, and today’s no-shows with open slots to offer them. Staff make every call and every diary change.
- Starts it
- Front-desk coordinator
- Brings
- export, notes, document
- Gets
- 7 outputs
Cancellation request response
When a customer asks to cancel or cut back, the account manager gets one page: the request and the reason in the customer's words, the account's recent history, only the options your business already approved that fit that reason, and a reply that confirms the choice and what happens next. A person sends it.
- Starts it
- Account manager
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Chargeback response pack
When a card dispute lands, the store owner or finance lead gets one pack: the dispute matched to its order, the evidence its reason calls for marked found or missing, a response drafted well inside the deadline, and the store's dispute ratio for the month. A person decides whether to contest and submits it.
- Starts it
- Finance lead
- Brings
- export, notes, document, pasted text
- Gets
- 7 outputs
Churn risk and save plan
Once a quarter, the owner or account lead sees why customers really left, read from your own cancellation notes and records, how many left for each cause, and one change to try for each, with an owner, a start date and the count that will show whether it helped. A person decides every change.
- Starts it
- Owner
- Brings
- export, notes, document, pasted text
- Gets
- 6 outputs
Client document request tracker
When a client sends its first batch of records, the engagement manager gets the request list brought up to date: each item and period marked received, incomplete, mentioned only or missing, plus a short follow-up draft. The manager judges what is sufficient and approves anything sent.
- Starts it
- Engagement manager
- Brings
- export, notes, pasted text
- Gets
- 5 outputs
Client findings validation document
Before research becomes recommendations, the engagement lead sends the client one document: each material finding beside its evidence, the implication proposed and a clear request to confirm, correct or defer it. Nothing is added that the evidence does not show.
- Starts it
- Engagement lead
- Brings
- export, notes, document, pasted text
- Gets
- 5 outputs
Client-status update preparation
Every client gets an accurate status update on schedule, drafted from the notes and the task list, with confirmed dates kept apart from estimates and the client’s open decisions in plain view.
- Starts it
- Project manager
- Brings
- export, notes, document, pasted text
- Gets
- 5 outputs
Completed engagement file review
The quality partner gets a worksheet that tests finished engagement files against the firm's own checklist: each item linked to the engagement letter, workpaper or sign-off that answers it, with any open finding, and the missing evidence listed. The quality partner confirms findings and assigns remediation.
- Starts it
- Quality partner
- Brings
- export, notes
- Gets
- 4 outputs
Customer feedback themes
Each month your support lead sees what customers keep telling you: tickets, disputes, reviews and survey comments grouped into themes with counts and quotations, the three issues most worth fixing with a proposed fix and owner, and a note for customers once a fix ships. A person decides every fix.
- Starts it
- Support lead
- Brings
- export, notes, document
- Gets
- 5 outputs
Customer satisfaction detractor follow-up
Every week your support lead gets each low satisfaction or recommendation score with the ticket behind it: the customer's own words, what went wrong as far as the ticket shows, a suggested owner and a draft message, plus the trend and a warning wherever the numbers are too thin to read. A person sends every message.
- Starts it
- Support lead
- Brings
- export, notes, pasted text
- Gets
- 7 outputs
Daily production report
When a shoot day wraps, the production coordinator gets a draft daily report from the call sheet, timecards and department reports: hours totaled as written, schedule changes noted, and every missing or overlapping entry listed as a query. The production manager checks it.
- Starts it
- Production coordinator
- Brings
- export, notes, document, pasted text
- Gets
- 5 outputs
Discipline interface issue register
After a coordination meeting exposes conflicts between disciplines, the design coordinator gets one register: each conflict from the minutes, linked to the clash-export rows and model revisions involved, with the lead who owns each system and the decision still needed. Nothing is resolved.
- Starts it
- Design coordinator
- Brings
- export, notes, document
- Gets
- 5 outputs
Engagement margin review
Midway or at close, the partner and finance lead get one worksheet for an engagement: recorded time, agreed fee, billed to date and supplied costs by workstream, the gaps that limit it, and the questions the team must answer. No cost rate is invented.
- Starts it
- Finance analyst
- Brings
- export, notes
- Gets
- 6 outputs
Engagement staffing plan
When several engagements want the same people, the resource lead sees the collision before kickoff: role needs against free days, leave and competing assignments, week by week, with two or three staffing options. The resource lead and partners choose.
- Starts it
- Resource lead
- Brings
- export, notes
- Gets
- 6 outputs
Freight shortage record packet
When a receiver reports missing or damaged freight, the claims coordinator gets one packet lining up dispatch quantities, warehouse scans, bill of lading, proof of delivery, photos and the customer report, with each unanswered question listed. It assigns no fault and sends nothing.
- Starts it
- Claims coordinator
- Brings
- export, notes
- Gets
- 6 outputs
Help centre gap review
Once a period, your support lead sees what the help centre is missing, read from that period's tickets and search log: questions agents answered by hand, articles that fell short, articles search could not find, and one gap list ranked by the tickets an article could have saved. The lead decides what is written.
- Starts it
- Support lead
- Brings
- export, notes
- Gets
- 6 outputs
Implementation blocker brief
When a customer's setup milestone slips, the implementation lead gets one brief: the missing inputs, the unresolved access and data questions and the dependencies behind the delay, each with its source and an owner, plus points to raise with the customer.
- Starts it
- Implementation lead
- Brings
- export, notes
- Gets
- 6 outputs
Incoming referral completeness check
When a referral arrives, the coordinator gets one checklist: what the referring office sent, held against the practice's own referral checklist, what is missing or needs a new copy, and a draft request for exactly those items. A clinician sets urgency; nothing is sent until the coordinator approves it.
- Starts it
- Referral coordinator
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Matter budget and status summary
The responsible partner sees one matter whole: scope, phases against their dates, the budget against fees to date and the projected total, a red, amber or green status with the rule behind it, risks and next actions with owners. Built from the time export and the matter plan, never a view on the merits.
- Starts it
- Matter lead
- Brings
- export, notes, document
- Gets
- 10 outputs
Missed milestone client reply
When a client challenges a delay, a deliverable or an earlier commitment, the account director gets a draft reply and an internal action note that keep confirmed facts apart from proposed recovery steps and the decisions still needed. Nothing is sent.
- Starts it
- Account director
- Brings
- export, notes, document, pasted text
- Gets
- 2 outputs
Pilot build readiness brief
Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.
- Starts it
- Build lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Premortem before a decision
Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.
- Starts it
- Owner
- Brings
- notes
- Gets
- 4 outputs
Program outcome map
Before an evaluation, the program and evaluation leads get one map linking each activity to the outcome it is meant to serve, with proposed measures, data sources, assumptions and the questions the evidence cannot yet answer. It claims no impact.
- Starts it
- Program lead
- Brings
- export, notes
- Gets
- 8 outputs
Project handover readiness check
When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.
- Starts it
- Project manager
- Brings
- export, notes
- Gets
- 6 outputs