Templates
Transactional, product and security templates with variables, a Hindi version and a live preview.
The right notice, on the channel each person chose
Send order, invoice and sign-in notices by email, in-app, SMS or WhatsApp, with each person's preferences.
Each domain keeps templates by key (order.shipped) in a transactional, product or security category, never marketing, with content per channel (email, in-app, SMS, WhatsApp), {{variables}} with fallbacks, a Hindi translation, sample data and a live preview; twelve ready templates cover orders, invoices, payments, appointments, sign-in and one-time codes. Subscribers carry the business's own id, email, phone, name, locale and data, with preferences per category and channel and an hourly or daily email digest on a /preferences/<token> page in the domain's brand; security notices cannot be turned off. POST /api/v1/notify takes a template key, a subscriber and data with an idempotency key, and each channel is queued or skipped with the reason. Delivery runs from D1: a first try at once, then a cron every minute with backoff over six tries, a daily cap per domain and a limit per address; the log shows each channel's status and failure reason, with retry and CSV. Email goes from notifications@appneural.com in the domain's name; SMS and WhatsApp use the business's own MSG91, Twilio, Gupshup or WhatsApp Cloud API account, sealed with VAULT_KEY and off until set up. An in-app feed (GET /api/v1/feed with an HMAC subscriber hash) behind an /embed.js bell, webhooks, and Claude for template drafts and Hindi translation.
What Notifications does for you.
Transactional, product and security templates with variables, a Hindi version and a live preview.
Each person turns categories and channels on or off; security notices always go out.
Every channel's status and reason, with retries, digests and daily limits.
A suggested path for Notifications. What you can do depends on your access in the app.
Start from one of twelve ready templates, or describe one for Claude to draft.
Call POST /api/v1/notify with a template key and a subscriber.
See what was sent, skipped or failed, and retry.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps templates by key (order.shipped) in a transactional, product or security category, never marketing, with content per channel (email, in-app, SMS, WhatsApp), {{variables}} with fallbacks, a Hindi translation, sample data and a live preview; twelve ready templates cover orders, invoices, payments, appointments, sign-in and one-time codes. Subscribers carry the business's own id, email, phone, name, locale and data, with preferences per category and channel and an hourly or daily email digest on a /preferences/<token> page in the domain's brand; security notices cannot be turned off. POST /api/v1/notify takes a template key, a subscriber and data with an idempotency key, and each channel is queued or skipped with the reason. Delivery runs from D1: a first try at once, then a cron every minute with backoff over six tries, a daily cap per domain and a limit per address; the log shows each channel's status and failure reason, with retry and CSV. Email goes from notifications@appneural.com in the domain's name; SMS and WhatsApp use the business's own MSG91, Twilio, Gupshup or WhatsApp Cloud API account, sealed with VAULT_KEY and off until set up. An in-app feed (GET /api/v1/feed with an HMAC subscriber hash) behind an /embed.js bell, webhooks, and Claude for template drafts and Hindi translation.
Marketing email belongs to Campaigns; the inbox belongs to Mail; automations that trigger notices belong to Workflows.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
notifications.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.