Guided Notebook
Design a small, human-supervised workflow that turns a missed call into a timely customer follow-up.
Business outcome
Compatibility paths
Coding approaches
Deployment targets
The Lab remains useful without selecting a coding agent and does not require one model provider.
Known limitations
Learn
Define the outcome before choosing tools.
Instructions
Review the business outcomes, identify the minimum data needed, and keep message delivery outside the agent's authority.
A missed call is an event, not permission to contact a person automatically. Separate event intake, drafting, approval, and delivery.
Architecture
Separate deterministic control from agent drafting.
Instructions
Trace data from the webhook to the reviewer and identify every external boundary.
The backend controls state and the agent supplies only a proposed draft.
Backend
Validate and normalize the incoming event.
Agent Runtime
Propose text using bounded context.
Human
Approve or reject the proposed follow-up.
Relationships
Provide validated context.
Present the draft without sending it.
Prompt · Optional
Create provider-independent drafting instructions.
Instructions
Edit the example without inserting real contact details, credentials, or private customer records.
Demonstrate a bounded drafting instruction that remains independent of model provider.
{{service-category}}A public description of the requested service category.
Example: home-repair consultation
Security Stop
Stop before connecting customer systems.
Instructions
Confirm the minimum data, scoped credential types, logs, human approval, and emergency stop before implementation.
Pause and understand the boundary before continuing.
Data visible
Read capabilities
Write capabilities
Credential types
webhook-signing-secretscoped-api-tokenAffected systems
Logging considerations
Emergency stop / rollback
Disable intake and delivery independently before investigating failures.
Risk notes
Human approval required: Yes
Test
Define checks without executing external actions.
Instructions
Use synthetic event data and verify each expected state transition manually or in an isolated test environment.
Validation instructions
Submit a synthetic event to a test adapter and inspect only redacted state transitions.
Regression criteria
Human Approval
Make the external action an explicit human decision.
Instructions
Review the draft, destination, and consequences before choosing approve or reject.
Proposed action
Allow a separately implemented delivery service to send the reviewed follow-up.
Why approval matters: Customer contact is externally visible and may affect trust or legal obligations.
Consequences
If approved
The reviewed draft may advance to an authorized delivery step.
If rejected
The draft is closed or returned for revision without delivery.
