Graphy student history: what to check before a follow-up
Before following up with a Graphy learner, check who they are, which course they joined, their latest question and what your team last promised. A useful student history helps staff choose the next action without treating every conversation as a new sales enquiry.
Build a short context card before writing a message
Start with a learner identifier, verified contact details, the relevant course, the latest interaction, its owner and the next agreed step. Keep each item connected to its source and last checked date. This is a planning checklist for your academy, rather than a promise that every field is already synced into every CRM. A person should be able to explain the reason for a follow-up before choosing a channel or sending it.
Separate course access from payment assumptions
A learner with course access is not necessarily a new paid customer. Graphy's learner reporting documentation distinguishes course assignment information, enrolment timing and learning progress. Review the relevant course record before deciding what to say. For your operating process, keep free participation, a paid purchase and a manual assignment separate unless a verified transaction establishes otherwise. An old payment failure should not trigger a reminder when a later payment has resolved the situation.
Match the person without merging on a name alone
Similar names do not establish identity. Check an available account identifier and corroborating contact details. A family may share a mobile number; an academy inbox may serve several people. Put uncertain matches into staff review instead of combining their history automatically. If someone provides a different number during a booking, verify that number for the booking purpose without silently replacing a different learner's contact record.
Keep conversations as dated events
Record what the learner asked, the response given and any commitment your team made. Add the date, time and staff owner. A note such as 'send course outline on Friday' is more useful than 'interested'. Append a correction or a new outcome instead of replacing the earlier conversation. For example, a learner might request course details on Monday, clarify a prerequisite on Wednesday and ask for a demonstration the following week. Those are distinct events around one relationship.
Give the next action its own date and owner
The next follow-up date belongs beside the conversation history, not inside an undated block of notes. Set a person responsible for the action and describe its purpose. Completing today's call should preserve its outcome even when you schedule the next call. Separate the date an enquiry arrived, the time of a booked meeting and the due date of a staff follow-up: each answers a different operational question.
Confirm what the integration actually supplies
Graphy's public API guide explains how to access integration credentials and points to its endpoint documentation. Check API availability for your account and confirm the exact fields, permissions and update behaviour needed for the workflow. A field visible in an LMS report is not proof that your CRM receives it. Demonstrate a sample learner record, a changed record and a missing value before agreeing which system is authoritative for each field. Keep credentials out of notes and screenshots.
Keep permission and delivery separate from learner interest
An enrolment, an enquiry and permission to contact someone are different facts. Use your verified permission process for each channel, respect stops and unsubscribe requests, and check whether another team member has already replied. Also separate queued, provider-accepted, delivered and read states. A follow-up should not assume that a previous message was received just because a system accepted a send request.
Use a small review checklist in your CRM demo
Bring an anonymised example containing a course record, two dated conversations, an unresolved question and a next action. Ask how the proposed setup represents missing data, multiple contacts and a later correction. Check which updates are automatic and which require a staff decision. CloudFolks CRM is built for Graphy instructors; use a personalised walkthrough to confirm the learner-history and follow-up workflow your academy needs before expanding it across your courses.