How merge fields choose whose details to use

Every merge field is a slot with a name. At generation time, CaseConnect fills each slot from the matter. There are three kinds of slot you need to understand:

1. The recipient (who the letter is addressed to)

Use recipient_* fields for the address block and salutation:

  • recipient_name

  • recipient_address

  • recipient_salutation (produces "Dear …", or "Dear Sir/Madam" if unknown)

By default the recipient is the matter's lead client. But when you generate a document, you can pick a different contact — and every recipient_* field re-points to that contact automatically. This is exactly how "write a letter to a contact" works from the matter screen: pick the template, pick the contact, and their details flow into the letter. You do not need a different template per contact.

2. The client (who you act for)

Use client_* fields when you mean "the client we act for", regardless of who the letter is going to:

  • client_name — e.g. "we act for {{ client_name }}" in a letter to the other side.

Tip: For the address block, prefer recipient_*. For "we act for…", use client_*. If you only ever write to the client, the two behave the same.

Branch (office) fields: If a client_* or recipient_* contact is an organisation with multiple offices and a specific branch has been selected for them on the matter, the *_address fields for that block already resolve to that branch's own address — you don't need to do anything differently. If you also want to name the office itself (e.g. "for the attention of our Manchester Claims office"), use client_branch_name / recipient_branch_name (also available: _branch_code, _branch_phone, _branch_email, _branch_is_head_office). These render as an empty string when no branch is selected, so it's safe to include them in a template used across matters where the contact may or may not have offices.

3. The other parties (the other side)

Use role slots for other people on the matter. These match each party by the role they have on the matter:

  • defendant1_name, defendant1_address

  • claimant1_name, landlord1_name, tenant1_name, purchaser1_name, respondent1_name, applicant1_name

  • party1_name, party2_name … (positional, if you don't want to rely on role)

  • all_defendants, all_claimants, all_parties (comma-separated name lists)

So a single "Letter to the Other Side" template using {{ defendant1_name }} works on every litigation matter — the defendant is whoever holds that role on that matter.



Was this article helpful?
©2026 We Serve You Limited T/A CaseConnect