SplitTesting / Client onboarding / System 03 of 04
2021Recorded work
Booked calls and onboarding team handoffs
Bring a scheduled onboarding call into the client record and give the team the links needed to join or reschedule it.
- Noah’s contribution
- Connected Calendly bookings to the client-directory record, onboarding-call fields and team notification.
- Historical stage
- Historical booking implementation walkthrough; no final adoption or exception-path verification.
- Part of the business
- SplitTesting overview ↗
- Calendly
- Monday.com
- Slack
- Make / Integromat
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- Calendly booking event
Retrieve the event, invitee and event-type context for the booked call. - Client-directory records
Use the Monday directory as the shared source of client identity. - Find the booking’s client
Search for the directory item whose email matches the booking address. - Record the booked-call milestone
Update the call-specific onboarding columns on the matched item. - Onboarding team notification
Include the call’s join and reschedule links in the team channel.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Booking | Invitee email and event details | Provide the context needed for the call handoff. |
| Client-directory item | Matched email and onboarding-call fields | Keep the booked-call state against the client’s operating record. |
| Onboarding notification | Booking confirmation, join link and reschedule link | Give the team the call information in its existing coordination channel. |
Inside the system / 01
A booking belongs in the operating record
The Calendly scenario started when an event was booked. It retrieved the invitee and event type, collecting the pieces needed for the following steps. The client lookup then searched the Monday client-directory board for an email address matching the one used for the booking.
After finding the client, the workflow updated the columns relating to the onboarding call. The appointment was therefore represented in the operating record used for client onboarding, rather than existing solely in the booking tool. The walkthrough describes the search and update sequence; it does not demonstrate every unmatched-booking path.
Inside the system / 02
Put the useful links beside the notification
The workflow posted a message to the onboarding channel confirming that a call had been booked. It included both the link to join the call and the link to reschedule it. Those links carried the immediate next actions into the channel where the team coordinated onboarding.
This was a specific handoff between tools: Calendly supplied the booking information, Monday held the client context and Slack communicated the event. Updating the call fields and sending the message were separate steps in the scenario. The recording does not establish automatic attendance tracking, calendar conflict resolution or rescheduling synchronization back into every client field.
Inside the system / 03
Keep a booked call distinct from completed onboarding
A booked call confirms an appointment, not attendance or completed onboarding. This workflow recorded the booking and notified the team; it did not mark the wider onboarding process complete.
The lookup used the email address supplied for the booking. Alternate-email matching, duplicate directory items and missing client records remain unresolved in the available account. Related white-label recordings describe their own completion checks and progression rules, but those exact rules are not treated as SplitTesting behavior. The historical walkthrough establishes a concrete booking-to-record handoff; it supplies no measured attendance, retention or onboarding-conversion result.
Within SplitTesting