A company-scoped setter workflow joins message context, qualification, knowledge and follow-up state before deciding the next response.
3 messages → 1 context; the conversation-buffering use case, not three separate replies.
Name the system: lead operations and appointment setting
This is the setter workflow, not an unrelated support chatbot. The original archived appointment-setter export has forty-seven nodes, including forty-four non-note nodes, and is shown as a disconnected local import.
Keep the lead and company context together
Incoming message context belongs with the CRM record, the company knowledge and the qualification state. A short burst should not be treated as unrelated conversations just because messages arrive separately.
Decide the next action from the state
The workflow separates qualification, response handling and follow-up state.
Check the destination before calling it complete
The business outcome is a valid next handoff or appointment state, not merely a successful model response. This preview does not claim measured booking lift, client revenue or validated live delivery.
Supporting views
About this view
Local interface with lead context.
About this view
Local follow-up view, not a booking or revenue result.
About this view
47-node archived source, including 44 non-note nodes, imported locally. Inactive; no execution or credentials.
About this view
Native local source detail. No message or appointment was sent.