Care Plan Mappings

Care plan mappings connect your care plans to your service types. They tell REV23 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 → Forms & Care → Care Plan Mappings

Template Mappings, under the same settings group, works the same way for a different question: which release form a service uses. Care mappings can override per artist; template mappings override per studio.

How mappings work

The mappings page lists 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:

Priority	Mapping Level	Example
1 (highest)	Artist + Service Type	Artist “Jess” doing a “Lobe” piercing
2	Artist + Category Type	Artist “Jess” doing any piercing
3	Service Type	Any artist doing a “Lobe” piercing
4 (lowest)	Category Type	Any artist doing any piercing

Tip

Start simple. Set a care plan at the category level (e.g. all piercings use your Piercing Aftercare plan), then add overrides only where needed.

Category-level defaults

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.

Category	Care Plan
Tattoo	Tattoo Aftercare
Piercing	Piercing Aftercare
Permanent Makeup	PMU Aftercare

Service type overrides

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 / Type	Care Plan
Piercing	Piercing Aftercare
Piercing > Lobe	(inherits)
Piercing > Surface	Surface Piercing Aftercare
Piercing > Dermal	Dermal Aftercare

Excluding a service type

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 differs from leaving the service type unmapped. An unmapped service type inherits from its category; — None — blocks that inheritance.

Category / Type	Care Plan
Piercing	Piercing 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.

Bulk exclusion with Set All

The Set All option on a subcategory — a named group of service types inside a category, like Ear or Facial — 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.

Artist overrides

Filter the page to an artist 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 / Type	Default	Artist: Mike
Tattoo	Tattoo Aftercare	Mike’s Tattoo Aftercare

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

When no care plan is mapped

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 — Neither the service type nor its parent category has a care plan assigned.
• 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.