Jotform

Your assistant can pull the submissions across your account and read them, which is the part nobody has time for once a form is getting more than a handful a day. Ask it for the themes, the complaints that repeat, the ones that need a reply today. Jotform returns answers keyed by question ID rather than by the question text, so tell it which form you mean and check that it has matched the fields to the right questions before you trust the summary.

What you end up with. A written read of the week's responses with the repeated themes named and the ones needing a reply pulled out.

Start with it bringing you the information and you deciding.

Never without. Check that it mapped the fields correctly before believing the summary. Submissions come back keyed by question ID, and a mismatch turns one question's answers into another question's conclusion.

Built on: Get User Forms / Get User Submissions

It can list every form on the account with its status and creation date, then look at the submissions against each one and tell you which have gone quiet. Most accounts have a long tail of forms nobody remembered to switch off, still live on a page somewhere, still accepting entries into a folder nobody reads.

What you end up with. Your forms sorted by last submission, with the live-but-abandoned ones named so you can decide what to close.

Start with it bringing you the information and you deciding.

Never without. A quiet form is not always a dead form. Check where it is embedded before you close anything seasonal, since an annual registration form looks identical to an abandoned one for eleven months of the year.

Built on: Get User Forms / Get User Submissions / Get User Usage

Jotform already generates report links for the forms on your account, in Excel, CSV, printable chart, and embeddable table form. Your assistant can fetch the list and tell you which link is which, so you get the existing export rather than a rebuilt copy of it. Where no report exists yet, it can read the submissions directly and shape them into the columns you asked for.

What you end up with. The right export link in your hands, or the response data laid out in the columns you named.

Start with it bringing you the information and you deciding.

Never without. Check whether the report link is public before you paste it anywhere. Jotform report URLs are shareable by design, and form responses regularly carry contact details people gave you for one purpose only.

Built on: Get User Reports / Get User Forms / Get User Submissions

It can read your monthly usage, covering submissions, payment form submissions, and storage, and read the limits your plan carries so the two sit side by side. Worth asking before a campaign goes out rather than after, because a form that has hit its ceiling stops taking entries and the person filling it in is the one who finds out.

What you end up with. This month's usage against your plan limits, with the headroom you have left before a form stops accepting entries.

Start with it bringing you the information and you deciding.

Never without. Ask before the send, not after. A form that hit its limit mid-campaign loses the entries silently, and there is no record of the people who tried.

Built on: Get User Usage / Get User Details / Get System Plan

The account keeps an activity history and your assistant can fetch it filtered by action type and date. When a form suddenly stops collecting a field, or an email notification stops arriving, this is where the answer usually is. It reads the record and changes nothing.

What you end up with. A dated list of who did what to the account, narrowed to the window and the kind of change you asked about.

Start with it bringing you the information and you deciding.

Never without. Use this to find out what happened, not to build a picture of how a colleague works. Activity history is a debugging record and it makes a poor performance record.

Built on: Get User History / Get User Forms

Jotform organizes forms with labels, and the connector covers the whole loop. Your assistant can list the labels you already have, read which forms sit under each one, create the ones you need, rename or recolor an existing one, and take forms off a label or delete a label that has outlived its scheme. Describe the grouping you want, such as by client or by year, and have it show you the current tree and the proposed one side by side before it writes anything.

What you end up with. A label scheme that matches how you actually look for things, with your forms grouped under it and a saved list of what moved and what was removed.

Start with it doing the work and checking with you.

Never without. Never delete a label before reading what sits underneath it, because Jotform removes every sublabel along with the parent and the organization scheme does not come back. Have it list the label tree and the forms attached, keep that list, and approve exactly what you read.

Built on: Get User Folders / Get Label / Get Label Resources / Create Label / Update Label / Remove Resources from Label / Delete Label

It can copy an existing form with its questions and settings intact, which is the sane way to run anything annual or per client. The copy arrives as a new form you then edit, so the original is untouched and last year's responses stay where they are.

What you end up with. A new form carrying last year's questions and settings, ready to edit, with the original and its submissions left alone.

Start with it doing the work and checking with you.

Never without. Confirm which form it copied by name and open the copy before you publish it. Settings travel with the clone, including notification emails and payment configuration, and those are rarely still correct for the new one.

Built on: Get User Forms / Clone Form