1. Thank caller
What would you like to support?
Captures donor pledge intent, amount range, restrictions, follow-up preference, and stewardship notes.
What would you like to support?
Do you have an amount or range in mind?
How should the team follow up?
What would you like to support?
Do you have an amount or range in mind?
Collect donation pledge calls. Thank the donor, ask campaign, pledge amount or range, restrictions, contact details, and follow-up preference. Do not collect full payment details.
{
"outcome": "Donation pledge follow-up outcome",
"fields": [
{
"description": "donor name captured during the call.",
"name": "donor_name",
"required": true,
"type": "text"
},
{
"description": "phone number from caller id captured during the call.",
"name": "phone_number_from_caller_id",
"required": true,
"type": "text"
},
{
"description": "campaign captured during the call.",
"name": "campaign",
"required": true,
"type": "text"
},
{
"description": "pledge amount or range captured during the call.",
"name": "pledge_amount_or_range",
"required": true,
"type": "number"
},
{
"description": "restriction captured during the call.",
"name": "restriction",
"required": true,
"type": "text"
},
{
"description": "follow up preference captured during the call.",
"name": "follow_up_preference",
"required": false,
"type": "text"
},
{
"description": "notes captured during the call.",
"name": "notes",
"required": false,
"type": "text"
}
]
}
AI: Hi, I am an AI call workflow for Donation pledge follow-up. What would you like to support?
Caller: I want to pledge to the building fund.
AI: Do you have an amount or range in mind?
Caller: Please have someone email me the giving options.
Make the first screen and opening line match what the caller will actually get. For Donation pledge follow-up, the promise should be narrow enough that a caller understands the purpose before sharing details or scanning a QR code. Avoid broad claims like "we can help with anything"; a specific promise produces cleaner calls and clearer follow-up.
Decide which fields are required before the call can be considered complete. A practical first version should capture donor name, phone number from caller id, campaign, then send a summary that the workflow owner can act on without replaying the call. If a field is not used for routing, qualification, scheduling, or review, remove it from the first launch.
Write down the cases that should not be automated. Use human review for major gift, tax or legal question, caller wants payment processing so the workflow stays useful without pretending to handle every edge case. Review the first real calls before connecting higher-risk actions or expanding the workflow.
Use it when the call is repeatable, the team already knows the information they need, and the caller benefits from speaking instead of filling out a form. It works best for nonprofits, churches, fundraisers.
The first question should identify the caller goal and gather enough context to continue naturally. For this template, start with: "What would you like to support?". Keep follow-ups short so the caller does not feel like they are reading a form over the phone.
Save a structured result with donor name, phone number from caller id, campaign, plus a summary, completion status, and handoff reason when needed. The owner should be able to act on the result without interpreting raw transcript text.
Human handoff should trigger when the caller needs judgment, asks for a person, gives conflicting answers, or matches one of the workflow-specific rules: major gift, tax or legal question, caller wants payment processing.
The template includes prompt, questions, output fields, sample transcript, handoff rules, and a live call entry point.