ONE EMAIL.
SEVEN FIELDS.
SNT turns deployment emails into fully populated ServiceNow change-management tickets in 5–15 seconds. Paste the email, pick the target environment, click Generate — the AI writes the business impact, descriptions, justification, implementation plan, backout plan, and test plan, then auto-injects the full server inventory for the chosen environment so you don't have to type host names ever again.
From Deployment Email to Ticket in 6 Steps
Paste a deployment email, pick a target environment, and SNT generates all 7 ServiceNow change-management fields with the correct server inventory injected automatically.
3-Column Workflow
Left column: paste the email, optionally hit Rewrite for spell/grammar fix, pick the target environment, click Generate. Center column: 7 editable fields fill in 5–15 seconds. Each field has its own Copy button so you can paste straight into ServiceNow without touching anything else. Right column: searchable history of every ticket you've generated, click any row to reload it.
Servers Auto-Populated
Pick an environment from the dropdown. The matching server inventory is shown to the AI as prompt context (so the implementation plan can name specific servers) AND a deterministic "Servers in Scope" block is appended to the Detailed Description after generation. No more forgetting a host. No more typo'ing PRT2HICISAPP as PRT2HICISAPPP.
Servers in Scope — Production
Application Servers:
- PRT2AICISAPP.dti.state.de.us
- PRT2BICISAPP.dti.state.de.us
- PRT2CICISAPP.dti.state.de.us
- PRT2DICISAPP.dti.state.de.us
- PRT2EICISAPP.dti.state.de.us
- PRT2FICISAPP.dti.state.de.us
(... 6 more ...)
Work Flow Servers:
- PRT2AICISWK.dti.state.de.us
- PRT2BICISWK.dti.state.de.us
(... 4 more ...)
Batch Server:
- PRT2AICISBT.dti.state.de.us
Storage Server:
- prt2hicis.dti.state.de.us
Searchable Audit Trail
Every saved ticket is searchable by title, short description, or original input text. Filter by model, see token usage, drill into any record to reload it back into the editor, or bulk-delete. CSV and JSON exports for compliance reporting.
Everything You Need to Write Change Tickets Fast
SNT is a focused change-management pipeline — not a chat wrapper. A deployment email goes in, a fully structured ticket comes out, the right servers get named, and every field is saved and searchable.
Every ServiceNow Field, Drafted
One Generate click produces all 7 ServiceNow change-management fields. Each is editable, individually copyable, and re-loaded from history any time.
Business Impact
2–3 sentences on what business risk exists if the change fails.
Short Description
One concise line under 100 chars summarizing the change.
Detailed Description
Full narrative: what's deployed, which servers, environment, date/time, who performs it. Auto-appended with the Servers in Scope block for the selected environment.
Justification
Plain-text business reason for the change.
Implementation Plan
Numbered steps: who does what, in what order, including SA tasks and Ansible/MSI automation. References specific servers by name.
Backout Plan
Numbered revert procedure if the deployment fails.
Test Plan
Numbered verification steps to confirm successful deployment.
Server Inventory by Environment
SNT ships pre-loaded with the exact server inventory for each environment. Pick one from the dropdown and the right servers are injected into the ticket automatically.
OpenRouter + Claude Haiku 4.5
SNT routes through OpenRouter (platform convention) and defaults to anthropic/claude-haiku-4.5
for cost and speed. Switch to claude-sonnet-4-5 in Settings any time you need higher-quality
ticket fields. Token usage is logged per generation and shown on the dashboard for the trailing 7 days.
OpenRouter
Single API for 100+ models. Fail-over and routing handled upstream.
Haiku 4.5 (default)
~$0.001 per generation. Cleanest balance of speed and quality for ticket-style structured output.
Sonnet 4.5 (upgrade)
Drop-in for high-stakes generations. Switch via Settings, no code change.
Settings page
Per-user model + default environment + Telegram alerts on AI failure + history retention.
What a Generated Ticket Looks Like
Below is a real example: a one-paragraph deployment email on the left, the 7 SNT-generated fields on the right. No hand-editing, no cleanup — this is what lands in the editor after a single Generate click against the Production environment.
Please deploy CICIS v3.1.0 to Production on Friday at 7pm EST. SA will run the Ansible playbook to push the new JAR file to all production app servers, then bounce the work flow servers. Health checks should pass before we hand off to ops. The release contains the Q2 compliance fixes so we cannot miss the window.
Thanks, M.
The Case for a Dedicated Tool
You could paste a deployment email into a chat UI and ask for ServiceNow fields. It would kind of work. SNT exists because "kind of works" is how tickets end up with the wrong host names, missing backout plans, and inconsistent business impact paragraphs three quarters in a row.
Structured output, always
The prompt enforces strict JSON with exactly the 7 ServiceNow fields. No missing sections, no surprise markdown, no "Sure, here's a draft!" preamble.
Server names are deterministic
The Servers in Scope block is appended in code, not generated by the model. The AI can reference hosts by name but cannot invent or misspell them.
One click, not a conversation
No back-and-forth. Paste, pick env, Generate. If something is wrong, edit inline — don't prompt-engineer your way to a correct ticket.
Every ticket saved
Full-text history with CSV/JSON export means compliance has an audit trail without you running a separate spreadsheet.
Cheap by default
Haiku 4.5 costs roughly $0.001 per generation. Sonnet 4.5 is one setting away when a change is high-stakes.
Fits the MelTuc platform
Single sign-on via the platform shell, shared design tokens, Telegram alerts on failure, and user-scoped settings. Not a bolt-on.
Common Questions
Does SNT push directly to ServiceNow?
No. SNT generates the content. You paste each field into ServiceNow yourself using the per-field Copy buttons. This keeps you in control of what gets submitted and avoids coupling to a specific ServiceNow instance.
Can I add a new environment?
Yes. Provide the server inventory to the platform owner and it's added to the environment registry. The dropdown picks it up on next restart.
What if the AI gets something wrong?
Every field is an editable textarea. Fix it inline, click Save, and it's stored that way in history. If generations fail repeatedly, Telegram alerts fire to the configured chat.
Is my input sent to a third party?
Prompts route through OpenRouter to Anthropic Claude. Don't paste anything you wouldn't send to a vendor. Settings let you lower retention if needed.
Can I switch models?
Yes — the Settings page has a per-user model selector. Haiku 4.5 is the cheap default; Sonnet 4.5 is one click away.
Where is ticket history stored?
In the MelTuc platform database, scoped to your user. Only you (and platform admins) can see your tickets. Bulk-delete wipes them any time.
Stop Writing Tickets by Hand.
Paste an email. Pick an environment. Click Generate. 7 fields, ready to copy into ServiceNow.
Requires a MelTuc account. Create one free.