followUpWithin

Followupwithin is a term used in workflow automation, customer support, and CRM to describe the time window after a triggering event during which a follow-up action should occur or a reminder should be sent. The phrase emphasizes timeliness rather than the content of the follow-up.

Representations vary by system. It may appear as a duration value such as 24h, 2d, or P2D, a relative offset from the trigger, or as a field name in an API payload (for example, followUpWithin or followupwithin). Some platforms also convert this into working hours, excluding weekends and holidays.

Typical use cases include ensuring timely responses to support tickets, re-engagement in lead nurturing campaigns, or standard task reminders. It is often paired with business hours and SLA rules to determine when a reminder should be sent or when escalation should occur.

Examples: If a ticket is opened at 10:00, followUpWithin: 24h would trigger a reminder at 10:00 the following day, subject to business hours. In a campaign, a followUpWithin of P3D could schedule the next message three days after the last customer interaction.

Implementation considerations: time zone handling, business hours, holidays, and whether the window is inclusive or exclusive. Validation ensures the value represents a valid duration and that it aligns with other SLA constraints.

See also: follow-up, reminder, SLA, workflow automation, due date.