Trigger
service.due
YDretention module
Service-Due Reminder
For recurring services (HVAC tune-up, pest treatment, cleaning), remind customers when they're due. Lock in recurring revenue that used to depend on customer memory.
The pain this solves
Lock in recurring revenue that used to depend on customer memory. The workflow exists to remove a repeated operational leak: a missed response, delayed follow-up, manual handoff, billing drag, review friction, or retention gap.
What it does
send email, send sms, offer booking link
Success metrics
due to booking rate, recurring revenue share
Functional workflow contract
- Input: contact record
- Input: last service record
- Input: service cadence
- Action: send email
- Action: send sms
- Action: offer booking link
- Setting: Default service cadence (months)
- Setting: Lead time (days)
- Setting: Allow customer to set cadence
Traceability
| Catalog code | service_due_reminder |
|---|---|
| API record | /api/catalog/modules?code=service_due_reminder |
| Activation API | POST /api/tenants/activate-module with module_code=service_due_reminder |
| Required capabilities | crm, email, sms |
| Compliance guards | sms_opt_out, quiet_hours |
| Status | spec · guided activation |
If a tenant lacks entitlement or required capabilities, activation returns a typed deferred state rather than pretending the workflow is live.
Recommended for
owner-operatoroffice-managerhvacpest-controlcleaning
What ships behind the promise
This marketplace page is not standalone brochure copy. Every activated item belongs to the same business-unit standard: catalog traceability, tenant entitlement checks, capability checks, event logs, workflow state, internal provider interfaces, optional PostHog analytics, AI/MCP tool metadata, central configuration, build repair telemetry, and resumable checkpoints.
Traceable activation
Each promise maps back to catalog data, API records, activation routes, capability requirements, and deferred states when a tenant is not ready.
Self-hostable core
Core logic uses internal interfaces for payments, email, storage, analytics, documents, AI, signatures, and notifications. External services stay optional adapters.
AI and MCP ready
Generated builds include tool-registry evidence, permissions, workflow definitions, prompt assets, retrieval scaffolding, and model routing guidance.
Repairable build pipeline
Failed build classes feed into detector/remediator pairs, BUILD-REPORT telemetry, and resume checkpoints so future builds continue from the last verified state.
Media and analytics expansion
When enabled, video asset planning and PostHog-ready event tracking connect marketing content to product, funnel, revenue, and customer lifecycle metrics.
Niche validation
Content, offers, workflows, pricing, contracts, and support language are checked against the niche, buyer, location, business model, and primary offer.