Notification Readiness

Notification readiness determines which channel Motornauts can use for supported events.

Steps

1. Tenant Admin reviews enabled modules.
2. Confirm customer contact availability separately from channel consent.
3. Confirm an explicit current SMS grant and SMS readiness if SMS is expected. A phone number alone does not opt the customer in.
4. Confirm email delivery and templates if email is used.
5. Send only customer-safe content; keep detailed service information in the portal.
6. Review notification attempt state and failures. A failed channel does not automatically trigger a different delivery channel.

For post-delivery feedback, missing SMS consent or contact records a skipped attempt. It does not block the in-app/portal path or otherwise eligible email delivery. The current feedback workflow has no authoritative SMS-preference source, so do not expect feedback SMS delivery until Motornauts adds that separate capability.

Use the portal for sensitive details such as estimates, private documents, invoices, and service history. Customers can open the related appointment, estimate, invoice or service visit directly from its inbox update. Share feedback opens eligible feedback after sign-in. An update whose related record is no longer available may remain readable without an action. Appointment times follow the service branch timezone. Inbox update times show the workshop’s timezone alongside the date, so workshops and customers can compare times reliably. Before testing appointment reminder SMS, confirm the customer has current durable SMS consent. Feature enablement and a valid phone are insufficient by themselves. A later withdrawal or opt-out wins at worker send time and is recorded as a skipped attempt; staff should not retry or bypass that decision by creating a provider message directly.

Use an appointment more than 24 hours away to expect both reminder windows. An appointment more than two hours but no more than 24 hours away receives only the two-hour window; appointments at or inside two hours receive neither. Rescheduling replaces obsolete pending windows. Temporary queue failure does not require staff to reconfirm or reschedule the appointment: the saved reminder is recovered with its stable job identity. An unexpectedly early job is moved back to its persisted due time, and channel-dispatch failures retry without treating partial queueing as a completed reminder.