A plastic surgery coordinator should record enough to establish what happened, who owns the next action and when it is due. That usually means defined administrative stages, a small outcome dictionary and timestamps, not a longer free-text note. Keep clinical assessment and sensitive detail in the practice's approved clinical workflow rather than turning a marketing tracker into a second medical record.
Start with a small set of fields your team can maintain consistently. Define what booked, attended, pending and closed mean before using them to judge a campaign. The dictionary below is a proposed administrative model to adapt with the practice's authorised operations and privacy reviewers, not a clinical protocol.
Separate the current stage from the reason and next task
These are three different pieces of information. The stage describes the current administrative position. The outcome reason describes a verified explanation for a change. The next task describes the responsibility that remains.
For example, a request can be at consultation booked, with a rescheduling task due to the coordinator. A person can have attended a consultation but requested more time before discussing an administrative quote. Neither should be reduced to a broad label such as not converted.
Do not make one status field carry every detail. If you create dozens of hybrid labels, staff may choose the nearest one and reports become difficult to interpret. Keep a concise stage vocabulary, separate reason codes and an explicit owner.
Clinical eligibility is not a coordinator's marketing stage. If the clinician's decision changes the administrative route, reflect only the approved operational consequence needed by the authorised team.
Define the evidence for each stage
An inquiry received stage should mean the request exists in the approved receiving system. A contact attempted stage needs an actual attempt, not a task that was merely created. A two-way conversation needs an exchange, not an outbound voicemail.
A consultation booked stage should refer to the practice's defined appointment record. A consultation attended stage needs an attendance confirmation from the authoritative system. A reminder being sent does not establish attendance.
Decide how cancellations and reschedules are represented. Replacing every reschedule with a brand-new inquiry can inflate campaign totals. Leaving a cancelled appointment marked booked can make the pipeline appear healthier than it is.
If a system cannot provide evidence for a transition, record the gap. Do not fill it with an assumption because the monthly report needs a complete funnel.
Copy this coordinator outcome dictionary
Adapt these entries to the practice's actual workflow. Each definition should include who may make the update and where the evidence comes from.
- Received: a unique request is recorded; owner assignment is still required if not already present.
- Contact attempted: an approved response was attempted; time and channel recorded.
- Two-way contact: an exchange occurred; the requested administrative next step is understood.
- Awaiting practice action: the practice owes a response, time option or clarification; owner and due date required.
- Awaiting person response: the practice has responded and is waiting; contact limits and any agreed pause remain respected.
- Consultation booked: a defined consultation appointment exists in the authoritative calendar.
- Consultation attended: attendance is confirmed, not inferred from booking or a sent reminder.
- Reschedule pending: an appointment change needs completion; the request stays owned.
- Paused by request: the person asked to stop or delay the administrative conversation; permitted next contact, if any, is documented.
- Closed administratively: no open task remains, with a verified reason or an explicit unknown.
Use a separate reason vocabulary: requested more time, location mismatch, unavailable appointment, chose not to proceed, duplicate/test, contact details invalid or reason unknown. Do not use financially unqualified, unsuitable or not serious unless there is a legitimate, reviewed need and reliable evidence; those labels easily turn guesses into facts.
Keep opt-out and contact-preference handling distinct from campaign performance labels. The system should support respecting the person's instruction even when a marketing report would prefer another contact attempt.
Name the timestamps that matter
Record request receipt, assignment, first response attempt, first two-way contact, booking creation, appointment date and the relevant outcome update. Use a consistent timezone or clearly stored offsets so an out-of-hours request is not mistaken for an unexplained delay.
Do not replace an original timestamp every time a record is edited. A history of changes is more useful than a single field that always shows the most recent action. Ask the software administrator what audit history is actually available.
Separate the request date from the appointment date. A request made late in the month may lead to attendance the next month. Without that distinction, a campaign can appear to have failed simply because the reporting window closed before the consultation happened.
Only collect fields that have an approved operational purpose. Adding timestamps should not require copying a patient's full conversation into a generic analytics tool.
Use outcomes to explain work, not pressure patients
The coordinator needs to know whether the practice owes a next step. That is different from constructing an endless follow-up sequence for anyone who has not accepted treatment.
If someone asks for time, record the instruction and adjust tasks accordingly. If they ask not to be contacted, respect the applicable process. A paused status should not trigger messages saying the person has forgotten to book.
Administrative quote status can be useful where authorised, but it should not be treated as proof of treatment acceptance or used to infer an individual's financial circumstances. Sensitive quote details and clinical records require the practice's approved handling.
Ask the responsible reviewers to define access. Reception, a coordinator and an external agency may need different information. A shared dashboard should not automatically expose everything to everyone because it makes reporting convenient.
For the underlying US security framework where HIPAA applies, consult HHS's Security Rule summary. The practice must assess its actual systems and obligations; this dictionary is not a compliance determination.
Walk through three synthetic records
Use these fictional examples to desk-check the definitions before changing a live system.
Request A: received Friday evening, assigned to the weekend response role, two-way contact Saturday, consultation booked for the following week. The inquiry cohort is Friday's, while attendance remains pending until the scheduled appointment.
Request B: two-way conversation completed, the person asks for a later appointment, no suitable time offered yet. This is awaiting practice action, not a lost lead. The owner needs to resolve availability or explain the next option.
Request C: consultation attended, person requests a pause before any further administrative discussion. Record attendance and the pause separately. Do not erase the attendance or schedule automatic pressure messages simply because there is no later acceptance outcome.
Now ask a coordinator and backup responder to describe the next action for each fictional record. If they disagree, adjust the definition before automating it. This proposed test is not a claim that a real practice or product has completed it.
Before rollout, rehearse a reassignment as well. The old owner should no longer have an active response task, while the new owner can see the approved context and due date. Check that a paused contact remains paused through that change; transferring responsibility should not silently restart messages.
Report cohorts without moving the goalposts
Count unique requests from a defined period and observe them on a stated date. Show bookings, attendances and pending outcomes separately. Do not compare one fully matured cohort with another whose appointments have not happened.
Use aggregate counts for agency-facing reporting unless a specific approved purpose requires something else. Explain the denominator beside each percentage. Booked out of unique requests and attended out of bookings are different measures.
Link the dictionary to why plastic surgery leads do not book for diagnosis, and consultation no-show reduction for the appointment stage. Do not create new definitions for each report.
Fyntrix's inquiry and follow-up work can help clarify system responsibility. Record the next responsibility as carefully as the last result.