Custom values: the twenty minutes that make one snapshot fit any account

One crate. Twenty businesses. The same nine components, the same workflows, the same message copy, and every one of those accounts sends messages that name the right company, quote the right phone number and link to the right calendar.

That is not clever engineering. It is one feature, used properly, and it is the difference between a snapshot being a product and a snapshot being a starting point somebody has to rebuild.

It is also the single most common reason a customer receives a text with a hole in the middle of it.

A custom value is not a custom field

These get confused constantly and the confusion is where the damage starts.

A custom field belongs to a contact. First name, last service date, policy renewal, vehicle registration. It is different for every person in the account, and it is the thing that makes a message feel written rather than blasted.

A custom value belongs to the account. Business name, the number people should call, the booking link, opening hours. It is identical for every contact and it changes only when the business changes.

Confuse them and you get one of two failures. Either somebody stores the business phone number as a contact field and then has to set it on eleven thousand records, or somebody writes the business name directly into forty templates and then the business rebrands.

Values live in Settings, then Custom Values. Fields live with the contact.

What a well-built crate ships with

A crate should arrive with the value set already referenced everywhere it is needed and simply waiting to be filled. There are usually eight that carry almost all the weight.

The business name, exactly as customers say it. The number to call, which is often not the number the account sends from. The booking link. The service area or location line. The opening hours sentence, written as a sentence rather than a table, because it goes inside a text message. The current offer or reason to act. The review link, which is a specific Google or Facebook URL and not a homepage. And the sender’s name and sign-off, because “the team” reads like software.

Everything after those eight is refinement. Those eight appear in nearly every outbound message a crate sends, which is exactly why they are the ones to fill first.

Referenced once, typed nowhere

The rule is that a value is written into the account once and referenced everywhere else as a token.

The temptation is the opposite. It is quicker, on any single template, to type the business name than to insert {{custom_values.business_name}}. Do that across a crate and you have created forty places that need editing the day the business changes its trading name, its number, or its offer, and you will find thirty-eight of them.

A message referencing a value is also safe to carry across a push. When the machinery is replaced with a newer version, the identity is not sitting inside the machinery, so nothing personal to that business is lost. That boundary is what makes pushing snapshot updates a routine operation rather than a rescue mission.

An empty value is the other side of the same mechanism. A perfectly correct workflow will send “Thanks for calling” followed by nothing, or in some templates will fail to send at all, and neither outcome raises an error anywhere you would look. It is one of the first things to check when a crate appears to be misbehaving, which is why it sits near the top of the diagnostic order for a snapshot that will not fire.

A naming convention that survives an agency

One account, any naming works. Six accounts and two people, naming is the whole game.

Prefix by domain, lower case, no spaces, no punctuation beyond an underscore. Something like biz_name, biz_phone, biz_hours, book_link, book_policy, review_link_google, offer_current, sender_name. The prefix does the sorting for you, so the list stays readable at forty values instead of turning into an alphabetical jumble where business name and main number sit nowhere near each other.

Two rules that matter more than the exact scheme. Never rename a value once it is in use, because renaming breaks every reference to it silently. And never create a second value that means the same as an existing one, because within a month nobody will know which of the two the templates actually use.

The twenty minute fill order

Filling values is often treated as an hour of dull data entry and then done badly at the end of a long afternoon. There is a faster order that also catches mistakes.

Fill the eight that appear in every message first. Nothing else, and do not stop to admire the rest of the list.

Then send one test contact through the longest sequence in the crate. Not the shortest. The longest sequence touches the most templates, so it exercises the most values in a single pass, and you are reading the messages as they arrive on a real phone rather than in a preview. Every gap shows up immediately and in context.

Then fill the rest of the list, which by that point you have a much better sense of, because you have seen where the copy actually lands.

Twenty minutes, and the crate is sending as the business rather than as a template. It is the same twenty minutes on the second account and the twentieth. The pre-import checklist puts this immediately after the import for that reason, and the installation and fit-out service does this pass as part of the job when you would rather not.

Finding every place a value renders

Before you change a value that is already live, find out what it touches.

Search the account’s templates and workflows for the token itself rather than for the words it produces. Searching for the business name finds the places somebody typed it by hand, which is useful in its own right and worth doing once as an audit. Searching for {{custom_values.book_link}} finds every place the crate genuinely references it, including the ones inside branches you forgot existed.

Do this before a rebrand, before a number change, and before you retire a value. A value that still has references is not safe to delete just because you stopped using it consciously.

The same crate in six sub-accounts

This is where custom values stop being tidy housekeeping and start being commercial.

Six branches of the same trade, or six clients in it, take one crate and one value sheet each. One spreadsheet, eight columns for the values that matter, one row per account. The fit-out becomes a fill-in rather than a rebuild, and the crate stays a single thing you maintain in one place.

A cleaning company crate rolled across six franchise territories differs only in name, number, area and booking link. A gym and fitness studio crate across three sites differs in hours and offer. In both cases the machinery is identical and the value sheet is the entire delta.

That arithmetic is what makes an aisle pack practical rather than merely cheaper per crate. Buying several crates off one aisle only pays if fitting the second one takes twenty minutes instead of an afternoon, and the packs on the pricing page assume exactly that. Where the roster spans several trades rather than several sites, the multi-niche agency rollout service sets the naming standard once so it holds across all of them, and the home and trade aisle is where most multi-site rosters start.

What to decide next

Decide who owns the value sheet. On a single business it is whoever answers the phone, because they are the one who knows the number changed. On an agency roster it needs a named owner, or the sheet drifts out of date and the accounts quietly start telling customers the wrong thing.

Then decide whether your values are the account’s identity or a dumping ground. If a value holds something that differs per contact, it is in the wrong place, and moving it to a contact field before the account grows is a ten minute job that becomes a migration later. The full catalog ships every crate with the boundary already drawn the right way.