Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.daylit.com/llms.txt

Use this file to discover all available pages before exploring further.

A collection program is Daylit’s dunning engine: a set of rules that automatically determines which customers to contact, when to contact them, and what to say — based on how long their invoices have been overdue. Once configured and activated, a collection program runs on a recurring schedule and generates outreach touchpoints without requiring your team to manually identify who needs follow-up. Collection programs are best suited for companies that want systematic, at-scale dunning across a large customer base.

​
Collection programs vs. sequences

Both collection programs and sequences automate customer outreach, but they serve different purposes:
Collection programsSequences
EnrollmentAutomatic — customers are enrolled based on invoice aging rulesManual — you choose which customers to enroll
CadenceConfigured by send days, send time, and cadence (weekly, biweekly, etc.)Configured by step offsets in days from enrollment start date
ScopeAccount-level or invoice-level touchpointsCustomer-level outreach
Use caseSystematic dunning across all overdue accountsTargeted nurture or pre-due outreach for specific customers

​
How collection programs auto-enroll customers

When a collection program is active, Daylit’s scheduler runs on the configured cadence (for example, every Monday at 9:00 AM in your timezone). On each run, it:
  1. Identifies all customers with invoices overdue by a number of days matching a touchpoint’s offset.
  2. Checks each customer’s enrollment status — enrolled customers receive touchpoints; unenrolled customers are skipped.
  3. Generates a batch of touchpoints for all eligible enrolled customers.
  4. Delivers the batch automatically (auto mode) or holds it for your review (review mode), depending on the touchpoint’s delivery setting.
You cannot pause or archive the last active collection program in your account. Daylit requires at least one active program to keep the dunning pipeline running.

​
Touchpoints: steps in a collection program

A touchpoint is a single outreach event within a collection program. Unlike sequence steps — which fire once per enrollment — touchpoints fire repeatedly on the program cadence for as long as the customer is enrolled and their invoice remains unpaid. Each touchpoint has the following settings:
SettingDescription
LabelA short name for the touchpoint, used internally (for example, “30-day overdue email”).
Offset daysHow many days past the invoice due date this touchpoint applies to. A touchpoint with offset 30 fires for invoices that are 30+ days overdue.
Target levelInvoice — one touchpoint per overdue invoice; Account — one touchpoint per customer account summarizing all overdue invoices.
ChannelCurrently supports email only.
Delivery modeAuto — sends without review; Review — holds the touchpoint in the inbox for your approval before sending.
Content modeTemplate — uses a subject and body template; Prompt — uses AI to generate the message at send time.
TemplateThe email template assigned to this touchpoint, with variable placeholders for invoice data.

​
Create a collection program

  1. Go to Settings → Collection programs.
  2. Click New program.
  3. Enter a program name.
  4. Optionally, select an existing program to duplicate — this copies the schedule settings and all touchpoints, letting you start from a proven configuration.
  5. Click Create. The new program is created in Active status with a default set of touchpoints.
If you duplicate a program, the new program starts active immediately. If you create from scratch, Daylit seeds a default set of touchpoints based on common dunning intervals (typically 1, 7, 14, and 30 days past due).

​
Configure program schedule

From the program detail view, you can update:
  • Send days — Which days of the week the program runs (for example, Monday and Wednesday).
  • Send time — The local time of day batches are generated and delivered.
  • Cadence — How many weeks between runs (1 = weekly, 2 = biweekly).
  • Timezone — The timezone used to interpret the send time.
  • Sender mailbox — The connected email account used to send program emails.
Changing any schedule field on an active program triggers an automatic replan that reschedules all pending touchpoints to align with the new cadence.

​
Add touchpoints to a program

  1. Open the program in Settings → Collection programs.
  2. Click Add touchpoint.
  3. Configure the offset days, target level, delivery mode, and content mode.
  4. Assign an email template or write the template inline.
  5. Save the touchpoint. Daylit immediately replans scheduled touchpoints to include the new step.
Each combination of offset days and target level must be unique within a program. You cannot have two active touchpoints at offset 30, account level, in the same program.
To archive a touchpoint that has historical send data (rather than deleting it), click Archive on the touchpoint. Archived touchpoints no longer generate new scheduled rows but remain visible in historical reports.

​
Enrollment management

The Enrollments tab of a collection program shows every customer and their current enrollment status. You can filter by enrollment status, customer name, label, or open balance.
Enrollment statusMeaning
EnrolledThe customer is actively enrolled and will receive touchpoints on the next program run.
Not enrolledThe customer exists in your account but has not been enrolled in this program.

​
Enroll or unenroll customers

To change enrollment status for a single customer:
  • Find the customer in the enrollments grid and toggle their enrollment on or off.
To bulk update enrollments:
  1. Select multiple customers using the checkboxes.
  2. Use the bulk action toolbar to enroll or unenroll the selected group.
  3. Daylit confirms the count of changes before applying them.
Filter the enrollments grid by “Not enrolled” and sort by open balance descending to find high-value customers who are not yet in your dunning program.

​
Review batches

When a touchpoint is configured with Review delivery mode, Daylit groups the generated emails into a review batch before sending. A review batch represents all the emails due to go out for a specific touchpoint on a specific send date. You review batches from Inbox → Dunning. Each batch shows:
  • The customer and associated invoices
  • The rendered email subject and body
  • The recipient email address
From the review inbox, you can:
  • Approve the batch to send all emails in it.
  • Reject the batch to cancel sending for this cycle.
  • Edit the email content or recipients before approving.
  • Group batches by customer to review account-level and invoice-level emails side by side.
Batches that are not reviewed before the next scheduled run cycle are automatically cancelled and superseded by the next run’s output.

​
Scheduled touchpoints

Scheduled touchpoints are the queue of upcoming automated communications that Daylit has planned but not yet sent. You can view them from Inbox → Scheduled and filter by program, customer, or status. Statuses for scheduled touchpoints include:
StatusMeaning
ScheduledPlanned for a future send date, not yet due.
ProposedDue and waiting for review (review-mode touchpoints only).
CompletedSuccessfully sent or manually marked complete.
CancelledCancelled before sending.
FailedAttempted delivery failed.
SupersededReplaced by a newer scheduled row for the same invoice/touchpoint combination.
SkippedSkipped by the engine (for example, customer had no overdue invoices on the run date).
You can manually cancel an individual scheduled touchpoint from this view without affecting other touchpoints in the program.

Action center

Review and send one-off AI-recommended collection actions.

Collection sequences

Build manual multi-step outreach cadences for targeted customers.

AI email drafting

Learn how program email templates are rendered with live data.

Settings: integrations

Connect an email account to use as the program sender mailbox.