This bot is available for free, and its usage does not consume credits. For more information about credit usage, refer to this article.
How the Forbid declining revision bot works
Prevent altaFlow signers from declining document revisions with the Forbid declining revision bot. The bot automatically hides the Decline option in the Other Actions menu — recipients must accept or negotiate proposed revisions instead of outright declining them. Ideal for critical contracts where changes need to be discussed rather than rejected.
Use case example: Imagine a legal team working on a critical contract that requires multiple rounds of review and approval. In this scenario, the Forbid declining revision bot can be used to ensure that all proposed revisions are either accepted or discussed, avoiding the risk of important changes being outright declined without operations being saved like user input and data transfer between documents.
How to set up
When the bot works by default:
The Forbid declining revision bot activates when a document is opened by a recipient.
Add the bot depending on your needs as described in this article. You may install this bot both in the step or using the All bots tab. Find the Forbid declining revision bot in the list of bots and click Install bot.
Alternatively, the bot is also available as a part of the steps settings. All you need is to access the required step settings, go to the Advanced settings>Signing process, and check the Forbid recipient to decline revision option.
Action settings
The option is enabled automatically. No actions are required from your side.
Conditions
Set conditions to hide the Decline option only in specific scenarios. Common use cases include:
Final approval stage: Hide Decline only at the last approval step where recipients should either sign or escalate — not decline outright.
Mandatory compliance contracts: Enforce for documents where the type field equals "NDA", "Compliance", or "Regulatory" — legally binding docs that shouldn't be silently rejected.
VIP client workflows: Apply only when the client tier field equals "Enterprise" — ensures white-glove clients get personal follow-up instead of a decline.
Multi-round negotiations: Hide Decline during middle revisions of a negotiation, allow it only on the first or final round.
Learn more about bot conditions usage in the dedicated bot execution conditions article.
If no condition is set, the bot hides the Decline option whenever a document is opened by the recipient.
Advanced settings
Fine-tune how the bot enforces the Decline block:
Run frequency: The bot runs on every document open by default. No configuration needed for typical use.
Failure handling: If the bot fails to hide the Decline option (rare), decide whether to proceed with the workflow or halt for admin review.
Document tags: Tag documents where declining is forbidden (e.g., "decline-locked") for audit trails — especially useful in compliance-heavy workflows.
Learn more about adjusting Advanced settings in the bot setup glossary.