Workflows Directory
Find your team’s next superpower.
- Function: Analytics and reporting
- Function: Customer support and service
- Industry: Professional services
- Clear all filters
Results
25 workflow templates, showing 1 to 24
Analysis plan
Before anyone opens the spreadsheet, the owner or manager gets a one-page plan: the question restated, the hypotheses, the fields and periods needed, and the result that would change the decision. It runs no analysis and states no finding. You own the question and the criteria.
- Starts it
- Owner
- Brings
- export, notes
- Gets
- 6 outputs
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
Budget-versus-actual variance commentary
Before the month's results go to management, the finance lead gets written commentary on every line that moved past the threshold: the figures, the budget owner's explanation marked confirmed or to be confirmed, a bridge from budget to actual, and the questions still open. No cause is invented.
- Starts it
- Finance lead
- Brings
- export, notes, pasted text
- 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
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 campaign performance report
At the weekly or monthly reporting cutoff, the analyst gets a client report in the agency's format from the exports supplied: source figures, a drafted narrative, anomalies and discussion points. Gaps stay gaps, and every explanation is labelled a hypothesis.
- Starts it
- Analyst
- Brings
- export, notes, document
- Gets
- 6 outputs
Client report check log
Before a batch of client reports is released, the reporting lead gets a log, report by report, of household membership, periods, totals against the custodian statements, fee figures and missing sections, with every difference marked for correction. Nothing is released or sent.
- Starts it
- Reporting lead
- Brings
- export, notes, document
- Gets
- 5 outputs
Customer reply drafting
Every customer gets the reply your best person would write. Hand over the customer's message, your tone guide and your approved answers, and get back a draft in your voice where every statement and every promise traces to something you approved. A person on your team reads it, edits it and sends it.
- Starts it
- Support agent
- Brings
- notes, document, pasted text
- Gets
- 3 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
Dashboard brief
Before anyone builds the dashboard, the requester gets one brief that settles the work: the decisions it serves, what is shown, each metric's definition, the filters, notes on every source and who refreshes it. The requester approves what is shown and the definitions.
- Starts it
- Analyst
- Brings
- export, notes
- Gets
- 4 outputs
Dataset profile
Before anyone joins or relies on a new export, the analyst gets one profile of it: what one row stands for, where keys repeat, what is missing, which values look odd, and a numbered list of questions for the data owner. No data is changed and no verdict is given.
- Starts it
- Analyst
- Brings
- export, notes
- Gets
- 4 outputs
Help article from a resolved issue
Turn every answer your team works out once into an article the next customer finds on their own. Hand over a resolved ticket and your list of articles; get back a draft in your customers' words, with their details removed and every step traced to the ticket. Your knowledge-base owner decides what goes live.
- Starts it
- Support agent
- Brings
- export, notes, document, pasted text
- 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
Hiring pipeline status report
Each week your people lead or founder sees every open role on one page: applications at each stage, days open against the target, roles running late, pass-through between stages, which sources lead to interviews, and every blocker with its owner. It counts; it never assesses a candidate.
- Starts it
- People lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Lead form field review
When a client questions a long inquiry form or abandoned submissions, the conversion lead gets a field-by-field review: what each field is used for downstream, where people leave, and proposed labels, error messages and test questions. The lead and the client's data owner decide every change.
- Starts it
- Conversion lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Lead quality pattern review
When sales feedback or results raise a lead-quality concern, the acquisition lead gets a review of leads and their outcomes by source, page, location, device and timing, with cases to verify with sales and possible measurement faults listed.
- Starts it
- Acquisition lead
- Brings
- export, notes
- Gets
- 5 outputs
Metric definition reconciliation
When two reports give different numbers for one metric, the owner gets a page: the definitions side by side, the gap bridged step by step from supplied records, each cause marked shown or not, and a proposed common measure. The owner chooses.
- Starts it
- Analyst
- Brings
- export, notes, document
- Gets
- 7 outputs
Sales pipeline review
Each week your sales lead sees the whole open pipeline on one page: value and age by stage, what moved since last week, the deals at risk and coverage against your target. Every figure traces to your export, and the forecast number is left for a person to commit.
- Starts it
- Sales lead
- Brings
- export, notes
- Gets
- 9 outputs
Service inbox routing plan
When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.
- Starts it
- Service owner
- Brings
- export, notes
- Gets
- 5 outputs
Stale ticket sweep
Once a week the support lead gets one sheet of what the queue is hiding: tickets with no real activity past their limit, tickets left waiting on the customer with the three ways out of each, likely duplicates, and each person's load weighed by size and age. A person makes every move.
- Starts it
- Support lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Support escalation brief
When a support case must move to a specialist or manager, the support lead gets one brief: the customer's impact, a dated timeline from the ticket history, the evidence, the fixes tried, the workaround in place and the decision needed. Nothing goes to the customer.
- Starts it
- Support agent
- Brings
- export, notes, document
- Gets
- 8 outputs
Support service level definition
The support lead gets reply and resolution targets for every priority level, worked out from the team's own ticket history and the hours the team really has. Each target shows how often the team already meets it, and every gap comes back as a question for the lead to settle.
- Starts it
- Support lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Tracking event plan
Before analytics goes onto a website or app, the founder or product owner gets one plan: the events and properties worth collecting, when each fires, where it goes, what it is called and who owns it, each tied to a question the business needs answered. The owner approves what is collected.
- Starts it
- Founder
- Brings
- export, notes
- Gets
- 5 outputs
Website findability audit
An owner or marketer asking why the website is not found gets a plain report from saved copies of their own pages: what stops each page being reached, read or understood, the fixes in order, and the checks only a live look can settle. No ranking is promised.
- Starts it
- Owner
- Brings
- notes, document
- Gets
- 7 outputs