Knowledge CenterAPI References

Configuring communication steps

How to configure Email, LinkedIn, and WhatsApp message steps in Dalil sequences — timing, senders, personalisation, and rate limits.

Updated April 25, 20263 min read

Communication steps are the actions that send messages to contacts across Email, LinkedIn, and WhatsApp. Well-configured steps increase deliverability, improve engagement through personalisation, and scale intelligently within rate limits.

Message timing

Every step can be configured to send:

  • Immediately after the previous step completes
  • Wait X minutes/hours/days (optionally restricted to business days only)

Send windows respect the global Scheduled Send Window (default: 9 AM–6 PM, Monday–Friday, in the contact's timezone).

Sender configuration

Email senders: Select team members whose accounts can send. The system prioritises the contact's assigned Owner; otherwise distributes randomly among selected senders.

LinkedIn senders: Only users with connected LinkedIn accounts can send messages or connection requests.

WhatsApp senders: Pro plan users with connected WhatsApp numbers. Uses the same Owner-first priority logic as email.

Personalisation with merge tags

Merge tags pull contact data into messages:

TagExample output
{{first_name}}Sarah
{{last_name}}Chen
{{company_name}}Acme Corp
{{title}}VP of Sales
{{owner}}James (the assigned rep)
{{custom_field}}Any custom field value

Personalised messages achieve 3–5× higher open rates compared to generic versions.

Send Email step

  1. Add Send Email step in the sequence Editor
  2. Select a template or compose a custom email
  3. Write the subject line (40–60 characters; avoid spam triggers)
  4. Compose the body with merge tags
  5. Configure timing
  6. Select senders (minimum one required)
  7. Configure rate limits (default: 50 emails/24h per sender)

Best practices:

  • Include the contact's first name in the subject
  • Use a personalised hook referencing the company or recent news
  • Keep paragraphs to 2–3 sentences
  • Include a single, clear call-to-action
  • Avoid generic openers like "I hope this finds you well"

LinkedIn Message step

Prerequisite: Recipients must be existing LinkedIn connections. The sender must have a connected LinkedIn account.

  1. Add LinkedIn Message step
  2. Compose plain text (300–500 characters recommended)
  3. Use line breaks for readability
  4. Configure timing (typically 2+ days after email)
  5. Select senders
  6. Respect rate limits (30 messages/24h default)

Best practices:

  • Avoid URLs — they reduce acceptance rates
  • Open with a personalised hook
  • End with a soft call-to-action
  • Keep it concise

LinkedIn Connection Request step

  1. Add LinkedIn Connection step
  2. Compose an optional personalised note (max 300 characters)
  3. Configure timing
  4. Select senders
💡

Personalised connection notes increase acceptance rates to 40–50% vs. 15–20% without a note.

WhatsApp Message step

Prerequisites:

  • Contact must have a phone number in CRM in international format (+country code)
  • Contact must have WhatsApp installed
  1. Add WhatsApp Message step
  2. Compose plain text (1,600 character limit)
  3. Include one clear call-to-action
  4. Configure timing (typically late in a sequence)
  5. Select WhatsApp account/number
  6. Respect rate limits (20 messages/24h)

Best practices:

  • Lead with value or curiosity
  • Keep it personal and brief
  • Use emojis sparingly
  • Avoid links if possible

LinkedIn Profile Visit step

A non-message action that visits the contact's LinkedIn profile to create a notification on their end. Configure timing (typically before messaging) and select the sender account.

Rate limits summary

ChannelDefault limit
Email50 sends/24h per sender
LinkedIn messages30 messages/24h per sender
LinkedIn connections20 requests/24h per sender
WhatsApp20 messages/24h per sender

Dalil enforces these limits automatically to protect your accounts from restrictions.

← PREVIOUSDesigning Flow with Conditions
NEXT →Using Personalization & Messaging

Was this article helpful?

Your feedback helps us improve our documentation.