Guides
Build a CRM- or scheduler-triggered Thoughtly workflow that reconnects enrollment no-shows, offers verified advisor availability, and measures completed conversations through student starts.
Last updated
A missed enrollment-advisor meeting is not the same thing as a cold lead. The prospective student already raised a hand, chose a time, and then failed to attend. Treating that record like a brand-new inquiry ignores useful context; dropping it into an undifferentiated nurture sequence wastes the strongest signal you have.
An enrollment no-show recoveryNo-show recoveryThe process of re-engaging leads or patients who missed a scheduled appointment, using automated voice, SMS, or email outreach to reschedule and recover revenue that would otherwise be lost. workflowWorkflowAn automated, multi-step process — usually triggered by an event (form fill, new lead) and orchestrating one or more voice / SMS / email actions. should do one job: reconnect a known inbound inquiry, learn whether the student still wants help, and either rebook a real advisor slot or close the loop cleanly. The useful conversion unit is not calls placed. It is completed advisor conversations, followed downstream by applications, deposits, starts, and yield in the institution's system of recordSystem of recordThe authoritative system where customer, lead, policy, loan, appointment, or account data is stored and updated..
Thoughtly's point of view is simple: the CRMCRMThe system of record for leads, contacts, deals, and activity. Thoughtly reads from and writes to your CRM continuously. or scheduler should decide who is eligible for recovery, the agent should use only the context needed for that conversation, and a calendar integration should offer only real availability. Human enrollment staff stay focused on questions and decisions that deserve a person.
The existing enrollment follow-up implementation guide covers the path from a new inquiry to qualification and a first counselor booking. This workflow starts later: an advisor meeting was already scheduled, the meeting did not happen, and the next best action is now uncertain.
That different start state changes the build. You need an authoritative no-show event, a duplicate-booking check, the original appointment context, a recovery-specific opening, a rescheduling path, and an explicit terminal state for students who are no longer interested. Replaying the original speed-to-lead sequence would be clumsy at best.
Write the eligibilityEligibilityThe fit criteria that determine whether a prospect can move forward, such as service area, insurance coverage, loan type, location, age, or program requirements. rule in plain language before opening Thoughtly. A useful rule might be: enter the workflow when an inbound education inquiry has a completed no-show status, has no later advisor meeting already booked, has a usable phone number and timezone, and remains eligible for the institution's approved follow-up.
Keep exclusions equally explicit. Suppress records with an opt-outOpt-outA recipient’s request to stop receiving calls or messages. Compliant systems must capture opt-outs and suppress future outreach where required., wrong-party flag, duplicate active workflow, completed enrollment, unresolved complaint, or any institutional hold that should stop communication. The automation should enforce these rules before a recovery call is attempted.
| Workflow state | Required context | Thoughtly action | Success condition | Fallback |
|---|---|---|---|---|
| Eligible no-show | Contact ID, missed meeting time, program, timezone | Call Contact | Student reconnects | Record no answer and follow approved retry policy |
| Still interested | Program and intended start term | Check real calendar availability | A valid slot is selected | Offer a human follow-up task |
| Rebooked | New slot and advisor or event type | Send confirmation and update CRM | New appointment is written to both systems | Flag write-back failure for review |
| Interested, not ready | Preferred date or requested channel | Store the next allowed action | Approved callback or nurture state is recorded | End without inventing a date |
| Needs an advisor now | Reason for escalation and prior context | Transfer or create a priority task | Human accepts the handoff | Book the next available conversation |
| No longer interested or opted out | Disposition and channel preference | Stop the recovery path | Suppression state is written back | No further automated contact |
In Thoughtly Automations, begin with one of two patterns:
The current automation triggerTriggerThe event or condition that starts an automated workflow, such as a new lead, missed call, CRM status change, calendar booking, or completed call. documentation supports Incoming WebhookWebhookAn event-based integration that sends data from one system to another when something happens, such as a form submission, booked appointment, or completed call. and Recurring Schedule triggers, and recommends testing in Draft mode with sample output before switching to Live. Whichever pattern you choose, plan for idempotency: the same no-show event must not start two recovery calls.
Use Create or Update Contact when the source payload may represent a new Thoughtly contact, or Get Contact by Phone Number when the contact should already exist. Then use Call Contact rather than Call Phone Number. Call Contact links the conversation to a contact ID, preserves history, and lets later steps write Attributes and dispositions against the same record.
Separate persistent facts from one-call context. Thoughtly's Attributes versus Metadata guide is the useful boundary: store durable fields such as program interest, intended start term, campus preference, or last appointment outcome as Attributes; pass the missed meeting time, recovery reason, and campaign or workflow ID as Metadata for this call.
Do not pass a full student record simply because the source system can provide it. The agent needs enough context to avoid asking the student to repeat known information, not a copy of every field in the CRM or student information systemSISA student information system — the system of record for education programs. Slate and Ellucian are common; Thoughtly integrates with both..
Create a focused agent flow rather than sending no-shows back through the original inquiry script. A practical structure is:
Capture a small set of variables from the conversation: `still_interested` as a boolean, `preferred_date`, `preferred_timezone`, `needs_advisor` as a boolean, and `recovery_disposition` as a controlled value such as rebooked, callback_requested, not_ready, not_interested, or opt_out. Leave a value empty when the student did not provide it.
Thoughtly Variables extract after the caller's reply and can feed rule-based Outcomes. Use rule-based branches for operational decisions such as `still_interested == false` or `booking_status == confirmed`; reserve prompt-based interpretation for genuinely open-ended intent.
Follow the production pattern in Thoughtly's voice agentVoice agentAn autonomous, conversational interface that interacts with humans over the phone — answering, qualifying, and routing calls without human staffing. scheduling guide: collect a preferred date and timezone, run the connected scheduler's availability action, present a short list of returned slots, capture the student's choice, and then run the booking action.
Never let the agent invent a slot. If the availability response is empty, ask for another day or move to a human fallbackFallbackA safe backup path used when the caller says something unexpected, an integration fails, or the agent cannot confidently complete the intended step.. If the scheduler exposes a native reschedule action, use it against the existing appointment. If it does not, create a new booking only after the original record is definitively in a no-show or closed state, then save the external reference so both systems agree.
Scheduling actions accept a timezone input. Map the student's confirmed timezone when available; otherwise use the institution's documented fallback. Read the final date, time, and timezone back to the student before ending the call.
The happy pathHappy pathThe ideal conversation flow where every input matches expectations and the agent reaches the intended outcome with no detours. is only one branch. Add explicit Outcomes and a default branch for each of these states:
The automation actions reference documents Conditions, Delay Until, Call Contact, Send SMS, CRM actions, and scheduling actions. Use an Else or Default route wherever a field or API result could be missing.
After a successful booking, send a short SMS or email confirmation from the connected channel. Include the confirmed date, time, timezone, advisor or event name, and the institution's official change or cancellation path. A confirmation should reflect the scheduler result, not a free-form summary produced before the booking completes.
Use the CRM integrationCRM integrationA two-way connection between a voice/SMS/email agent platform and a CRM that syncs contact data, call outcomes, dispositions, and follow-up tasks in real time. action or Send Webhook to write back a compact recovery record: original no-show ID, recovery disposition, new appointment ID and time when booked, contact timestamp, next allowed action, and the Thoughtly conversation or call ID. Add a stable event ID so retried writes update the same record instead of creating duplicates.
For the broader write-back pattern, see How to Set Up Post-Call Webhooks for CRM Automation. The On Call Completed trigger can also route dispositions, summaries, captured variables, and notifications after the recovery conversation ends.
Run the automation in Draft with internal numbers and representative sample payloads. Refresh the trigger Output after each sample so the field picker reflects the real schema. Be careful with call steps: refreshing their Output can place a real call to the mapped number.
At minimum, test:
Switch to Live only after the workflow produces one clear disposition for every test and the source system, calendar, and CRM agree on the final state.
A no-show recovery dashboard should begin with the eligible cohort and end with the enrollment outcome. Track eligible no-shows, recovery attempts, contacts reached, students still interested, meetings rebooked, advisor meetings completed, applications resumed or completed, deposits, starts, and yield. Join Thoughtly conversation outcomes to the CRM or student information system using stable contact, appointment, and workflow identifiers.
Use failure metrics to improve the build: duplicate-trigger rate, missing-context rate, booking-action failure rate, CRM write-backCRM write-backUpdating the CRM after an interaction with call outcomes, transcripts, qualification answers, notes, appointments, dispositions, and next-step fields. failure rate, and opt-out handling accuracy. A high rebooking count with weak meeting completion is a reminder problem; strong meeting completion with no downstream application movement is an enrollment-process problem. The call count alone cannot tell you either.
Yes, when the source system can send a no-show event to an Incoming Webhook, or when a Recurring Schedule queries an approved no-show cohort. The source record should remain authoritative, and the workflow should check for an existing future booking before calling.
You can reuse shared knowledge and scheduling connections, but the no-show path needs its own opening, metadata, dispositions, and stop conditions. A student who already booked should not be asked to repeat the entire new-inquiry flow.
Use the provider's availability and booking actions to create a new appointment only after the old appointment is confirmed as a no-show or closed. Save the new external appointment ID and make the CRM write-back explicit. If the state is uncertain, send the record to an advisor rather than risking two active bookings.
Capture the requested date, time, timezone, and callback permission. Use Delay Until or create an approved CRM task for that moment. If the request is vague, ask for clarification or let a human follow up; do not infer a time.
No. This workflow is for a known inbound inquiry who booked and missed an enrollment conversation. Eligibility, timing, channel, and suppression rules still come from the institution's current policy and systems of record.
No. It restores coverage for a narrow lifecycle step, handles routine rescheduling, and brings interested students back to the team with context. Advisors keep the conversations that require judgment, reassurance, or program-specific guidance.
Thoughtly Automation actions and steps
Thoughtly voice agent scheduling guide
Thoughtly for higher education enrollment
