ReplyRafter · Privacy
Privacy at ReplyRafter
This page explains the lead details ReplyRafter accepts and how they are used for scheduled follow-up emails.
Lead information
- Manual records
- A business can enter a lead’s name, email, company, phone, service, message, source, marketing-consent status, and consent source.
- CSV imports
- Name and email are required. Company, phone, and source are optional. CSV imports leave marketing consent unknown.
- Website enquiries
- A configured website enquiry form collects a name and email, with phone, service, and message as optional fields. Website enquiries leave marketing consent unknown.
Scheduled follow-ups
- Campaign drafts
- A campaign draft defines the email subject and body and exactly three configurable follow-up delays. Each delay can be set from 1 to 90 days.
- Messages
- Scheduled messages are addressed to the lead’s email. Their text can use the lead’s name, company, and service when those details are present.
- Queueing
- Saving a draft stores the campaign settings and does not send an email or queue follow-ups for a lead. Enrolling a lead queues the campaign’s scheduled steps; enrollment does not send an email.
Consent and email delivery
- Marketing consent
- Scheduled marketing follow-ups require recorded affirmative consent. An unknown consent status is not affirmative consent.
- Imports and enquiries
- CSV imports and website enquiries do not collect consent; they leave it unknown.
- Live delivery
- Live email delivery is currently unavailable until valid email setup is provided and the verified app owner enables delivery.
Replies, bookings, and opt-outs
- Replies and bookings
- ReplyRafter does not detect inbox replies automatically and has no separate booking state. When a customer replies or books, the business marks the lead as replied to stop its remaining scheduled follow-ups.
- Opt-outs
- Marking a lead as opted out also stops its remaining scheduled steps and prevents new sequences or retries.