> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Complete the due-diligence call

> Book the post-verification call and distinguish a recorded booking from final due-diligence approval.

After KYC becomes verified, the Owner setup flow advances to the due-diligence call. Tapp embeds a booking experience, records a successful booking through a webhook, and keeps due-diligence approval as a separate status.

## Who can do this?

Owners can use the information with the scope described. Only Owners may start or resume KYC. API status read access exists for all three store roles even though the current Admin UI presents progress only to the Owner.

## Where

Open the **Set up your shop** pill after the KYC step is verified. The active step becomes **Book your call**. If Tapp has already recorded a booking, the state changes to **Check your inbox**.

## Steps

1. Select **Book your onboarding call** to open the embedded calendar.
2. Choose an available slot and complete the booking using the information requested by that booking surface.
3. Wait for the booking-success confirmation. Tapp leaves the confirmation visible briefly, returns to overview, and refreshes KYC status.
4. Use the booking communication sent to the signed-up email for the appointment details, then attend the scheduled call.
5. Return to Tapp afterward. Only a due-diligence state of approved completes this step; a booked timestamp alone does not activate approval.
6. If the state is rejected, the current UI offers booking another call.

## Platform notes

The booking is embedded from Cal.com. A `bookingSuccessful` event triggers an optimistic booked state, while the durable `due_diligence_call_booked_at` value is written by the booking webhook. The UI distinguishes pending, approved, and rejected. It does not expose reviewer notes or a guaranteed approval timeline.

## Market notes

The same Owner workflow is used for GB and DE. Appointment availability and review outcomes are external state and are not guaranteed by this article. The call does not replace any market-specific legal, tax, billing, or fiscal responsibility.

## Evidenced troubleshooting

If the calendar fails to initialize, reload once and keep the exact error context for @sebestil. If booking succeeded but Tapp still shows Book your call, wait for the webhook-backed refresh, reopen the setup pill, and check the signed-up email. Do not create overlapping bookings merely to force the status.

## Related articles

* [Understand KYC status](/en/kyc/understand-kyc-status)
* [Troubleshoot KYC](/en/kyc/troubleshoot-kyc)