| name | ktb-notification-writer |
| description | Generates first-draft notification copy (EN + TH) for the Krungthai Business corporate banking platform, following the official UX Writing Guideline v1.0. Use this skill whenever the user asks to write, draft, or generate notifications, alerts, or messages for the Krungthai Business / KTB platform — including any request mentioning channels like email, SMS, push notification, inbox, or pop-up in the context of banking workflows, transactions, or approvals. Also triggers for requests like "generate notification copy", "write a notification for [service]", "draft an alert for [workflow status]", or "create copywriting for [scenario]". Always use this skill even if the user only asks for one channel or one language.
|
KTB Notification Writer
Generates bilingual (EN + TH) notification copy for all channels on the
Krungthai Business corporate banking platform, strictly following the
UX Writing Guideline v1.0.
When Triggered
Use this skill for any request that involves writing or drafting notification
messages for the Krungthai Business platform — e.g.:
- "Write a notification for a rejected transfer"
- "Generate push + email copy for a successful PN issuance"
- "Draft an SMS for a pending approval"
- "Create inbox pop-up copy for a schedule reminder"
Step 1 — Gather Requirements
If the user hasn't provided all of the following, ask before writing. Keep the
ask concise — list missing items in one message.
Required inputs:
| Field | Example |
|---|
| Service Name (EN) | Virtual Accounts – Distribute Virtual Balances |
| Service Name (TH) | บัญชีเสมือน – จัดสรรยอดเสมือน |
| Status / Event | Unsuccessful / Pending Review / Successful / etc. |
| Recipients | Internal (all) / Checker / Approver / Maker / External |
| Channels needed | Email, SMS, Push, Inbox Pop-Up (any subset) |
| Key data fields | Ref. No., Amount, Value Date, From/To Account, etc. |
| Navigation path | My Task: Task Status / Dashboard: Task Status / etc. |
Optional (ask only if relevant):
- Error reason field needed? (Unsuccessful scenarios)
- External recipient email also needed? (Successful scenarios)
- Scheduled / bulk transaction? (affects field list)
- Contact email:
corporate.contactcenter@krungthai.com (default) or cash.management@krungthai.com
Step 2 — Determine Notification Type
Before writing, classify the notification:
| Status | Type | Pop-Up? |
|---|
| Pending Review, Pending Approval, Returned (to Maker) | Pending Action | No |
| All others (Successful, Unsuccessful, Rejected, Discarded, Returned non-Maker, Schedule Reminder, Expiry) | Alert | Yes |
Step 3 — Write the Copy
Generate copy for every requested channel. Always produce EN and TH for each.
Read references/copy-rules.md for the complete rules before writing.
Channel formats at a glance
Email
- Subject:
[App Name]: [Event] (Ref. No. {{refNo}}) ({{companyId}})
- External recipients: omit
({{companyId}})
- Body structure: Salutation → Opening sentence → Navigation hint → Details block → Status → Closing → Sign-off → Disclaimer
- Details block: labelled fields, one per line,
Field Name: {{value}}
SMS
- 1–2 sentences only
- Include: service name, Ref. No., amount (if any), status, navigation or next step
- End with
({{companyId}}) for internal recipients
Push Notification
- 1 sentence: event summary with Ref. No. + amount (if any) + status
- End with:
Click to view details of this request/transaction.
- End with
({{companyId}}) for internal recipients
- Include a Label tag (product category — see copy-rules.md §12)
Inbox Pop-Up (Alert type only)
- Title: Short noun phrase (e.g. "Transaction Unsuccessful")
- Body: Lead sentence + condensed fields (label on one line, value on next) + Status last
Output format
Present copy in this structure for each channel:
## [Channel Name]
### English
[copy]
### Thai
[copy]
Step 4 — Quality Check
Before presenting output, verify:
Reference Files
Read these files as needed:
references/copy-rules.md — Full copy rules: tone, field labels, placeholder conventions,
sentence formulas by scenario, bilingual requirements, disclaimer text, and naming conventions.
Read this before writing any copy, especially for unfamiliar scenarios.
