Templates

Templates are reusable response structures that DelegateZero can adapt. They help maintain consistent tone and formatting while allowing the content to vary based on context. Think of templates more like starting points for how to handle something, not hard and fast rules.

Templates might be used for instances such as:

• A standard approval response
• A polite decline message
• A recurring report email structure

Here are some examples:

Client-facing update email

When sending an analytics report via email to a client, use the template below.

Subject: {{client_name}} — {{reporting_period}} update

Hi {{client_contact}},

Here's a brief update on {{reporting_period}} performance. Overall trends are consistent with expectations, with {{key_metric}} being the primary driver.
Let me know if you'd like a deeper breakdown or have any questions.

Best,
-Tyler

Escalation response:

Whenever we need to escalate internal communication, respond with a message like this:

I'm looping this through for review before responding, as it involves {{reason_for_escalation}}.
I'll follow up once I have confirmation.

Polite refusal

When we need to refuse a request, respond with a concise but polite message such as:
I can't move forward with this as requested, but I'm happy to discuss alternatives.

A couple things to keep in mind regarding templates:

• Templates describe what the response should look like, not when it should be used (think playbooks).
• Templates may be used across various channels and adapted by DZ based on context and confidence. You can specify how you might want a certain message formatted for different channels.

Use templates to define how responses are structured. Use playbooks to define how decisions are made.