Describe what a procedure should do, what edits you want to make, or why it's not working — and Fin Operator handles the rest. It builds complete procedures from plain-language descriptions, edits existing ones with full validation, and diagnoses execution issues by pulling the trace from a specific conversation.
Note: All changes go through a proposal system. Fin Operator proposes, you review, you approve.
What you can do
Create
Describe what the procedure should accomplish and what data it needs to collect. Fin Operator handles the branching logic, step ordering, and validation.
Example prompts:
"Create a refund procedure that collects order number and reason, and auto-approves for amounts under $50"
"Build a procedure for handling billing disputes that routes to a specialist if the amount exceeds $500"
"Create a returns procedure that asks for the order number, checks if it's within the return window, and either processes it or explains why it can't be returned"
Edit
Modify existing procedures — add steps, change conditions, update data collection fields, or restructure branching logic.
Example prompts:
"Update our returns procedure to add an approval step for items over $200"
"Change the routing in our billing procedure to send enterprise customers to the dedicated team"
"Add a data collection step for email address to our account recovery procedure"
Audit
Have Fin Operator analyze your procedures for structural issues, unreachable steps, impossible conditions, or build-time safety problems.
Example prompts:
"Audit our procedures for any issues"
"Check if our refund procedure has any unreachable steps"
"Review all our procedures and flag anything that looks wrong"
Debug
Investigate why a procedure behaved a certain way in a specific conversation. Fin Operator fetches the execution trace and the conversation transcript, then walks through exactly what happened — which steps fired, which branches were taken, and why.
Example prompts:
"Why did this procedure fail for this customer?" (with conversation link)
"This customer says they weren't asked for their order number — can you check what happened?"
"The refund procedure approved a $500 refund that should have been escalated — what went wrong?"
Tips
For new procedures, describe the desired outcome and the data to collect — let Fin Operator handle the branching logic.
For debugging, share the specific conversation where the procedure behaved unexpectedly — Fin Operator needs the conversation link to pull the execution trace.
Complex procedures benefit from an iterative approach — start simple, test with a few conversations, then add complexity.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts