# Six booking-action checks you can run locally — 30s silent walkthrough

**URL:** <https://community.retellai.com/t/six-booking-action-checks-you-can-run-locally-30s-silent-walkthrough/3763>\
**Category:** Share Your Videos\
**Created:** [October 21, 2026, 6:11am UTC](https://community.retellai.com/t/six-booking-action-checks-you-can-run-locally-30s-silent-walkthrough/3763 "2026-10-21T06:11:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasonjibuilds](https://yyz2.discourse-cdn.com/flex008/user_avatar/community.retellai.com/jasonjibuilds/32/2925_2.png) [@jasonjibuilds](https://community.retellai.com/u/jasonjibuilds)\
**Post date:** [October 21, 2026, 6:11am UTC](https://community.retellai.com/t/six-booking-action-checks-you-can-run-locally-30s-silent-walkthrough/3763/1 "2026-10-21T06:11:50Z")

</div>

I packaged six synthetic booking scenarios each for Retell-shaped and Vapi-shaped exports, with a matching contract policy and expected results. They run in CallCheck without signup or provider keys.

30-second silent walkthrough:

[https://call-check-voice-20261020.activesnow6.chatgpt.site/media/booking-check-walkthrough-20261021.mp4](https://call-check-voice-20261020.activesnow6.chatgpt.site/media/booking-check-walkthrough-20261021.mp4)

The cases are:

- A correct recorded booking.
- A successful tool response with the wrong date.
- Two booking invocations for one expected action.
- A booking invocation with no correlated result.
- An email argument that differs from the independent test-script value.
- Explicitly incomplete result evidence.

With the included policy, each six-call file produces 1 pass, 4 failures and 1 unknown. You can change a value, run again and follow the finding to its source event.

Guide, fixture download and browser checker:

> **[CallCheck — catch the wrong booking](https://call-check-voice-20261020.activesnow6.chatgpt.site/guides/retell-tool-results?utm_source=retell&utm_medium=community_tutorial&utm_campaign=trial-20261021)**
>
> Inspect the actions behind recorded voice calls. Free to try, no signup, call data stays in your browser.

To reproduce:

1. Download and unzip the pack, then open the checker from the guide.
2. Import retell-fixtures.json or vapi-fixtures.json.
3. Open “Edit tool names & contracts,” paste booking-contract.json and run the checks. Leave the expected-date override blank.

For your own workflow, change book\_appointment and the argument/result paths to your actual contract. The email check compares against a known test expectation; it does not assess speech recognition. Recorded tool results still need an independent calendar/CRM read-back when you need proof of saved state.

The 30-second silent walkthrough uses actual product screenshots and synthetic records. No customer calls or live provider connection are shown.

Which argument or returned result is hardest to verify in your current workflow?
