Pause reminders when a client disputes a request

Pause the disputed item deliberately

Pause the reminder, give the disagreement an owner and state what needs deciding. That keeps the engagement moving without making the client answer the same question again.

Your request system handles the chase. When the reply contains supplier invoice PDFs that need to become an Excel schedule, try ParseMill for that next step: extract, review against the source and download a workbook. Reminder scheduling stays in your current tools.

A pause is not acceptance or withdrawal. It means a named decision is pending. Record the reason, owner and review date so the request cannot disappear into an indefinite holding state.

Find the controls that actually send messages

List every reminder route for the disputed item: portal automation, scheduled email and manual task lists. Karbon: Client Requests documents native reminder behavior in Karbon; Microsoft: Follow-up flags describes personal follow-up alerts in Outlook. A staff reminder and a message sent to the client are different controls. Verify which one has been paused and retain an internal reminder to resolve the dispute.

Use the current instructions for the system you have. Do not assume changing a visible request status disables every scheduled message. Inspect the actual sending settings or pending work, and check the next planned follow-up before considering the pause effective.

Record a narrow dispute

Synthetic example: request R24 asks Cedar Joinery for a lease schedule. The client says the equipment was purchased outright and challenges the request.

Other outstanding statements remain in their normal workflow. The reviewer may withdraw R24 and create a different requirement, but that outcome should be recorded rather than inferred from the objection.

Resolve the substance before resuming

Check the original scope, source of the requirement and client's explanation. If the request was wrong, acknowledge the correction and remove only the affected obligation. If evidence is still needed, explain why and restate the exact item or acceptable alternative approved by the reviewer.

Avoid marking the client unresponsive while the firm itself is deciding what to ask for. The next due date should reflect the clarified request and any agreement with the client. Preserve the original timeline so workload reporting can distinguish client waiting time from internal decision time.

Test the stop and restart

Before resuming reminders, confirm the current wording, recipient, due date and remaining evidence. Check that old message drafts do not ask for the superseded item. If the requirement was withdrawn, close the pause with the approving decision and ensure future recurring templates do not recreate it automatically.

A useful audit is to inspect a paused case just before its former reminder time and verify that no client message is due. the related workflow guide explains the broader chasing process. Use the workflow audit checklist to record recurring dispute causes; unclear scope may be the real problem rather than insufficient reminders.