Skip to main content

Promise-to-Pay

How Stuut captures, processes, and tracks customer payment commitments.
When a customer tells the AI call agent or writes in an email reply that they intend to pay, the AI extracts the promised date and payment method and creates a Promise-to-Pay task for you.The AI does its best to interpret natural language — for example, “I’ll send a check tomorrow” said on March 5th becomes March 6th. You can always adjust the date manually.
When a customer is vague, the agent assumes the latest reasonable date: “next week” becomes next Sunday, and “next month” becomes the end of next month. Payment processing days are then added on top (see below).Hover over the ? next to the saved date to see how the agent interpreted what the customer said. If your team prefers a different interpretation, add a Playbook article describing it.
From the Promise-to-Pay task, you have several options:
  • Acknowledge by clicking the checkmark — confirms the promise and pauses dunning for those invoices until the date.
  • Edit the date with the pencil icon if you want a different one.
  • Close individual invoice promises if some don’t apply (e.g., one was already paid).
  • Close the whole task with no action if the promise isn’t valid.
Acknowledging vs. closing If you close a PTP task without acknowledging the dates, dunning will NOT pause. You must click the checkmark for the pause to take effect.
Yes. You can override the date on the invoice, in the task, or in the agent automation log.
With this setting on, Stuut acknowledges a promise automatically only when the agent identified both the specific invoice and an explicit date. Anything less certain still becomes a task for your team to review.
Stuut adds payment processing days based on the payment method to allow time for funds to actually arrive:Example: customer says on March 1 they’ll mail a check tomorrow (March 2). The acknowledged PTP date becomes March 16 — preventing a false broken-promise flag before the check has time to arrive.
Not by default. Invoices with an active promise are left out of the invoice tables in other outreach. To include them, turn this on under Agent settings → Promise to pay.
If payment isn’t received by the acknowledged PTP date (plus a grace period of 1–2 days), Stuut creates a Broken Promise task. It includes the original promise details — date, method, invoices — so you have full context for follow-up. Outreach will resume on those invoices.
Promise-to-Pay and Broken Promise tasks show the original email or call alongside the task.
Yes. Add a Playbook article such as “Don’t create a promise-to-pay task if the email only contains remittance details.”
Yes. If a customer replies with a screenshot of a payment confirmation or a remittance advice, the AI will attempt to read it and may update the PTP information automatically.