Skip to content

Care Plan Mappings

Care plan mappings connect your care plans to your service types. They tell REV23 Cloud which care plan to use when a customer receives a service, which determines the aftercare instructions, healing stages, and messages they’ll receive.

Location: Settings > Care > Care Plan Mappings

The mappings page shows a tree view of service category types, expandable to individual service types. Assign a care plan at any level.

Mappings are resolved using a cascade — the most specific match wins:

PriorityMapping LevelExample
1 (highest)Artist + Service TypeArtist “Jess” doing a “Lobe” piercing
2Artist + Category TypeArtist “Jess” doing any piercing
3Service TypeAny artist doing a “Lobe” piercing
4 (lowest)Category TypeAny artist doing any piercing

Assign a care plan to a category type and every service type in that category inherits it. This is the most common setup — one plan per category covers the majority of studios.

CategoryCare Plan
TattooTattoo Aftercare
PiercingPiercing Aftercare
Permanent MakeupPMU Aftercare

Override the category default for specific service types that need different care instructions. For example, a surface piercing has a much longer healing time than a lobe piercing and warrants its own plan.

Category / TypeCare Plan
PiercingPiercing Aftercare
Piercing > Lobe(inherits)
Piercing > SurfaceSurface Piercing Aftercare
Piercing > DermalDermal Aftercare

Some service types fall under a category that has a care plan mapped, but don’t actually need aftercare. For example, “Jewelry Change” and “Removal” are piercing service types, but sending piercing aftercare instructions for them doesn’t make sense.

For these cases, select — None — from the care plan dropdown on the service type. This explicitly excludes the service type from inheriting its parent category’s care plan. No care journey will be created when this service is performed.

This is different from simply having no mapping. Without a mapping, the service type inherits from the category. With “None” selected, inheritance is blocked — the service type is explicitly opted out.

Category / TypeCare Plan
PiercingPiercing Aftercare
Piercing > Lobe(inherits)
Piercing > Jewelry Change— None —
Piercing > Removal— None —

To return a service type to inheriting from its category, select — Default — (or use the reset option), which removes the override.

The Set All option on a subcategory supports all three states: assign a specific care plan, set to None to exclude all service types in the group, or Default to clear all overrides and return to inheritance.

Use the artist filter dropdown to view or set per-artist overrides. This is useful when a specific artist has their own aftercare routine or preferred instructions.

For example, if one artist uses a specific healing protocol for their tattoos:

Category / TypeDefaultArtist: Mike
TattooTattoo AftercareMike’s Tattoo Aftercare

Artist overrides follow the same cascade. An artist + service type mapping is the most specific and always wins.

If no care plan is mapped for a given service type (at any level in the cascade), no care journey is created for that service. This is expected — not every service type needs automated aftercare.

There are two ways a service type can end up without a care journey:

  • No mapping exists — The service type and its parent category have no care plan assigned. It simply inherits nothing.
  • Explicitly excluded — The service type is set to “None,” which blocks inheritance from the parent category. Use this when the category has a care plan but the specific service type should not.