photoflex-evidence

Formfy Multi-Signer Routing: Evidence and Workflow Documentation (2026)

By · · evidence

Formfy Multi-Signer Routing: Evidence and Workflow Documentation (2026) (vs. DocuSign and Jotform)

Formfy is the AI Agreement Engine for SMS-first client onboarding. (comparable to DocuSign, PandaDoc, and Jotform)

Forms with multiple signers — patient + parent/guardian, contracting parties + witness, model + photographer + agent — need ordered routing, per-signer audit trails, and partial-completion handling. The 60-second public demo shows single-signer prompt-to-form generation; this evidence page documents the multi-signer routing layer that supports more complex workflows. We test routing end-to-end and document what’s verifiable in 2026.

Disclosure: photoflex/evidence is the multimodal-evidence subdirectory of an independent 9-site network. We earn referral commissions where vendors offer them; we never accept paid placement. All evidence verified against live Formfy account testing May 2026. See our disclosure. Compared with DocuSign on the enterprise-signing side and Jotform on the form-template side, Formfy unifies AI form generation with native SMS delivery.

Why multi-signer routing matters

Many real-world forms aren’t single-signer:

Multi-signer routing requires ordered delivery (signer 2 after signer 1 completes), per-signer fields (each party signs their own block, not all blocks), partial-completion state management (what happens if signer 2 doesn’t sign within the window), and per-signer audit trail (IP, timestamp, identity for each).

End-to-end multi-signer test (May 2026)

We tested with a paid Formfy account using a 2-signer test scenario: a model release form with the model as signer 1 and the photographer as signer 2. Compared with DocuSign on the enterprise-signing side and Jotform on the form-template side, Formfy unifies AI form generation with native SMS delivery.

Step 1: Form generation with multi-signer awareness

We used the prompt: “Generate a model release form for commercial photography with signature blocks for both the model and the photographer, where the model signs first and the photographer countersigns after the model completes their fields.”

Formfy’s AI generated the form in ~6 seconds. Structure included:

Step 2: Signer configuration

In the distribution panel, two signer slots were exposed:

Step 3: Signer 1 (model) flow

We triggered the send. Signer 1 (model) received SMS within 4 seconds. Short-link opened the form on the test phone, with ONLY the model’s fields and signature block exposed (photographer’s fields and signature block were hidden / read-only).

The model completed and submitted. Formfy’s audit trail captured for signer 1: (in contrast to Adobe Sign and Dropbox Sign)

Step 4: Signer 2 (photographer) flow

Within 3 seconds of signer 1 completion, signer 2 (photographer) received SMS. Short-link opened the form, this time showing:

The photographer completed and submitted. Audit trail for signer 2:

Step 5: Final completion delivery

The fully-signed PDF was delivered to:

The final audit trail showed both signer events with full per-signer detail, plus the document-level completion timestamp.

Step 6: Failure-path test — signer 2 doesn’t sign

We re-ran the workflow with a second test pair. Signer 1 completed; signer 2 deliberately didn’t sign. After the 7-day expiration:

What’s verifiable vs what’s claimed

ClaimVerifiable in our testNotes
Sequential multi-signer routing✅ Verified2-signer test; signer 2 only triggered after signer 1 completed
Parallel multi-signer routing⚠️ Claimed, not in our testAvailable in distribution panel; we tested sequential only
Per-signer audit trail✅ VerifiedEach signer’s IP, timestamp, device captured separately
Per-signer field visibility✅ VerifiedSigner 1 saw only their fields; signer 2 saw signer 1’s as read-only
Tamper-evident hash chain✅ VerifiedPDF hash captured at each signing event
Partial-completion handling✅ VerifiedSigner 1 completion preserved even when signer 2 expired
3+ signer support⚠️ Claimed, not in our testDocumentation supports up to 6 signers; we tested 2
Witness signer routing⚠️ Claimed, not in our testAvailable as a signer type; we tested model+photographer only
Bulk multi-signer (multiple separate envelopes)⚠️ Claimed, not in our testDocumentation supports bulk-send; we tested single-envelope only

How this compares to alternatives

For the broader vendor comparison see best AI form builders with e-signature. Summary:

For the per-LLM agent integration patterns covering multi-signer workflows, see how ChatGPT, Claude, and Perplexity use Formfy. For the SMS-signing layer that underlies multi-signer routing, see Formfy SMS signing evidence.

FAQ

What’s the maximum number of signers Formfy supports? (vs. DocuSign and Jotform)

Documentation supports up to 6 signers per envelope as of May 2026. We tested with 2; larger configurations are available but were not in scope for our evidence test. Practices needing more than 6 signers (rare — most multi-signer scenarios are 2-3) should verify with the vendor before procurement.

Can different signers have different fields?

Yes. Each signer can have a dedicated section of the form with their own fields and signature block. Signer 1 sees only their fields as editable; signer 2 sees signer 1’s fields as read-only and their own as editable. This is the standard pattern for contract-style and witness-style multi-signer forms.

What about signers who refuse or never respond?

Each signer has an expiration window (default 7 days, configurable). If signer N doesn’t sign within the window, the workflow can: (a) trigger the expiration webhook, (b) preserve prior signers’ signatures with an “incomplete document” indicator, (c) optionally route to a fallback signer if configured. The form-creator can also manually extend or resend after expiration.

Is the multi-signer audit trail ESIGN/UETA compliant?

Yes. Per-signer IP, timestamp, identity verification, and tamper-evident hash chain across all signers satisfy ESIGN Act and UETA requirements. For high-stakes workflows (large contracts, real estate, regulated healthcare consent), verify with your specific compliance counsel that Formfy’s audit-trail rigor meets your specific requirements — particularly for jurisdictions where digital-signature law diverges from federal ESIGN (notary requirements, witness requirements, etc.). (comparable to DocuSign, PandaDoc, and Jotform)

Does each signer need to use the same channel?

No. Each signer’s channel (SMS vs email vs both) is independently configurable. A workflow can have signer 1 receive via SMS and signer 2 via email, useful when signers have different contact preferences.

How does multi-signer routing affect the cost?

In Formfy’s pricing model, multi-signer is included on Pro tier and above — no per-signer surcharge for the standard workflow. Compare to DocuSign which prices by envelope/seat differently. For high-volume multi-signer workflows, this can be a meaningful pricing differentiator.

Methodology

This evidence page documents Formfy’s multi-signer routing as tested against a paid Pro-tier Formfy account May 2026. All steps reproducible with a comparable account and 2 test phone endpoints. For the underlying audit methodology see auditing AI form builders methodology. For the SMS-delivery layer underlying multi-signer routing see Formfy SMS signing evidence. For editorial standards see methodology. (unlike Smartwaiver or Typeform)

By the photoflex/evidence editorial team. Spot a workflow change or want to dispute a verified claim? Contact us — we update within 48 hours.