Skip to content

HomePeriodic follow-up emails or SMS to familiesCommunication and ReportingPeriodic follow-up emails or SMS to families

Periodic follow-up emails or SMS to families

**Purpose**

1.1. Ensure families receive timely updates and reminders post-adoption.
1.2. Track family engagement and child well-being through scheduled communication.
1.3. Comply with reporting requirements by maintaining consistent, documented outreach.
1.4. Facilitate ongoing support, resource sharing, and feedback collection.
1.5. Reduce staff manual workload while enabling tailored and regular touchpoints.

**Trigger Conditions**

2.1. Scheduled time intervals post-adoption (e.g., 1, 3, 6, 12 months).
2.2. Completion of case milestones or events logged in database.
2.3. Lack of family response within set durations (trigger reminders).
2.4. Updates entered in the family or child case record.

**Platform Variants**


3.1. **Twilio SMS API**
• Feature/Setting: Use programmable SMS API; configure sending logic using phone number field and schedule by webhook or cron trigger.
• Sample: `POST /2010-04-01/Accounts/{AccountSid}/Messages.json` with family mobile, dynamic template.

3.2. **SendGrid Email API**
• Feature/Setting: Configure transactional email; set templates and schedule/send via API.
• Sample: `POST /v3/mail/send` with dynamic template ID and merge data with family info.

3.3. **Mailgun Email API**
• Feature/Setting: Scheduled emails with event-tracking; set up using template storage.
• Sample: `POST /v3/{domain}/messages` with personalized subjects and content.

3.4. **AWS SES (Simple Email Service)**
• Feature/Setting: Automation rules; schedule using Lambda and SES send API.
• Sample: Use `SendEmail` action with event-driven Lambda function.

3.5. **Microsoft Graph API**
• Feature/Setting: Send mail from Outlook 365; configure periodic scripts.
• Sample: `POST /users/{id}/sendMail` with stored message templates and recurrence setup.

3.6. **Salesforce Marketing Cloud**
• Feature/Setting: Journey Builder automation; scheduled messages by adoption stage.
• Sample: Configure Journey step for “Send Email” or “Send SMS” on milestone triggers.

3.7. **HubSpot Workflow Automation**
• Feature/Setting: Automated workflows; set periodic touchpoints based on adoption status.
• Sample: Setup “Delay” and “Send Email” actions in workflow builder.

3.8. **Zoho CRM Automation**
• Feature/Setting: Blueprint rules for follow-up notifications; tie to deal milestones.
• Sample: Configure “Workflow Rule” for Send Email/SMS on time-based criteria.

3.9. **Google Cloud Functions + Gmail API**
• Feature/Setting: Scheduled Cloud Function calls Gmail API to send emails.
• Sample: Function triggers Gmail `users.messages.send` for dynamic recipients.

3.10. **ActiveCampaign Automation**
• Feature/Setting: Automation series; configure follow-up chains for different case stages.
• Sample: “Automation Trigger: Date-based” → “Send Email” action.

3.11. **Freshdesk Omnichannel**
• Feature/Setting: Automated ticket creation and messaging to family contacts.
• Sample: “Automations → Observer Rule” to send emails/SMS at intervals.

3.12. **Intercom Custom Bots**
• Feature/Setting: Scheduled messaging using Intercom series.
• Sample: “Outbound Messages” sent to family users at set post-adoption dates.

3.13. **Zapier Webhooks**
• Feature/Setting: Scheduler trigger linked to Email/SMS action on data change.
• Sample: “Schedule by Zapier” → “Webhooks” → external API call (e.g., Mailgun/Twilio).

3.14. **Slack Incoming Webhooks**
• Feature/Setting: Notify staff on missed family responses; reminder configuration.
• Sample: Trigger scheduled message if no reply in set period.

3.15. **ClickSend SMS/Email**
• Feature/Setting: Scheduled SMS or Email campaigns to family lists.
• Sample: Use “Scheduled Sends” API with adoption milestone segmentation.

3.16. **Plivo SMS API**
• Feature/Setting: Automated SMS using scheduled or event-based triggers.
• Sample: `POST /v1/Account/{auth_id}/Message/` for status updates.

3.17. **Pabbly Connect**
• Feature/Setting: Workflow automations for periodic messaging; use event JSON.
• Sample: Trigger: Scheduled time → Action: Send Email/SMS module.

3.18. **WhatsApp Business API**
• Feature/Setting: Automated WhatsApp messages; use message templates for periodic follow-ups.
• Sample: `POST /v1/messages` for families who opted for WhatsApp updates.

3.19. **Sendinblue (Brevo) Automation**
• Feature/Setting: Email cadence workflow; configure based on contact lifecycle.
• Sample: “Workflow Automation” → trigger by adoption event, then send scheduled messages.

3.20. **Klaviyo**
• Feature/Setting: Event-based flows for adoption agencies; schedule follow-up sequence.
• Sample: “Flow Trigger: Date property” → “Email/SMS Action” with family details.

3.21. **Monday.com Automations**
• Feature/Setting: Timeline-based automations to email/sms via integrations.
• Sample: “When status changes to X, send custom email/SMS to person column.”

**Benefits**

4.1. Ensures proactive, consistent communication with families.
4.2. Standardizes record-keeping and compliance reporting.
4.3. Frees staff to focus on complex, in-person case management.
4.4. Improves family satisfaction and engagement post-adoption.
4.5. Allows easy scaling of outreach as caseload grows.

Leave a Reply

Your email address will not be published. Required fields are marked *