Use the Lead Engine and email drafts

Open CRM → gear icon → Lead Engine. Enter the day values you want and save. The defaults are 14 days for first contact, 7 days each for reacting to materials, following up after a demo, reacting to a proposal, and form follow-up, and 2 days for a step of your own. These windows drive due dates; they don't send any emails themselves.

Enter signals and segment groups as comma-separated lists. Signals describe occasions for later work; the configuration doesn't monitor external events. You can choose segment groups on a lead and analyze them in the dashboard. Add packages with a name, price, and interval: one-time, weekly, every four weeks, monthly, or yearly. Enter the price in euros. Save the configuration.

Create a Knowledgebase article with reliable product information: value, scope, evidence, tone, and boundaries. Enter its slug under Product briefing; the default is product-briefing. Use the link next to it to open the article. The article must exist in the same organization and have content, so AI drafts can be generated.

Open the lead and its Lead Engine section. Field changes are saved individually.

1. Under Ball is with, choose whether you, the other side, or no one needs to act next.
2. Under Waiting on, choose the matching reason, for example reacting to a proposal or a step of your own.
3. For a promised reply or a fixed appointment, enter the promised/appointment date.
4. Set priority A, B, or C, and record the next step concretely.
5. Maintain the number of unanswered contact attempts with plus and minus, and check the computed category.

Normal reaction windows start from the last logged activity, or the creation date otherwise. Internal notes or stage changes can therefore shift the starting point too.

Promised reply

The entered promise date is the due date.

Fixed appointment

The due date is one day before the appointment.

Signal or parked

Leads that depend on a signal, or carry a parked signal, don't get a date-driven due date.

Overdue

An elapsed deadline counts as overdue if the ball is with us, or a promised reply is outstanding. An expired normal reaction window on the other side alone isn't enough for that.

Open Email drafts on a lead and start generation. This needs a filled-in product briefing and available AI budget. The app blocks generation for outbound leads with no documented basis for contact, and for contacts on the block list. Keep actual information on the lead up to date. Then check recipient, subject, text, prices, reasoning, and send condition; add anything missing and save your edits.

Direct sending uses a connected, send-capable Google or Outlook mailbox, or the organization's configured SMTP connection otherwise. A pure IMAP connection isn't enough for this. The Mark as sent action records a send that already happened elsewhere and doesn't send anything itself. You can discard drafts you don't need. Generation alone doesn't send anything.

For a draft, selected lead details, notes, up to 20 recent activities, the product briefing, and the configured packages are passed to the connected AI service. Use suitable content for this. Instructing the AI to use only these facts doesn't replace reviewing the finished text.