Request scheduling, delays, and reminders
How Reveddy schedules the first testimonial email after Shopify or Stripe events, follow-up reminders, and what each request status means.
Automation should feel considerate, not impatient. Reveddy lets you set a request delay in days after the triggering event—commonly order fulfillment for Shopify or a successful payment for Stripe—so you only ask once the product has arrived or the service experience has started. Adjust this per campaign: digital goods might need a short delay, while physical shipments often need a longer one.
Follow-up reminders can nudge customers who did not open or complete the form. You can enable or disable reminders per campaign and set how many days after the initial send the reminder should go out. Reminders respect the same branding and legal disclosures as the first message. If you find unsubscribe complaints rising, lengthen delays or reduce reminder frequency.
Each testimonial request moves through statuses such as pending, sent, reminded, completed, and expired. These states help you diagnose funnels in Analytics and support tickets: for example, many “sent” without opens may indicate subject-line or deliverability issues, while opens without completions may point to form friction or incentive confusion.
When changing delays on a live campaign, remember that in-flight jobs queued in the worker may already use previous timing. After major edits, spot-check a few new requests to confirm schedules match the campaign summary you expect.