uControlSection — Email Responses
Section — Email Responses
What this section captures
The Email Responses section holds the canned reply templates the ITSM tool sends to a customer at key points in a ticket’s lifecycle — ticket logged, ticket acknowledged, ticket assigned, ticket resolved, ticket reopened, etc.
Why it matters
Email templates are the customer-facing voice of the service desk. Standardising them across an engagement keeps the tone consistent and prevents technicians from typing free-form replies that contradict the SLA wording or company branding.
How to fill it in
For each trigger event the ITSM tool supports, add a template row with:
Subject — what the customer sees in their inbox.
Body — the email content. Most tools support placeholder tokens (
,); document them as the customer’s tool requires.Notes — any internal context the reviewer needs to know.
Use the Load defaults button at the top of the page to seed common templates (Acknowledged, Assigned, Resolved, Reopened, Pending Customer, Closed) as a starting point.
Tick the per-row checkboxes to bulk-edit notes or trigger types if you imported a large block from another engagement.
Tone and branding
Templates are written in plain English by default. If the customer has a corporate style guide (e.g. “use first names”, “no exclamation marks”) capture that in the section Notes at the top of the page so the reviewer checks for it before approving.
Language: the seeded default templates are provided in English, but the text is fully editable — you can rewrite any subject and body in whatever language the customer needs, and the templates are stored and sent exactly as you author them. (This is independent of the product’s five UI languages, which control the TekReady interface, not the customer-facing reply text.)
Approval implications
This section follows the standard four-state approval lifecycle: Draft (editable) → Submitted (locked, awaiting the customer’s Manager) → Manager Approved (locked, awaiting the Partner approver) → Final (fully signed off and locked). A reviewer can reject the section back to Draft, with a reason, at either approval step.
Once Final, templates are locked. Any post-go-live tweak needs a reviewer to reject the section back to Draft, which produces an audit-log entry. This protects against ad-hoc changes that bypass the customer’s comms standards.