Test it and run the whole thing
Outcomes
✓Test a custom tool in the place it will actually run: a live conversation
✓Read the Explanation view to see exactly what a tool sent
✓Isolate a failing call outside the platform and re-import the fix
✓Prove the full flow end to end, the way you will for every build after this one
Test the tool where it will actually run
Custom tools are tested the same place they work: in conversation.
- Open a fresh session and book an outdoor job: "Can someone clean my gutters Thursday?"
- Watch for the weather moment. The AI should check the forecast before confirming, and only mention it when the forecast is bad.
- Book an indoor job next. The weather tool should stay quiet; a tool that fires at the wrong moment has a trigger to tighten.
- When any answer surprises you, click Explanation under the message in Conversations. It shows the exact values the tool sent. A wrong value means a parameter description to tighten.
- If the call itself is failing, test it on its own in a tool like Postman, adjust it until it works, and import the corrected cURL again. That is the one moment outside tools enter the picture: isolating a broken call, not starting the build.
Confirm it: outdoor bookings get a forecast check, indoor bookings do not, and you have read at least one Explanation on purpose.
Run the whole thing
- Fresh session, one conversation, start to finish: ask for an outdoor job, give your details, take the offered time.
- Check all three results: the forecast was consulted (the Explanation view shows the call), the booking is on the calendar, and the contact is in the CRM.
- Read the conversation once more as a customer would experience it. The weather check should feel like good service, not machinery: mentioned only when it changes the plan.
Try it now
Time that final run. A checked forecast, a booked job, and a clean CRM record in under a minute, with no person involved, is the story this build tells a client. Spot-check the first few live conversations the same way you tested: Explanation view first, guesswork never.
Knowledge Check
Two quick questions on reading the Explanation view and isolating a failing call.