Routing and repetition, handled.
The document you send fifty times a month shouldn't be rebuilt fifty times. Flows keeps signing order, templates, bulk sends, reminders and approvals running on their own — so the only human step left is the signature.
Templates, bulk send and API are Business features — R239/seat per month billed annually, or R299 month-to-month.
Saved once. Sent whenever the next hire happens.
The busywork between "ready" and "signed", automated.
Signing order has been core KuduDoc from day one. Flows adds everything around it — the templates, the bulk sends, the reminders, the approvals — so repetition stops costing you afternoons.
Templates
Build the envelope once. Send it forever.
Fields, signing order, reminders and expiry — saved as a template your whole team shares. The next offer letter or lease is a name and an email address away, not an afternoon of setup. Shared templates are a Business feature.
See the Business planBulk send
One template. A whole list of recipients.
Upload a recipient list and every person gets their own envelope, their own signing link and — once they've signed — their own sealed document with its own audit trail. Policy acknowledgements, seasonal contracts, annual renewals: one send, tracked individually. A Business feature.
Included on BusinessReminders · expiry · approval
The chasing happens without you.
Automatic reminders nudge whoever's next in line. Expiry closes envelopes that have gone quiet, so nothing lingers half-signed. Approval-before-send* lets a manager check the outgoing document before a client ever sees it. And conditional routing* handles steps that only sometimes apply — a guarantor who's only brought in when surety is required.
There's even an envelope type for documents that must stay on paper: physical-signature envelopes* print the pack, everyone signs in ink, and Scan & Seal brings it back in with the same proofs as anything signed on screen.
See how Scan & Seal works See signing order in actionDelivery · where signers actually are
WhatsApp delivery* — because email is where requests go to die.
Coming as a Business add-on: signature requests sent as WhatsApp utility-template messages, reminders that actually get read, and the completed, sealed PDF delivered straight back over WhatsApp — attachments up to 100 MB. SMS delivery* joins it for signers without smartphones. DocuSign's early-access WhatsApp Delivery claims completion around seven times faster than email; that's the bar we're building to.
One honest line, though: WhatsApp is a delivery channel, not a signing surface. The signature itself still happens on the secure signing page, where consent, intent and the audit trail are captured properly.
See plans and add-ons* On our roadmap — in build, not live yet.
1 → many
one template, bulk-sent — every recipient gets their own sealed document
R239
per user per month on Business, billed annually — team seats, bulk send and API included
0
manual chasing — reminders and expiry run on their own
3 proofs
on every completed document — bulk-sent or not
Signing order is core. The heavy lifting is Business.
Sequential and parallel routing is part of KuduDoc signing on every plan — including Free. Reusable templates start on Professional at R166/seat per month billed annually; bulk send and API access are Business features at R239/seat. Both are priced on the pricing page, not behind a sales call.
* On our roadmap — in build, not live yet.
The guarantor only hears about it when the condition fires.
Frequently asked questions
Three things: shared templates, bulk send and API access — all on the Business plan at R239/seat per month billed annually (R299 month. Signing order itself, sequential or parallel, is core KuduDoc and works on every plan, including Free. The full breakdown is on the pricing page.
No — and that matters. Every recipient on the list gets their own envelope and, once they sign, their own completed document with its own certification signature, SHA-256 fingerprint, timestamp and audit trail. Fifty recipients means fifty individually sealed documents, each one independently verifiable.
That's conditional routing, and it's on our roadmap — in build, not live yet. A step will apply only when a condition is met: the classic South African example is a guarantor who's only routed in when the agreement actually requires surety. When the condition isn't met, that recipient is never contacted and the flow simply skips ahead. Today, sequential and parallel signing order already works on every plan.
It puts a named approver between "prepared" and "sent". The document waits until they've reviewed it, their approval is recorded, and only then do recipients receive anything. It's the difference between hoping the junior got the lease right and knowing someone checked before the tenant saw it. Approval-before-send is on our roadmap — in build, not live yet — headed for the Business plan.
After the window you set, an unsigned envelope closes itself — its links stop working and nothing can be half-signed into limbo afterwards. If the deal is still on, send a fresh envelope from the same template in seconds. Reminders exist to make expiry the exception, not the routine.