Modules · Meeton Email · Step 4
Cadence
How many emails a person can get, how far apart, how far ahead they are scheduled, and when the sequence starts over. Signals decide whether an email is worth sending; cadence decides the limits it must respect.
Term
Cadence and sequence are the vocabulary of sales-engagement tools. Meeton uses them the same way, with the difference that each message is written for one person rather than templated.
| Setting | Meaning | Default |
|---|---|---|
| Max emails per contact | Maximum number of emails to send per lead. The limit resets if the lead re-engages after a period of inactivity. | 3 |
| Delay after lead | Hours to wait after a lead is created before sending the first email. | 24 h |
| Minimum delay between emails | Minimum hours to wait between emails to the same person. | 72 h |
| Pre-approval lead time | How many hours before the scheduled send time to generate the email and request approval. 0 auto-sends without approval. | 0 |
| Scheduled-ahead slot count | How many future email slots to pre-schedule per contact at a time. | 3 |
| Reset sequence after inactivity | If a contact returns to the website after this many days of inactivity since their last email, their sequence resets and they can receive the full series again. Blank never resets. | — |
| Skip holidays and weekends | The scheduling agent never places emails on weekends or Japanese public holidays. | on |
How scheduling works
- When a contact becomes eligible, Meeton pre-schedules up to the slot count, respecting the delay after lead, the minimum gap, and holidays.
- At the pre-approval lead time (or at send time when it is 0) the AI generates the draft for that slot from the contact's current context, so a draft written today reflects yesterday's visit.
- If a contact has a past-due email awaiting approval, scheduling stops for that contact until it is approved or deleted, so a queue never silently piles up.
- A reply or a booking ends the sequence; the contact's status explains why nothing more is sent.