Review submissions and manage approval or payment requests

Follow these steps

1. 01

   Open the experience admin dashboard and choose Form Submissions or Access Requests.

2. 02

   Search the respondent name and apply status, ticket and available form-answer filters. Open a response to inspect the answers and booking details.

3. 03

   For a requested application, choose Accept to approve it or Reject and supply the reason requested by the dialog.

4. 04

   For an accepted paid request, check the payment status. Approval alone does not confirm payment or guarantee entry.

5. 05

   Use the available pending-link actions to retrigger or cancel a link. Undo Cancel and Undo Reject are offered for eligible request states.

6. 06

   To change an unpaid request's ticket allocation, select eligible requests and choose Change ticket & send links. Review the replacement ticket quantities and reason, then generate the replacement links.

7. 07

   Use Email Recipients for follow-up and Download CSV for a submission export. Check the current filters before exporting.

Good to know

• Use form-answer filters to find relevant respondents before taking an action. A shortlist is decision support; your team still approves or rejects the request.
• Bulk cancellation stops active request payment links. It does not refund completed payments.
• A partial replacement result can mean the ticket change saved but delivery failed; the page reports this and may still let the attendee pay in the app.

If something isn’t working

• A customer remains Payment pending: ask them to check the payment result and review the Finance Hub; do not treat acceptance as payment success.
• Replacement links are unavailable: select requests that are still eligible for an unpaid replacement link. If Change ticket & send links remains unavailable or reports an unsupported action, contact support.
• No responses match: clear status, ticket, search and form-answer filters before assuming the form has no submissions.
• A rejection reason is required: enter a clear reason before submitting; it can be included in the customer notification.