Skip to main content

Send a One-Time Email from Lists

Learn how to send a personalized, one-time email to any contact directly from your Lists view.

Marine Melamed avatar
Written by Marine Melamed
Updated this week

Overview

The One-Time Email from Lists feature allows you to send personalized, one-off emails to prospects directly from the Lists view, without needing to set up a sequence. With the added power of AI, you can quickly draft tailored emails, making your outreach faster, easier, and more effective.

It’s ideal for initial engagements, ad hoc follow-ups, personalized touches, or quick outreach actions that don’t require automation.


Step-by-step instructions

1. Connect your mailbox: Before sending an email, ensure your mailbox is connected to Lusha.

2. Navigate to your List: Go to the Lists section in Lusha and open the list containing your target contact(s).

3. Select a contact: From the list view or the contact's side panel, click the Email icon to start composing a message.

4. Craft your email: The email composer will open.

Here you can:

  • Add a Subject Line that reflects your outreach goal

  • Edit the Email Body to personalize your message

  • Ensure the content is tailored and aligned with your objective

5. Use AI to speed things up (recommended):

For faster, high-quality outreach:

  • Click Help me write with AI or the AI icon to generate a personalized draft using Lusha data.

The AI will suggest a relevant, personalized email draft based on Lusha’s data

  • You can choose to insert the draft as-is into the email body or click Regenerate to get a new version (up to 3 times)

  • Once inserted, you can further edit and personalize the message to match your voice and intent

6. Send your email: Once you're happy with the message, click Send.

You’ll receive a confirmation if the email is sent successfully—or an error message if it fails.

💡 Note: Emails sent this way will appear in your Gmail or Outlook Sent folder.

To monitor replies, make sure to check your inbox directly—responses from prospects will arrive in your personal email inbox, not within the Lusha platform.


How One-Time Emails Affect Your Sending Limits

Engage applies sending limits (both daily and hourly) to each connected mailbox to manage email volume for automated outreach (i.e., sequence emails) and help maintain high deliverability.

While manual emails are not queued like automated sequence emails and can be sent instantly, they still count toward your daily and hourly sending limits used to regulate sequence email delivery. This means that even though sending manual emails is not blocked by the limits, sending them can reduce the number of automated sequence emails that are allowed to go out within the same period.

Example 1: Hourly Limit

  • A user’s sending limit is set to 6 emails/hour.

  • Engage Sequence schedules 6 sequence emails to be sent between 10:30 AM and 11:00 AM.

  • The user sends 2 manual emails at 10:15 AM.

  • Engage adds these 2 manual emails to the hourly sending counter.

  • When the system checks before sending the scheduled emails, only 4 of the 6 sequence emails can be sent this hour.

  • The remaining 2 sequence emails are rescheduled to the next available hour.

Example 2: Daily Limit

  • A user’s sending limit is set to 50 emails/day.

  • They have already sent 45 emails today.

  • There are 5 more sequence emails scheduled to be sent today.

  • Meanwhile, the user sends 5 manual emails, reaching the daily limit of 50.

  • Engage checks the total before sending sequence emails and detects that the limit has been reached.

  • As a result, the 5 scheduled sequence emails are rescheduled for the next available day, based on the user’s sequence settings.

💡 Notes: One-time emails aren’t blocked by Engage limits, but they do affect the counters used for automated sequences.

Be mindful of your manual sends to avoid:

  • Delaying sequence emails, which may be rescheduled due to reaching limits.

  • Excessive email volume from their mailbox, which could impact deliverability.

Did this answer your question?