Review and approve form submissions

Review new-customer requests, correct contact details, make a decision, and find every submission afterward.

public forms submissions review queue customers approvals

New Lead and Estimate Request forms create leads automatically. New Customer forms take a safer route: each request waits in Review Queue until an office user checks the contact details and approves, rejects, or deletes it.

Before you start: your account needs the PRO plan and access to Settings → Public Forms. The actions available to you depend on your Public Forms permissions.

  • 1

    Open Review Queue

    Select Settings → Public Forms, then open Review Queue. The queue lists pending New Customer requests; approved and rejected submissions remain in Submissions. The heading pill and tab badge show the number of requests in the current queue search, so both counts change when you search.

    Screenshot — Open Review Queue

    The Review Queue with pending requests and its count badge.

  • Who can review submissions

    Office users on a qualifying plan need Public Forms page and read access to open the queue and ledger. Edit contact, Approve & create customer, and Reject require update permission; only permanent Delete requires delete permission. Read-only viewers can search, select, inspect fields, and check duplicates, but none of those four mutation controls appears. An actor without page access is redirected away with an access error, and forged review or delete actions are denied without changing the submission.

  • 2

    Search and select a pending request

    Use Search pending submissions to narrow the queue by name or email, then select a row. Search is typo-tolerant; a search that removes the selected row also clears the detail pane. Before selection, the pane says Select a submission to review. A selected request shows its submitted fields, timestamp, and form inline as from “Form name”. Missing names appear as Unnamed, missing emails as an em dash, long queue values truncate, and full detail values wrap inside the card. A search miss shows Nothing to review. New-customer submissions land here. and a zero count without claiming that the account has no pending requests.

    Screenshot — Search and select a pending request

    An exact queue search narrowed the list to one selected New Customer request.

  • Check possible duplicate customers

    A request with candidates shows 1 possible duplicate customer or N possible duplicate customers and a Dup? marker. Each candidate explains the match as matches email, matches phone, or possible match for a weaker name match. The panel stays hidden when there are no candidates. Select View customer to inspect an existing record; it does not merge records, approve, or reject the request. Duplicate detection is advisory, so staff still choose the outcome.

  • 3

    Correct contact details

    Select Edit contact, update the prefilled Full name, Email, or Phone, then select Save changes. Full name is required. Email and Phone are optional; clearing either removes it from the stored request. Cancel closes the modal without saving. Correct the contact before approval because the saved values are used to create the customer.

    Screenshot — Correct contact details

    The Edit contact modal with the current submission values.

  • Fix validation errors on save

    Validation runs only when you select Save changes, not while you type, change, or leave a field. Email must have a valid shape and may contain at most 255 characters; Phone must use the same valid format as customer creation. An invalid save keeps the modal open, shows all relevant inline errors, and writes nothing. A successful save shows Contact details updated., refreshes the selected detail, and leaves the request pending for review.

    Screenshot — Fix validation errors on save

    Submit-only validation errors for a blank name and invalid phone.

  • 4

    Approve and create the customer

    After checking duplicates and contact details, select Approve & create customer. CleanOps creates the customer, removes the request from Review Queue, and confirms the result. The submission remains in the ledger with Customer created as its result.

    Screenshot — Approve and create the customer

    A successful approval confirmation after the customer was created.

  • 5

    Reject a request

    Select Reject when the request should stay in the audit trail but must not create a customer. CleanOps removes it from Review Queue and retains it in Submissions with Rejected as the result. Rejection does not offer an undo action.

    Screenshot — Reject a request

    The retained Reject Review submission shown in the Submissions ledger.

  • 6

    Permanently delete a request

    Select Delete only when the submission itself must be removed. In Permanently delete this submission?, Cancel leaves it unchanged; Delete Submission removes it from both Review Queue and the ledger and cannot be undone. A Customer or Lead already created from the submission remains.

    Screenshot — Permanently delete a request

    The permanent Delete submission confirmation and irreversible warning.

  • 7

    Find submissions in the ledger

    Open Submissions to see every retained response. Combine Form, Type, Channel, Result, and Date with Search name or email. Results include Lead created, Pending review, Customer created, and Rejected; New Lead, Estimate Request, and New Customer are available as types.

    Screenshot — Find submissions in the ledger

    The Submissions ledger with result filters and mixed submission outcomes.

  • List, filter, and empty states

    Each Form, Type, Channel, Result, and Date filter works alone or with the others and Search name or email. Channel is where the response arrived from — Hosted link, Website embed, QR code, Combined link, Combined embed, or Combined QR — so it is how you compare the places you published a form. Date supports previous/next month navigation, a selected range, Apply, Clear, and Today, Last 7 days, Last month, Tomorrow, Next week, and Next month. Use Prev, Next, page numbers, and Per page (10, 20, 50, or 100) when results span pages. A filtered zero result is an empty table; an account with no submissions instead says No submissions yet. They’ll appear here as visitors fill out your forms.

  • 8

    Export the filtered list

    Apply filters or search, then select Export CSV. The download contains the complete filtered result set—not only the visible page—with the columns Submitted, Form, Type, Name, Email, Channel, and Result. CleanOps neutralizes values that begin like spreadsheet formulas. Clear the filters and search first when you need the complete retained ledger.

    Screenshot — Export the filtered list

    A search narrowed the ledger to one matching rejected submission before export.

  • 9

    Follow submission notifications

    Open the notification bell and select a New form submission entry. A New Customer request opens Review Queue. A New Lead or Estimate Request opens the lead that CleanOps created automatically. The notification names the submitter, form, and request type so you can choose the right follow-up.

    Screenshot — Follow submission notifications

    Recent New Customer form-submission notifications that open Review Queue.

  • Recover from failed or stale actions

    If customer conversion fails, CleanOps shows Could not create the customer: …, creates no Customer, and leaves the request pending so you can correct it and retry. If another reviewer already approved or rejected it, a stale edit, approval, or rejection shows This submission has already been reviewed. and cannot create a duplicate Customer or second outcome. If the row was deleted, editing or deleting it shows This submission is no longer available. A forced review action is denied; a forced delete shows You do not have permission to delete submissions. and preserves the row. Refresh the queue after any stale result and continue with its current contents.

  • What happens after review

    Approval creates and links a Customer and records Customer created. Rejection records Rejected without creating a Customer. Permanent deletion removes only the submission; any Customer or Lead already created from it remains. New Lead and Estimate Request forms skip Review Queue and record Lead created.

  • Review tips and related guides

    • Treat duplicate warnings as a required check before approval.
    • Correct contact details before creating the customer.
    • Prefer rejection when you need to retain an audit trail; permanent deletion has no recovery.
    • Narrow the ledger before exporting when you only need one form, result, type, date range, or contact.
    • Related: create and share a public intake form, create a customer, and create a lead.

Need more help? If you can't find what you're looking for in our documentation, create a support ticket and our team will assist you.