This article explains how to create a stacked eForm set, add more forms, reorder them, update the client, and remove forms from the stack.
Before you start
Have your eForm templates ready (recommended), or plan to build forms from blank.
Know who the recipient is (existing client or new recipient name / email, and mobile if using SMS).
Confirm you have enough subscription requests or wallet balance for every form in the stack (1 request per form).
Stacked eForms may be rolling out as a beta capability. If you do not see Stack templates or the Form stack panel, contact OnboardMe support about access.
Option A: Create a stack from templates (eForms)
Go to eForms and start creating a new eForm (for example Create New eForm / create flow).
Choose Stack templates. The helper text explains that you pick several templates and create them as one ordered stack.
In the Stack templates modal:
Add templates from the left Templates list into Stack order on the right.
Add them in the order clients should complete them.
You can add the same template more than once if needed.
A new stack needs at least 2 templates.
Use Move up / Move down (or equivalent controls) to fine-tune order, and remove any template you added by mistake.
Continue with Next: client (when shown).
Choose Existing client or New recipient, then complete Recipient name, Recipient email, optional Recipient mobile, and Send SMS if required. The same client and recipient details are applied to every form in the stack.
Click Create stack.
OnboardMe creates the ordered forms and opens them for review. You can edit each form before sending.
Option B: Grow a stack from the form editor
You can start with one form and attach more forms using the Form stack panel in the eForm editor.
Open an eForm in the editor.
Find the Form stack panel (with the stack / layers icon).
Finish the basics on the current form before adding another: a real form name (not an untitled placeholder), client or recipient name + email, valid mobile if SMS is enabled, and at least one section with at least one question.
Click Add next form.
Choose how to add the next form (blank, from a template, or multiple templates via Add templates to stack / Add to stack).
Help text on a live stack notes that forms are completed in order and that stacking uses 1 request per form (including forms added after send).
The first form shows an Entry badge. Later forms are numbered in order.
Reorder forms
Open any form in the stack so the Form stack panel is visible.
Use Move up or Move down on a form row.
Order matters: the form in position 1 becomes the Entry form. Only the entry can be sent, and clients work through the stack in this order.
Reorder before you send whenever possible so the invite matches the form you intend clients to start on.
Remove a form from the stack
In the Form stack panel, choose Remove from stack on the form to detach.
If only one form would remain, OnboardMe clears stack membership and that remaining form behaves like a normal single eForm again.
Change the client or recipient on a stack
If you change the client / recipient on a form that belongs to a stack, OnboardMe asks:
Update client on stack?
This form is part of a stack. Apply the new client and recipient details to every form in the stack, or only this form?
All forms in stack (recommended in most cases): keeps recipient details consistent so the client can continue through the set smoothly.
This form only: updates just the form you are editing. Use with care. Mismatched recipient emails can block moving between forms in the stack.
Cancel: discard the change.
Stacks on proposals, engagements, and onboarding
Where your create flow offers Stack templates on a proposal / engagement eForm step or onboarding eForm step, you can build a stack the same way as from eForms.
The engagement stores a pointer to the stack entry form.
When a proposal is accepted, the stack can be marked sent without a separate invite email for each form: the entry becomes available through the proposal acceptance path, and later forms remain In Stack until the client continues.
Removing / detaching an unsent engagement form can remove the whole unsent stack. Confirm before discarding.
For the classic single-form proposal path, see Send an eForm with a Proposal.
Tips
Name each form clearly (for example "1. Business details", "2. ID documents") so staff and the Form stack panel stay easy to scan.
Review each form in the stack before sending the entry.
Keep recipient email consistent across the stack unless you have a deliberate reason not to.
You cannot add forms to a cancelled form stack. Start a new stack instead.
Related
Still need help?
Contact us