GridMagik can use a configured email provider, records reservation communication deliveries, and includes tenant communication settings. A complete automated lifecycle across confirmations, receipts, reminders, changes, follow-up, SMS, consent, retry, and suppression remains partial.
The application has shared email delivery plumbing, tenant sender and reply metadata, template foundations, and reservation communication records. Demo requests now use the same provider layer and fail honestly if durable capture or delivery cannot be completed.
Confirmation, receipt, reminder, reschedule, cancellation, waiver, follow-up, and racing-report messages do not become an automated system simply because templates exist. Trigger ownership, recipient selection, idempotency, retry, suppression, and operator visibility must be verified per type.
Before automated SMS or marketing campaigns are released, GridMagik needs explicit consent and preference capture, quiet hours, sender registration, country handling, opt-out enforcement, audience preview, rate limiting, and auditable delivery.
Consent → sender registration → schedule → delivery → STOP enforcement → audit.
No latency, deliverability, or inbox-placement metric is published without measured production evidence.
Use configured delivery infrastructure with explicit failure handling.
Persist the lead and route it through the real provider layer.
Track prepared, sent, delivered, and failed communication records.
External side effects need independent, durable retry guarantees.
Template and delivery foundations exist; full trigger coverage is not claimed.
Provider plumbing is not a complete consent-safe product flow.
Audience, scheduling, attribution, preference, and suppression work remains.
Guests need clear channel choices, opt-outs, and an audit trail.
Email delivery infrastructure and reservation communication records exist. The exact message types and triggers enabled for a venue must be demonstrated and confirmed during rollout.
Not as a complete production feature. Provider plumbing may exist, but consent, sender registration, opt-out enforcement, scheduling, cost visibility, retry, and tenant controls must pass before SMS automation is enabled.
Delivery status is part of the reservation communication model. Broader operator recovery and a durable outbox remain active hardening work.
No. GridMagik does not publish unmeasured inbox-placement or sub-second latency claims. Provider acceptance, recipient mailbox handling, and delivery evidence are separate states.
30-minute walkthrough. Your pricing, your calendar, your receipts — running live in a sandbox on your data. No slides.
