Customer operations / AI customer follow-up workflow
A customer follow-up workflow turns the records you share into a list of customers who need attention, with context and draft next steps. Tobin helps prepare the handoff for review; sending is confirmed separately during setup.
A useful first assignment starts with a clear source, a specific result, and someone to review it.
Provide the agreed customer tracker and project history. Decide which record is authoritative when two sources disagree, and which customers should be excluded.
Choose a clear rule: a completed project with no next appointment, a proposal awaiting a response, or an unresolved next step. Avoid using elapsed time as the only signal.
Share your tone, review owner, and any customers who should not be contacted. Confirm the supported channel and sending permissions separately.
Example assignment
Review the customer tracker for projects completed more than 14 days ago with no next appointment recorded. Prepare a list with the last project, source, reason for follow-up, and a short draft check-in. Flag missing information. Do not send messages or book appointments.
An example to adapt with our team. Sources, delivery, and supported actions are confirmed during setup.
The result to review
Fictional records, shown to make the handoff concrete. This example performs no external actions.
Site inspection completed 18 days ago. No next appointment appears in the selected tracker.
Hi Cedar team, checking in after the site inspection. Is there anything you would like us to follow up on?
Confirm the contact and check for a more recent conversation or appointment.
Check the agreed fields and reporting window. A missing appointment in one tracker does not prove that no appointment exists elsewhere; label that uncertainty.
Bring together the last project, the reason for the suggestion, and a concise draft. Do not invent a customer preference, promise a date, or imply an agreement.
The reviewer checks the recipient, context, tone, and proposed commitment. A draft or an approved item in the website example does not send a real message.
This is a workflow to scope with our team, not a promise of universal CRM or email support. Finding a customer, drafting a message, sending it, and scheduling a visit are distinct actions. Confirm availability and permission for each action before relying on it.
How access and setup workNo sending is implied by this workflow. Agree on a supported channel, permissions, and approval steps before enabling any external message delivery.
A shared tracker can be a starting point if its format and access are supported. The team checks the available records and helps define a useful first review.
We’ll work through the sources, the result, and what needs your review.