> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/set-up-your-studio/templates/account-contact-and-employee-templates.md).

# Account, contact and employee templates

The extra fields your accounts, contacts and employees carry. Set once, rarely touched again.

These three work differently from event, task, email and form templates. They don't generate anything or trigger anything. All they do is decide which custom fields a record carries.

**Templates > Account Templates**, **Contact Templates** or **Employee Templates**.

## Fields live on the template, not the record

This is the part that surprises people. You can't add a custom field to one account. You add it to the **account template**, and every account using that template gets it.

So "how do I add a field to this school?" really means "which template is this school on, and does that template have the field?"

## They're optional

When you create an account, contact or employee, the template defaults to **Blank**, which means no template and no custom fields. That's fine, and plenty of records never need one.

The same is true on import: leave the Template Name column empty and the record is created without a template.

So reach for these when you have something extra to capture, not because every record needs one.

## Different templates for different kinds of account

You pick the template when you create the record, which is how you give different records different fields.

A studio working with both schools and sports leagues might run two account templates, because a league needs season dates and a school needs enrolment numbers. Neither has to carry the other's fields.

Most studios don't need that. One per record type is usually enough and easier to keep tidy.

## What they're for

Schedulink already stores the obvious things: names, addresses, emails, phone numbers. Custom fields are for what's specific to how your studio works.

On **accounts**, studios commonly add district, enrolment size, contract renewal date, lab account number, preferred background, or which of your studios covers them.

On **contacts**, things like preferred contact method, best time to call, or whether they've been sent a W-9.

On **employees**, certifications, equipment assigned, shirt size, or which regions they'll travel to.

## When to add a field

When you find yourself putting the same kind of information in a notes field over and over.

A custom field is searchable, filterable, and can be shown as a column on your lists. A note is none of those things.

## Adding a field later

You can add fields to these templates at any time. Existing records on that template pick up the new field, empty, ready to fill in.

So there's no need to design these perfectly at the start. Add fields as you discover you need them.

## Using them on import

If you're importing accounts or contacts and want them on a template, build the template first. The Template Name column is matched against templates that already exist, and a name that doesn't match fails the whole import. See Preparing your data for import.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/set-up-your-studio/templates/account-contact-and-employee-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
