Client labels

Labels are your own words for your clients: VIP, Instagram lead, Marathon prep, Needs a call, whatever distinction you actually make in your head. Once a client carries a label you can filter your roster by it, on its own or combined with others.

Labels are separate from lifecycle stages. A client sits in exactly one stage (that’s your pipeline), but can carry as many labels as you like. Both are chips in the client record’s header, side by side.

Who else can see them

Labels belong to your business, not to you personally. Everybody on your team works from the same vocabulary: a label you create is immediately offered to your colleagues, and one they create is offered to you. There are no private labels.

Your clients never see them. Labels do not appear anywhere in the client app, on a plan, or in anything you send out. You can be as blunt as you like.

Anything connected to your Protocol API can read and write them too, which is the subject of Labels from connected systems below.

Tagging a client

Open a client and click the Labels chip in the header, next to their stage.

You don’t have to set labels up first. Type a new word and pick Create “…” and the label is created and applied in one go. Matching ignores capitals and any spaces you leave at either end, so typing vip when you already have VIP reuses the one you have instead of making a second.

Filtering your roster

The Segments column down the left of the client list has a Labels group. Pick one or more and the list narrows as you pick. Choose two or more and a switch appears under the group:

• Any label gives you clients carrying at least one of them. Good for “everyone I’ve flagged somehow”.
• All labels gives you only the clients carrying every one. This is the one for real segments: VIP and Marathon prep.

On a narrow screen the column collapses into a Filters button that opens the same groups as a sheet. Either way the choice lives in the page address, so you can bookmark a segment or paste it to a teammate.

The list also has a Labels column, showing up to two chips per client and a count for the rest, so you can see who carries what at a glance.

Managing your labels

Clients → Configuration is the full vocabulary, in the Labels card. That screen also holds your pipeline stages and your progress entry statuses; see Configuration for how the three fit together.

The Labels card lists every label you have, retired ones included. Every row shows how many clients carry that label, and a Retired marker on the ones you have taken out of circulation. Edit opens the editor, where you can:

• rename a label,
• change its colour,
• add a new one without going near a client,
• retire one, with the switch that reads Offered or Retired,
• merge one into another, keeping every tag,
• and delete one outright.

Each change saves as you make it. There is no Save button here on purpose: your integrations write to this same list, and saving the whole list back would wipe anything they created while you had the editor open.

Retiring a label, and when to delete instead

Retiring a label takes it out of circulation without touching anybody. In the editor it is the switch that reads Offered or Retired; on the Configuration card the row reads Retired too.

What retiring does: it hides the label from the pickers so nobody applies it again. The clients already carrying it keep it, it still shows on their record, and it still works as a filter. Use it for a campaign that ended, where the history is worth reading later.

Delete is the other option, and it is a different claim. It removes the label from every client carrying it, and the confirmation tells you how many that is. Delete a label that was a mistake; retire one that was real and is finished.

If the tags themselves are worth keeping, do neither and merge instead.

Merging near duplicates

Because a connected system can invent a label just by using its name, you end up with VIP, vip clients and V.I.P. meaning one thing. Merge folds them together: pick the row you want rid of, choose which label it goes into, and every client tagged with the old one comes out tagged with the one you kept. Nothing loses a tag, which is the whole difference between this and deleting.

Labels from connected systems

Anything connected to your Protocol API can tag clients too: a signup funnel marking new leads, a gym system marking members, an automation you’ve wired up yourself. Those labels are the same labels you see in the app, so a tag applied by your funnel is immediately filterable in your roster.

Because a connected system can invent labels, near duplicates build up: VIP, vip clients, V.I.P.. The Configuration tab is where you keep that tidy, by merging the ones that mean the same thing, renaming the keepers, and retiring the rest.

For the API and event details, see Webhooks. The client.labels.changed event fires whenever a client’s labels actually change.