# Recover Adobe Sign declines with alerts and follow-ups

> The moment a signer declines an Adobe Acrobat Sign agreement, ping your deals channel in Slack, open a Linear follow-up, and draft a re-engagement email in Gmail.

- Workflow type: agent
- Services: Adobe Acrobat Sign, Slack Bot, Linear, Gmail
- Categories: Sales, Operations
- Published: 2026-07-17

## What it does

- Watches Adobe Acrobat Sign for agreements that get rejected or declined by a signer
- Posts a short alert to your deals channel in Slack with the counterparty, deal reference, and decline reason if available
- Opens a follow-up ticket in Linear assigned to the account owner with the agreement link and a suggested next step, skipping duplicates if a recent open ticket already exists for the same agreement
- Drafts a warm re-engagement email in Gmail addressed to the signer so the account owner can review and send

## What you'll need

- An Adobe Acrobat Sign account that can send agreements and receive webhooks for the rejected event
- A Slack workspace with a channel your deals team already uses
- A Linear workspace with the team where deal follow-ups live
- A Gmail account for the person who will send the re-engagement email

## Prompt

When a signer rejects or declines an agreement in Adobe Acrobat Sign, run a full recovery play so the deal does not go silent.

Trigger: an Adobe Acrobat Sign webhook fires on the agreement rejected lifecycle event. Only proceed for rejection or decline events; ignore other statuses.

Step 1 — Fetch the context. Use Adobe Acrobat Sign Get Agreement to pull the agreement name, current state, sender, and any rejection reason or decline note surfaced on the agreement. Then use Adobe Acrobat Sign Get Agreement Members to list every participant so you can identify the signer who declined (the participant whose status is REJECTED) and grab their name, email, and company.

Step 2 — Post a short Slack alert. Use Slack Bot Send a Message to post to the deals channel. Keep the message tight: agreement name, counterparty name and company, the signer who declined, and the decline reason if Adobe returned one. Include a link to the agreement in Adobe Sign. Do not paste the full agreement metadata; the goal is a scannable alert, not a data dump.

Step 3 — Decide whether to open a Linear follow-up. Before creating anything, use Linear Search Issues to look for a recent open issue that already references this agreement id (search the agreement id string across issue titles and descriptions, and only count issues that are not archived and not in a completed or cancelled state). If a match exists, skip Linear entirely and note in the run summary that a follow-up ticket already exists. If none exists, use Linear Create Issue to open a new one assigned to the account owner. The title should name the counterparty and mark it as a declined agreement. The description should include the agreement link, the decline reason, the signer's name and email, and a suggested next step (for example: reach out within 24 hours, offer to walk through concerns on a call, or revise the terms and resend).

Step 4 — Draft a warm re-engagement email. Use Gmail Create a Draft addressed to the signer who declined. The draft should acknowledge the decline without being defensive, briefly reference the decline reason if one was given, and offer to jump on a short call to talk through their concerns. Keep it warm, human, and under 120 words. Leave the draft in Gmail so the account owner can review and hit send; do not send it automatically.

Business rules: match the account owner to a Linear user by email where possible. If no clear owner can be resolved, leave the Linear issue unassigned and note that in the Slack alert. If Adobe Sign returned no decline reason, say so in both the Slack message and the Linear issue rather than making one up. Never send the Gmail message — always leave it as a draft.

## How to customize

- Change which Slack channel receives the alert or the tone of the message
- Change how the account owner is resolved and which Linear team receives the follow-up
- Tune the re-engagement email voice, length, or call to action, or route the draft to a different Gmail account
- Adjust the duplicate check window (for example, only skip if an open Linear ticket for the same agreement was created in the last 7 days)

## FAQ

### What counts as a decline in Adobe Acrobat Sign?

Adobe Acrobat Sign fires a rejected lifecycle event when a signer explicitly declines to sign an agreement. This workflow only reacts to that event, not to cancellations, expirations, or agreements that are simply sitting unsigned.

### Will the workflow send the follow-up email automatically?

No. It only creates a draft in Gmail so the account owner can review the tone, add any personal context, and hit send themselves. Nothing goes to the signer without a human in the loop.

### How does it avoid spamming Linear with duplicate follow-ups?

Before creating a new ticket, it searches Linear for an existing open issue that already references the same agreement. If a recent open ticket exists, it skips Linear and just posts the Slack alert.

### What if Adobe Sign does not include a decline reason?

Some signers decline without leaving a note. In that case the workflow says so in the Slack alert and the Linear ticket rather than inventing a reason, so the account owner can chase it up directly.

### Can I use this with a shared inbox instead of a specific person's Gmail?

Yes. Connect the Gmail account you want the draft to appear in. Many teams use a shared sales@ or deals@ account so anyone on the team can pick up the follow-up.

Use this prompt in General Input: https://www.generalinput.com/prompts/recover-adobe-sign-declines-with-alerts-and-follow-ups