Workflows Directory

Find your team’s next superpower.

Results

25 workflow templates, showing 1 to 24

  • 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
  • Contract amendment trace

    Before a question about a signed contract goes to counsel, the contracts manager has one dated history of the provision that matters: every signed document in order, each version quoted with its document and section, every gap marked, and a list for the lawyer to confirm. It never says which wording controls.

    Starts it
    Contracts manager
    Brings
    export, notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts (filtered by)
    • Software technology (filtered by)
    • Consumer brands
  • Contract intake brief

    When another party's agreement arrives, counsel gets a one-page intake brief: what it is, read from its titles, the parties as named, what is missing, the requester's purpose and date, and the reviewer your own routing rules name. It comments on no term; counsel decides.

    Starts it
    Contracts manager
    Brings
    notes, document, pasted text
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts (filtered by)
    • Software technology (filtered by)
    • Manufacturing
  • Contract issues table for counsel

    Before counsel negotiates a vendor or customer agreement, the contracts team hands over one cited issues table: every clause quoted with its section, the playbook position it meets or departs from, the playbook’s fallback wording copied beside each departure, and the approver your matrix names. Counsel decides.

    Starts it
    Contracts manager
    Brings
    notes, document, pasted text
    Gets
    7 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts (filtered by)
    • Software technology (filtered by)
    • Consumer brands
  • Contract renewal and notice register

    From your signed agreements and amendments, the contracts manager gets a register for counsel to confirm: each term, renewal and notice clause quoted with its section, cancel-by and send-by dates proposed only under counsel's own counting rules, and the windows sorted by proposed send-by date. Nothing is sent.

    Starts it
    Contracts manager
    Brings
    export, notes, document
    Gets
    5 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts (filtered by)
    • Software technology (filtered by)
    • Manufacturing
  • 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 support and service (filtered by)
    • Software technology (filtered by)
    • Consumer brands
  • 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
  • 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
  • Inbound demand or claim intake record

    When a demand, claim or subpoena arrives, the company's lawyer gets one intake record the same day: who sent it, what it asks, every date it states, the facts and citations it relies on, related matters, where the records are, and a question on keeping them. It rates nothing and recommends nothing.

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

    Prepares work for a lawyer. Not legal advice.

  • Invention disclosure brief for patent counsel

    Before the first call with patent counsel, the founder or engineering lead has one factual brief: the invention in the inventor's words, who contributed what and when, every outside demonstration, sale, talk or publication with its date and audience, and the records still missing. Counsel decides.

    Starts it
    Founder
    Brings
    export, notes, document
    Gets
    7 outputs

    Prepares work for a lawyer. Not legal advice.

  • IP ownership and licence question table

    Before an agreement or statement of work is signed, IP counsel gets one table of the ownership, assignment, licence, background-IP and confidentiality clauses, each quoted with its section, set against the company's own IP positions and led by whether the assignment words counsel expects were found.

    Starts it
    Contracts manager
    Brings
    notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Legal hold custodian tracker

    Once counsel has issued a legal hold, your legal operations lead keeps one tracker for counsel: every custodian and system in counsel’s scope, who has acknowledged and who is overdue, who has left or changed role, the refresh date counsel set, and reminders copied from counsel’s own text for a person to send.

    Starts it
    Legal operations lead
    Brings
    export, notes, document
    Gets
    3 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts (filtered by)
    • Software technology (filtered by)
    • Manufacturing
  • NDA check against counsel's approved positions

    Before anyone signs a proposed NDA, counsel gets every clause quoted with its section and set beside the positions counsel has approved: matching, departing or not covered. Any obligation beyond confidentiality sends the whole NDA to counsel. The check never says an NDA is ready to sign.

    Starts it
    Salesperson
    Brings
    notes, document
    Gets
    6 outputs

    Prepares work for a lawyer. Not legal advice.

  • Open-source licence inventory for counsel

    Before a release ships or an acquirer asks, counsel and the engineering lead get every open-source package listed with its licence as found, the file and line where it was read, and the duties your own policy attaches to it. A missing, custom or conflicting licence is marked needs review, never cleared.

    Starts it
    Engineering lead
    Brings
    export, notes, document
    Gets
    5 outputs

    Prepares work for a lawyer. Not legal advice.

  • Outside-counsel invoice questions

    When a law firm’s invoice arrives, legal operations has one worksheet ready: every line set against the agreed rates, the approved matter budget and the company’s own billing guidelines, each difference written as a neutral question for the firm. Nothing is sent, paid or rejected until people decide.

    Starts it
    Legal operations manager
    Brings
    export, document
    Gets
    10 outputs

    Prepares work for a lawyer. Not legal advice.

  • Release notes draft

    The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 outputs
    • Product management
    • Customer support and service (filtered by)
    • Software technology (filtered by)
  • 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
  • Support ticket triage

    Your queue manager opens the morning’s tickets already sorted: each one with a category, a priority and a route, and the reason for all three in a line. The tickets that cannot wait sit at the top, stopped for a person to decide.

    Starts it
    Queue manager
    Brings
    export, notes, document
    Gets
    4 outputs