Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

82 workflow templates, showing 73 to 82

  • 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

  • Submittal register review

    The project engineer gets one register of every required submittal: what has arrived, the review status as recorded, the documents still missing and the long-lead items at risk against the date each order must be placed. Nothing is routed, accepted or ordered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 outputs

  • Subscription billing exception sheet

    Before a subscription billing run, or when a customer disputes a charge, the billing specialist gets a sheet tying each account's plan, quantity and invoice lines to the approved price mapping and the seat or usage records, with doubtful matches kept open.

    Starts it
    Billing specialist
    Brings
    export, notes
    Gets
    7 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

  • Three-week look-ahead constraint review

    Before the coordination meeting, the superintendent gets a brief that sets each planned activity of the next three weeks beside what could hold it up: trades sharing an area, unfinished predecessors, open approvals, late deliveries and unanswered RFIs. The superintendent confirms the sequence and assigns the follow-up.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    7 outputs

  • Volunteer shift options

    A volunteer lead gets draft shift options once an event's availability replies are in: each role's needs set against who volunteered, the requirements on record and the shifts already confirmed, with every uncovered position shown. The lead checks and confirms; nothing is assigned or sent.

    Starts it
    Volunteer lead
    Brings
    export, notes
    Gets
    4 outputs
    • People and HR
    • Government (filtered by)
    • Established businesses (filtered by)

  • Weekly status requests to outside counsel

    Every Monday, in-house counsel has a draft status request for each outside firm that owes one: what has happened since the last update, the dates on record to confirm, decisions pending and spend against budget, plus the matters skipped and why. Counsel edits and sends each one.

    Starts it
    Legal operations manager
    Brings
    export, notes, document
    Gets
    2 outputs

    Prepares work for a lawyer. Not legal advice.

  • Win-loss review

    Once a quarter your sales lead sees, from the deals you closed, where the losses ended, which kinds of deal you win and lose, what the largest deals show, and which findings rest on enough deals to act on. Actions are proposed in proportion to the evidence, and nothing in your sales system is changed.

    Starts it
    Sales lead
    Brings
    export, notes, document, pasted text
    Gets
    8 outputs
    • Sales
    • Engineering firms (filtered by)
    • Software technology (filtered by)

  • Workflow inventory

    When the ownership and status of your automated workflows come up for review, the platform owner gets one inventory built from the exports supplied: environments, enabled states, last run, queued runs and owner gaps. Quiet workflows become questions, not removal lists.

    Starts it
    Platform owner
    Brings
    export, notes
    Gets
    7 outputs