Inquiry saved
The record is written to the database first, independent of whether any notification succeeds.
This system captures every enquiry to a durable record before any notification runs and records a review task with a due date. Provider delivery, named assignment, and escalation are separately disclosed below.
The record is written to the database first, independent of whether any notification succeeds.
The configured Resend worker can process queued outbox events with bounded retries. Provider acceptance remains distinct from delivery, and signed callbacks are required before delivery is shown.
A task with a due date keeps the next review visible; a named assignee is not yet implemented.
A provider acceptance is never relabelled as delivered without the actual delivery confirmation.
An inquiry persists before a send attempt, and the current database records a next action and due date. This does not prove a named assignee or a completed follow-up.
The public request path creates a durable record. The deployed owner dashboard still needs authorised MFA-session evidence; controlled owner-email delivery is connected separately.
Resend accepts the configured owner-alert path and signed delivery callbacks persist provider events. Messaging and routine sender-domain delivery remain unconnected and are not claimed.
A client workflow needs approved provider terms, a configured account, consent rules, assignment/escalation ownership, and verified callback evidence before it can be described as operational.
Lite tier implementation fee:
Lite covers the agreed architecture. Standard and Pro add depth, integrations, and verified provider setup. Domain, hosting, AI compute, phone numbers, messaging, and calendar provider costs are billed directly by their providers and are never marked up by IronWake.