K
Kris Granger
Currently, workflows are rigid and linear - they run every step regardless of what's actually needed, and they can't gather additional information or adapt based on the specific request. This creates inefficiency and incomplete outputs.
What I am trying to do currently is create a workflow for Opportunities that automatically creates a scope of work and tells the user what products will be needed.
What This Ideal Workflow Does:
  1. Starts Smart - When an opportunity comes in, the workflow:
  • Reads the opportunity details.
  • Automatically searches all our tools for everything we know about this client
(Adding to the "Unified API access" request)
  • Asks follow-up questions if anything is unclear or missing.
(Adding to the "continue chat" feature request)
  1. Adapts to Need - The workflow intelligently determines what's required:
  • If the request mentions replacing a server, it activates the "Server Standards" module.
  • If it's about networking, it activates the "Network Configuration" module.
  • Only runs the steps that are actually relevant to this specific request.
  1. Keeps Humans in Control - At each step:
  • Users can pause and have a conversation to refine requirements.
  • The system asks "Ready to proceed to the next step?" before moving forward.
  • Maintains all context from previous conversations.
REAL-WORLD EXAMPLE
Opportunity comes in: "Client needs server upgrade"
  • Workflow pulls all client history, current infrastructure, past tickets.
  • Identifies this needs the "Server Standards" step.
  • Skips irrelevant steps like "Website Development" or "Security Audit".
  • Allows user to discuss specific requirements at each step.
  • Proceeds only when user confirms readiness.