Support inbox drafter

Ask Once

Two weeks of support email for a legal-transcription app (called "the app" here). Each email goes into one lane. If one help page clearly answers it, a reply is drafted for a person to check and send. Anything time-critical, about money, confidential, about a filed record, or from an upset customer is held for a person. Questions that several accounts keep asking with no help page are flagged. The decisions come from short, fixed rules, not a live model, so each one can be explained in a sentence.

Result

Turn on JavaScript to sort the inbox.

Inbox, 14 to 25 September

    Pick an email to see its lane, the rule that decided it, and the reply.

    How I checked it

    The lanes, checked in this order

    The first rule that fires decides. The hold rules (the first five) always run before any help page is matched, so a refund or a sealed hearing never gets an automated answer, even when a page matches.

    LaneRuleRules gaveMy labels

    Agreement with my labels

    The labels and the rules were written together, so this checks that the rules do what I meant. It does not show accuracy on a real inbox.

      Six edge cases, run live on this page

      Each one feeds purpose-written emails through the same rules and checks the lane.

        Assumptions

        See every phrase list

        Questions I'd want answered

        1. Which questions fill the inbox most, and which come by phone instead?
        2. When a reporter writes during a live proceeding, what is the fastest path to a person today?
        3. Which replies must a person always send, and is anything missing from money, confidential hearings and filed transcripts?
        4. Do agency admins and freelance reporters ask different things, and should they get different replies?
        5. Where do the answers live today: the docs site, saved replies, or someone's memory?