Dynamic tags are short placeholders you insert into text fields or templates, such as [client_name] or [practice_name]. When a proposal or letter is generated, Socket replaces each tag with the real data from your practice settings or from the specific proposal, so the final document reads correctly for each client.
Benefits of using dynamic tags
Save time, by avoiding manual copy and paste.
Keep documents consistent and error free.
Personalise at scale, so every client sees their own name, dates, fees, or your uploaded signature.
Maintain a single template that adapts automatically for each proposal or letter.
Types of dynamic tag
There are different types of dynamic tags which will populate based on different things:
Practice settings — tags like [practice_name] and [practice_principal] pull values you set in your account settings.
Proposal fields — tags such as [contact_first_name] or [start_date] populate as you complete the proposal. These only render once the relevant fields are filled.
Uploaded assets — tags like [client_owner_signature] will insert your uploaded signature image where placed.
How to use dynamic tags (step by step)
Open the editor where you want to insert a tag, for example a proposal intro, engagement letter template, or terms & conditions.
Place the cursor where the personalised information should appear.
Click the 'Insert tag' menu to display the options available.
Select the tag you want, for example [practice_name] or [client_owner_signature] The tag will appear in the editor.
Save the template or document. When you send or generate it for a specific client, Socket will replace the tags with the correct values.
"Replacement for [tag_name]"
A tag in an engagement letter or service schedule is a placeholder for information you supply. Where a tag has no default value set, you are asked for that information when you build the proposal, under a field labelled Replacement for followed by the tag's name.
Whatever you type there is what appears in the finished document in place of the tag. So a tag called client_information_provided_timeframe is asking for the timeframe you want that letter to state.
Setting default values on service schedule tags
If the same tags are asked for on the Customise step of every proposal, set a default value against them so they populate on their own.
Open the individual service schedule in your settings. A tags banner at the top lists the tags used in that schedule. For each one you can either:
Set a default value. The tag fills in with that value every time the schedule is used, and it isn't shown on the Customise step.
Set it to no default value. You are prompted to fill it in on the Customise step each time the schedule is used.
Most practices use a mix. A document turnaround time is the same for every client, so it gets a default. The period an agreement starts from changes with each proposal, so it is left without one.
Quick before / after examples
Template text:
Hi [contact_first_name],
Following the changes, the regular monthly fee in our invoices will change starting from [start_date] onwards.
Will display as:
Hi Richard,
Following the changes, the regular monthly fee in our invoices will change starting from May 2025 onwards.
Best practices
Double check and preview before sending, especially for new templates.
Use practice-level tags for firm details you don’t want to update in every template.
Set defaults on your service schedule tags for anything that is the same on every proposal.
Keep tag placement simple, a tag inside a sentence is fine, avoid splitting tags across lines.
Don’t overload templates with too many tags, use only the ones that add real value.
Preview your client proposal to ensure proposal-level tags populate as expected.
Troubleshooting
If a tag appears unchanged in the preview, check that the corresponding field is filled for the proposal, or that the practice setting is populated.
If you are asked for the same tags on every proposal, set a default value against them in the service schedule, as described above.
If an image tag like [client_owner_signature] doesn’t render, confirm the 'Client Owner' has a signature uploaded in Settings.
Still seeing problems? Take a screenshot of the template and the preview, then contact support.