This article covers how stacked eForms are sent and cancelled, how reminders work, and what your client sees from invite through to the last submission.
Sending a form stack
Who can send
Open the Entry form (the first form in the stack, marked Entry in the Form stack panel).
Use the normal Send Form action (same as a single eForm).
Only the first form in a stack can be sent. Sending a non-entry form is blocked.
What happens on send
OnboardMe checks funding for the full number of forms in the stack (1 request per form).
The entry form is sent like a normal eForm:
Status becomes Sent.
The client receives the invitation email (and SMS if enabled), unless notifications are muted for that send path.
Every later form is marked In Stack. They are billed with the stack but do not get their own invite.
There is no separate "stack email template". The entry form uses the normal eForm invitation content for that form / template.
Adding forms after send
You can still use Add next form after the stack is live, if funding allows.
The new form is charged immediately (1 request).
It is created with status In Stack and joins the end of the order.
The client reaches it only after submitting the previous forms, in order.
Resend and reminders
Manual resend / reminder behaviour follows the form that is actually Sent or Opened (usually the entry, until that form is finished).
Forms with status In Stack are not independently reminded. They are waiting for the client to arrive via the stack flow.
Practice automated reminders for eForms still apply to Sent / Opened forms as configured in Business Settings.
Proposals and engagements
When a stacked eForm is included with a proposal / engagement, acceptance can mark the stack as sent without firing a separate invite for each form. The client typically continues into the entry form from the proposal journey; remaining forms stay In Stack until reached in order.
Cancelling forms in a stack
Cancel uses the usual Cancel Form action, with stack-aware rules.
What gets cancelled
Cancelling a form cancels that form and all later unfinished forms in the same stack.
Forms already Submitted or Completed are left as-is.
Already Cancelled forms are skipped.
Confirmation copy explains that remaining unfinished forms in the stack will also be cancelled, and that submitted forms are left alone. Table actions may show a tooltip such as Cancel form (cancels remaining unfinished forms in a stack).
Rule for cancelling mid-stack
If you cancel a form that is not the first form, every earlier form must already be Submitted or Completed. Otherwise OnboardMe blocks the cancel with a message that earlier forms must be submitted before you can cancel the remaining forms.
Examples:
Cancel from the entry while later forms are still In Stack: cancels the entry and the remaining unfinished forms.
Client has submitted forms 1 and 2; you cancel form 3: cancels form 3 and any later unfinished forms. Forms 1 and 2 stay submitted.
You try to cancel form 3 while form 2 is still In Stack / Sent / Opened: cancel is blocked until earlier forms are submitted or completed.
Success messages include Form stack cancelled successfully (when cancelling from the entry) or Remaining forms in the stack cancelled successfully.
You cannot add new forms to a cancelled form stack.
What the client experiences
Invite: the client receives one invitation for the entry form (email and optional SMS), same style as a normal eForm link.
While completing: an alert shows Form X of Y with: "This is part of a multi-form set. Complete and submit each form in order."
After submit: OnboardMe advances them to the next form automatically when available. They may also see Form X of Y submitted and a Continue to next form action.
Reopening a finished form: if they reopen a form that is already submitted / completed, they can be directed to the next form that still needs action.
Last form: after the final submit, they get the normal thank-you experience (no continue).
Cancelled: a cancelled form shows that it was cancelled; answers are read-only where applicable.
Clients stay in the same recipient session for the stack, so they can move through forms without needing a fresh invite for each one.
What your team sees
Each stacked form is a separate row in eForms, with its own status (including In Stack).
Open any form in the stack to use the Form stack panel as a map of the set.
Review, export, PDF, and complete actions remain per form, the same as single eForms once a form has answers / is submitted.
Quick troubleshooting
Cannot send: confirm you are on the Entry form, funding covers every form, and the form is ready (name, recipient, questions).
Cannot cancel mid-stack: finish or wait for earlier forms to be submitted / completed first, or cancel from an earlier unfinished form if you intend to stop the whole remaining journey.
Client stuck / cannot continue: check that recipient emails match across the stack, that later forms are not cancelled, and that the previous form was submitted.
Unexpected In Stack rows: these are waiting forms. They are expected after send (and for non-entry forms before send when already attached to a stack).
Related
Still need help?
Contact us