Practice task
Design a Dental Clinic Field SetMagdisenyo ng Field Set para sa Dental Clinic
GoalLayunin
Design and create six custom fields a two-branch dental clinic needs, using the right field type for each.Idisenyo at gawin ang anim na custom field na kailangan ng dental clinic na may dalawang branch, gamit ang tamang field type para sa bawat isa.
What you needAno ang kailangan mo
- The lesson:Ang lesson: Custom Fields: Structuring Client DataCustom Fields: Pag-aayos ng Data ng Client (Module 2)
- Access to a GoHighLevel sub-account you're allowed to build inAccess sa GoHighLevel sub-account na pinapayagan kang mag-build
- About 20 minutesMga 20 minuto
Requirements
Tick them off as you go. Your ticks are saved in this browser.I-tsek habang ginagawa mo. Naka-save ang mga tsek mo sa browser na 'to.
Reveal the walkthroughIpakita ang walkthrough
Awaiting hands-on verification. The concepts here are sound, but the click-by-click steps have not yet been re-walked in a live GoHighLevel sub-account. GoHighLevel changes often, so a menu name or screen may differ from what you see. Flagged rather than presented as verified.
A suggested field set
| Field name | Type | Options / notes |
|---|---|---|
| Preferred branch | Dropdown (single) or Radio | Cebu, Mandaue |
| Patient type | Radio | New, Returning |
| Treatments of interest | Checkbox or Dropdown (multiple) | Cleaning, Whitening, Braces, Extraction |
| Last visit date | Date picker | — |
| Has dental insurance | Radio | Yes, No |
| Insurance provider | Single line | Only relevant if “Yes” above |
Why these choices
- Treatments is multiple-choice because a patient can want both cleaning and whitening. A single dropdown would force them to pick one.
- Last visit date is a date so you can later build “not seen in 6 months” smart lists and reminders. As text, you can’t compare it.
- Insurance is split in two: a yes/no you can filter on, and the provider as free text, because there are too many providers to list.
- Notice what’s not here: date of birth and address are standard fields already.
If you used tags for any of these (branch-cebu, new-patient), that can work for
yes/no facts — but a field keeps each fact in one place, which matters when the
list of options grows.
Suggested na field set
| Field name | Type | Options / notes |
|---|---|---|
| Preferred branch | Dropdown (single) o Radio | Cebu, Mandaue |
| Patient type | Radio | New, Returning |
| Treatments of interest | Checkbox o Dropdown (multiple) | Cleaning, Whitening, Braces, Extraction |
| Last visit date | Date picker | — |
| Has dental insurance | Radio | Yes, No |
| Insurance provider | Single line | Relevant lang kung “Yes” sa itaas |
Bakit ganito ang mga pinili
- Multiple-choice ang Treatments dahil pwedeng gusto ng patient ang cleaning at whitening nang sabay. Kapag single dropdown, mapipilitan silang pumili ng isa.
- Date ang Last visit date para makagawa ka mamaya ng smart lists at reminders na “hindi nakita sa loob ng 6 na buwan”. Kapag text, hindi mo ito maikukumpara.
- Hinati sa dalawa ang Insurance: yes/no na pwede mong i-filter, at ang provider bilang free text, dahil masyadong marami ang providers para ilista.
- Pansinin kung ano ang wala dito: standard fields na ang date of birth at address.
Kung tags ang ginamit mo sa alinman dito (branch-cebu, new-patient), pwedeng
gumana ‘yan para sa yes/no facts — pero pinapanatili ng field ang bawat fact sa
iisang lugar, na mahalaga kapag dumarami ang options.
Success criteria
How you know it worked.Paano mo malalaman na gumana.
Related lessonKaugnay na lesson
Module 2: CRM FundamentalsModule 2: Basic ng CRM Completed: Custom Fields: Structuring Client DataCustom Fields: Pag-aayos ng Data ng ClientReady for a harder one?Handa ka na sa mas mahirap?
A task gives you the spec. A client scenario makes you write it — that's the real job.Binibigay sa'yo ng task ang spec. Sa client scenario, ikaw ang susulat nito — 'yan ang totoong trabaho.