Tokens
Placeholders that fill themselves in per contact — so one template greets every person by name, quotes their own numbers, and links to their own pages.
On this page
1What a token is
A token is a placeholder you drop into a message. When ClientTether sends that message to a specific person, it swaps the placeholder for that person’s real value.
Write this once:
Hi {{client.firstName}}, thanks for reaching out about {{client.opportunity_name}}.
And every recipient gets their own version, without you writing a single message by hand. Tokens use double curly braces and a group prefix — client for the contact, account for your business, and so on.
2Inserting a token
Anywhere tokens are supported you’ll find a token picker — a searchable dropdown grouped by category. Pick the field you want and it inserts the correct code at your cursor. Typing the token by hand works too, but the picker is the safe route: a mistyped token won’t resolve and will go out to the customer as literal text.
Always send yourself a test first
Tokens only resolve against a real contact record. A token pointing at a field the contact hasn’t filled in comes out empty — which is how emails end up opening with “Hi ,”. Test with a contact that has realistic data before launching to a list.
3What’s available
There are around 140 built-in tokens, organised into groups in the picker:
| Group | What it covers |
|---|---|
| Contact | Everything about the person — the largest group by far |
| Account | Your own business details, for signatures and footers |
| Logged in User | The user sending the message, so a template can sign itself |
| Appointments | Appointment details for confirmations and reminders |
| Bot Appointments | Appointments booked through the scheduling bot |
| Current Date-Time | Today’s date and time, formatted for the message |
| Holiday and OoO | Holiday and out-of-office values |
| Proposals / Active Quote | Proposal and quote details, including the live quote on the contact |
| Work Orders | Work order details |
| CT-Sign | Signature request values |
| Hosted Pages | Links to your hosted pages, built from each page’s slug |
| External Integration Ids | Identifiers from connected systems |
| Custom Fields | Your own fields — see the next section |
The Contact group in practice
This is where most templates live. Alongside the obvious ones — {{client.firstName}}, {{client.lastName}}, {{client.email}}, {{client.phoneCell}}, {{client.compName}} — there are fields many people never realise they can personalise with:
{{client.link}}— a direct link to the contact record, handy in internal alerts{{client.assignedUser}}— the rep who owns the contact, so a message can name a real person{{client.actionPlan}}— the plan they’re currently on{{client.lead_source}},{{client.sales_cycle_name}}— where they came from and where they are in your process{{client.deal_size}},{{client.deal_closed}}— deal values{{client.anniversary_1}},{{client.anniversary_2}}— dates worth reaching out on- Household and demographic fields such as
{{client.home_owner_status}},{{client.household_income}},{{client.presence_of_pets}}— useful for service businesses that segment on them
4Your own fields as tokens
Custom fields become tokens automatically. If you create a field called Preferred Contact Time, it appears in the picker and resolves as {{tokens.Preferred_Contact_Time}} — the field label with spaces replaced by underscores.
The picker separates them by scope, so you can tell which level a field belongs to:
- Account custom fields — defined for your account
- User custom fields — defined at the user level
- Common custom fields — shared across the structure
Hosted pages work the same way: each page becomes {{hostedpage.your-page-slug}}, so a template can link to the right landing page without hardcoded URLs.
Renaming a custom field breaks its token
Because the token is built from the field’s label, renaming the field changes the token. Any template still using the old name will stop resolving and send blank. If you rename a field, search your templates for the old token and update them.
5Tokens in webhooks
Tokens aren’t only for messages. In a Webhook step inside an Action Plan, the payload’s Value fields accept tokens too — so you can send an external system the contact’s real email, deal size or assigned user rather than a fixed value.
Mix and match freely: some keys can carry constants your endpoint always expects, others carry tokens that change per contact.
6Troubleshooting
The token printed as literal text in the email
The token name doesn’t match anything. Usually a typo, a missing group prefix, or single braces instead of double. Re-insert it from the picker rather than fixing it by hand.
The token resolved to nothing
The token is valid but that contact has no value in the field. Check the contact record — and consider whether the sentence still reads properly when the field is empty.
A custom field token stopped working
Someone probably renamed the field. The token follows the label, so the old one no longer matches anything.
7Related pages
- Templates — where tokens are most often used.
- Action Plans — automated sequences that send those templates.