When a customer commits to paying by a specific date, the Task Manager treats that date as the task deadline and automatically monitors the promise. Everything happens without manual intervention the task reacts when the date is kept, missed, or withdrawn.
What happens to the promise | What happens to the task | Automatic? |
Recorded from the task | Due date set to the promised date, status Waiting | Yes, when you complete the action |
Recorded elsewhere | Attached to the related task, due date brought forward if earlier | Yes |
Broken (date passed, unpaid) | In progress, due today, one chase action; new task if none open | Yes |
Cancelled or rejected | In progress, action to ask for a new commitment; new task if none open | Yes |
Kept (paid) | Nothing, unless your playbook has a rule for it | Only with a playbook rule |
Understanding what a promise does to a task
A promise to pay sets the task's due date to the promised payment date
The task moves to "Waiting" status, removing it from your active queue until the promised date arrives
The system continuously monitors the promise for status changes
Recording a promise from a task
Use the Record Promise to Pay action on any task
If AI detected the promise in a customer email, the form pre-fills with the detected date and amount
Completing the action does three things: activates the promise, sets the task due date, and changes status to Waiting
When promises are recorded elsewhere
Promises created from the customer page, detected by AI, or imported are automatically linked to related open tasks
The task due date only moves earlier never relaxes deadlines already set
A new task is only created if the AI determines one is needed
When the promise is broken (missed)
Task automatically moves back to "In progress"
Due date resets to today
A follow-up action is created to chase the payment
A new task is created if no open task exists
When the promise is cancelled or rejected
Task moves back to "In progress"
An action is created to request a new payment commitment
A new task is created if none is open
When the promise is kept (paid)
Task remains unchanged unless your Task Playbook has a rule for kept promises
Without a playbook rule, the collector closes the task normally
Controlling this behavior
Use Classification Rules to decide whether promises join tasks, open new ones, or are left alone
Write rules in plain language the AI follows them over defaults
Use Task Playbook rules to define what happens to tasks when promise status changes
See Understanding Promise to Pay Statuses to learn how each status affects your tasks