Prototype

Meeting to CRM follow-up

Turn meeting context into reviewable, traceable next actions.

Department · sales / operationsComplexity · 3/5Human gate · requiredData · medium
Outcome

Reduce post-meeting admin and missed follow-ups.

02 / Interactive workflow

Inspect the responsibility chain.

Select a node to see its input, action, output, risk and control.

System / Meeting ends
Input

Calendar context and recording link

Action

Trigger workflow

Risk

False trigger

Control

Limit source and time window

Click a node to inspect the boundary. Human and AI are not interchangeable.

03 / Business view

What this workflow changes

Reduce post-meeting admin and missed follow-ups.

Metrics

  • Time to next action
  • CRM completeness
  • Follow-up adoption
04 / Technical & governance

Boundaries before automation

  • Unconfirmed commitments must not be written to CRM.
  • Customer-sensitive context must be minimized by permission.

Implementation notes

  • Start with one meeting source and one CRM field set.
  • Keep the first release draft-and-review only.
Prototype / Research labels are intentional. This workflow is a starting point for diagnosis, not a promise that your systems are already connected.