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.
Paste a deployment email, pick a target environment, and SNT generates all 7 ServiceNow change-management fields with the correct server inventory injected automatically.
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.
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.
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.
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.
One Generate click produces all 7 ServiceNow change-management fields. Each is editable, individually copyable, and re-loaded from history any time.
2–3 sentences on what business risk exists if the change fails.
One concise line under 100 chars summarizing the change.
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.
Plain-text business reason for the change.
Numbered steps: who does what, in what order, including SA tasks and Ansible/MSI automation. References specific servers by name.
Numbered revert procedure if the deployment fails.
Numbered verification steps to confirm successful deployment.
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.
SNT defaults to MiniMax via the shared LLM helper (minimax-direct/MiniMax-Text-01)
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.
Platform MiniMax path with optional model override in Settings.
Structured JSON for all 7 ServiceNow fields. Fast enough for desk use.
Drop-in for high-stakes generations. Switch via Settings, no code change.
Per-user model + default environment + Telegram alerts on AI failure + history retention.
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.
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.
The prompt enforces strict JSON with exactly the 7 ServiceNow fields. No missing sections, no surprise markdown, no "Sure, here's a draft!" preamble.
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.
No back-and-forth. Paste, pick env, Generate. If something is wrong, edit inline — don't prompt-engineer your way to a correct ticket.
Full-text history with CSV/JSON export means compliance has an audit trail without you running a separate spreadsheet.
MiniMax is the cheap default. Settings can point at another shared-LLM model ID when a change is high-stakes.
Single sign-on via the platform shell, shared design tokens, Telegram alerts on failure, and user-scoped settings. Not a bolt-on.
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.
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.
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.
Prompts go to the configured LLM provider (MiniMax by default). Don't paste anything you wouldn't send to a vendor.
Yes — Settings has a per-user model selector. MiniMax is the default.
In the MelTuc platform database, scoped to your user. Only you (and platform admins) can see your tickets. Bulk-delete wipes them any time.
SNT is a premier ServiceNow ticket field generator: paste a deployment email, get the 7 change-management fields as structured JSON. Default model is MiniMax. Health stays cheap. This landing never lists your tickets. If this page disagrees with the signed-in app, trust the app and fix the landing — product contract and tests enforce that rule.
Paste an email. Pick an environment. Click Generate. 7 fields, ready to copy into ServiceNow.
Requires a MelTuc account. Create one free.
Paste a deployment email — MiniMax fills all 7 ServiceNow change-management fields. Templates + history. Login required. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.