What it does
Custom templates let you configure Earmark to produce artifacts that match your team’s exact formats and workflows. Whether you need product requirements in a specific structure, engineering tickets that match your tracker, stakeholder updates in a particular format, or internal communications that follow a house style, we’ll build a custom task agent that handles it.Why it matters
Every team has its own way of working. Built-in templates cover common patterns, but your sprint retro format, your client debrief structure, or your post-mortem checklist is unique. Custom templates close that gap so Earmark produces outputs you can use immediately, without reformatting.How it works
Share your format
Send us the structure you want Earmark to generate. This can be:
- An existing template or document format your team already uses
- A ticket format from your project tracker
- A checklist or workflow you follow after meetings
- A past example of an artifact you liked
We create the task agent
Our team configures a custom task agent that understands your format and produces outputs aligned to the structure you provided.
Use it in meetings
The task agent appears in your template library. Run it during any conversation and it produces the artifact automatically, just like a built-in template.
What makes a good template
The best custom templates share a few traits:- Clear structure with defined sections, fields, or headings
- Repeatable workflow that your team follows regularly
- Recurring artifact that gets created after most meetings (not a one-off)
Request a custom template
From the template library
Open the template library in any meeting and select Request template. Fill in the details and submit, and we’ll follow up by email.By email
Contact support@tryearmark.com with:- What it’s called — a short name for the template
- What it does — describe the artifact and its purpose
- A sample or format — attach an example document, screenshot, or written structure
- Key fields or sections — call out any specific sections the output should always include
- Where the output will be used — tickets, docs, Slack updates, email, or something else
Tips
- Start with a real example from a past meeting rather than describing the format from memory
- Include section headings, field names, and any boilerplate text you always use
- Let us know which meetings this template will be used in so we can optimize for that context
- You can request changes anytime after the template is live


