AlterCall / Sales engagement / System 03 of 06
2021Recorded work
Course engagement and sales follow-up
Follow up according to whether someone has registered, started the course or booked a conversation.
- Noah’s contribution
- Noah developed email/SMS follow-up, optimized the existing foundation and documented the workflow and exceptions.
- Historical stage
- Documented historical course-funnel configuration and retrospective implementation accounts
- Part of the business
- AlterCall overview ↗
- Kajabi
- GoHighLevel
- Close
- Make / Integromat
- Zapier
- Lucidchart
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.
- Kajabi registration
A course registration looks up the lead and creates or updates the CRM relationship. - Course video started
The course-start tag triggers the Zapier and Make handoff when a participant watches. - Discovery call booked
A participant’s booking is a separate event with its own CRM and KPI updates. - Closing call booked
The scheduler event checks the Principles lead-source condition before its update. - CRM contact and engagement tags
Close and GoHighLevel retain identity, registration, start and booking context. - Has the participant started?
GoHighLevel evaluates course-start state after the configured wait. - Already joined the community?
The messaging condition checks membership context before sending the group prompt. - Course-start reminders
Send the relevant follow-up to registered participants who have not started. - Discovery-call text sequence
Use the course-start context to invite the participant to a discovery conversation. - Community invitation
Send the community-focused message when the joined condition has not been met. - Maintain the sales opportunity
Discovery booking updates the lead, creates opportunity context and applies its tag. - Daily milestone counters
Registration, course-start and qualifying booking events update distinct measures.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Course contact | Email identity and registration/start tags | Keep course events attached to the customer relationship. |
| Follow-up state | Registration, course-start and booking conditions | Determine the next configured communication path. |
| Sales handoff | Discovery/closing booking and opportunity context | Give the sales team the context created before the call. |
Inside the system / 01
The free course was part of a longer customer journey
AlterCall used a free course as an entry point to its coaching and paid-program sales process. The operational challenge was to retain the context after someone clicked an ad or submitted a form: whether they registered, began the course, joined the associated community or booked a conversation.
Noah set up email and text-message follow-up around those milestones and improved an existing foundation with exception handling and operating documentation. His contribution included connecting engagement activity to customer records and the sales handoff.
Inside the system / 02
Let the engagement event change the next step
A Kajabi registration triggered a search by email and a create-or-update path for the CRM relationship. Registration tags supplied state that the messaging workflows could use. When the participant started a course video, a course-start tag triggered the next automation handoff through Zapier and Make.
GoHighLevel held the messaging sequences. The walkthrough distinguished people who had not started the course after a waiting period from those who had started. Community-related messaging also checked the existing membership context rather than treating every contact as if they were at the same point in the journey.
Inside the system / 03
Carry the context into the sales handoff
The aim of the course-follow-up path was to move an appropriate participant toward a discovery call. On booking, the workflow found the lead by email, updated the lead and created an opportunity. It also applied the corresponding GoHighLevel tag and contributed the booking to the daily reporting record.
A separate closing-call event retrieved the scheduler’s information and checked the Principles lead-source condition before applying its tag and updating the closing-booking counter. These were distinct milestones: registering for a course, starting it and booking a conversation were not interchangeable measures of interest.
Inside the system / 04
Document the connections the team will have to maintain
The course walkthrough linked the diagram, Make scenarios, spreadsheet and connected workflows in general execution order. Separate historical accounts describe Notion documentation, explanations of unusual API requests and consistent organization inside Make. That connected the operating process to the places someone would inspect when a handoff failed.
The work covered message sequences, engagement conditions and sales handoffs. A teammate built the upstream contact-assignment process. Conversion improvement and current operation of every historical sequence were not verified.
Within AlterCall