Follow-ups fail in the gap between a conversation and a record. Someone promises to send a document in Teams, the channel moves on, and the task survives only in somebody’s memory.

An AI teammate can help, but only if you design the hand-off properly. The goal is not more messages in the channel. It is a visible owner, a next action and a reviewable draft.

Choose one queue first

Start with a single operational queue, such as:

  • Quotes awaiting a follow-up.
  • Documents missing from an onboarding checklist.
  • Meeting actions without an owner.
  • Supplier replies expected this week.

Do not connect every department on day one. A small queue gives your team something concrete to inspect and correct.

Use a standard assignment

A Teams assignment should describe the job, not merely mention the bot. For example:

Review the approved quote list. Prepare follow-up drafts for items due today, assign each to its current owner, and flag missing contact details. Send nothing without approval.

This instruction identifies the source, the output and the boundary. It also avoids the dangerous assumption that “follow up” automatically means “send”.

Separate preparation from sending

A supervised workflow has two states:

  1. Prepared: the teammate drafts the message, attaches relevant context and proposes the next action.
  2. Approved: a person reviews the content and authorises the send or record change.

Keep those states visible in Teams. A compact review card should show the owner, the customer or record reference, the proposed action and the reason it was selected. Staff should not need to reconstruct the decision from a long chat.

Design the exception path

Routine cases are only half the job. Decide what happens when the teammate finds:

  • Two possible owners.
  • Conflicting amounts or dates.
  • A request for revised terms.
  • An angry reply.
  • Missing permission to view a record.

The correct action is to stop and escalate with context. Do not train the workflow to produce a plausible answer at any cost.

Review the queue, not just the messages

A weekly review should ask whether ownership was correct, drafts used current records and exceptions reached the right person. Remove templates that repeatedly need rewriting. Narrow any permission that is not necessary for the job.

Teams becomes useful here because the assignment, review and escalation remain close to the people doing the work. MSPE can configure this as part of a managed AI teammate role, with ERPNext optional as the system of record.