> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/pulse/setting-up-a-pulse-sequence.md). # Setting Up a Pulse Sequence Pulse sequences let you automatically follow up with leads after an event — triggered by a scan, a qualifier value, or a lead score. This guide walks you through creating and activating a sequence. *** ## Before You Start * **Pulse is a paid add-on.** If you don't see **Pulse** in the Hub left nav, contact your CSM to discuss enabling it for your org. (If you're already a Pulse beta user, the same Hub nav rules apply — just confirm the feature is turned on for your account.) * You'll work in the Hub — Pulse isn't available from the mobile app. * If you want to send emails, the sender's email address must be verified — see [Verifying your sender address](#verifying-your-sender-address) below. * If you want to trigger on Lead Score, set up your scoring configuration first. *** ## Step 1: Create a New Sequence 1. In the Mobly Hub, go to **Pulse** in the left navigation 2. Click **New Sequence** 3. Give your sequence a name — something that makes it easy to identify later (e.g., "Post-Scan Intro — Q3 Events") 4. Click **Create** This opens the sequence editor. *** ## Step 2: Set Your Trigger The trigger defines who gets enrolled. Click **Add Trigger** and choose one: Trigger When it fires **Scanned** Any lead scanned at the linked event **Qualifier applied** When a specific qualifier value is applied to a lead **Lead Score** When a lead's score reaches a category (Hot, Nurture, Caution, Cold) You can add multiple triggers. A lead only enrolls once per sequence regardless of how many triggers they match. > **Tip:** "Scanned" is the most common trigger for event follow-up. Use Qualifier applied or Lead Score triggers to create more targeted sequences — for example, a separate nurture track that only goes to leads with the "Interested" qualifier value. *** ## Step 3: Build Your Steps Each step is a message sent to the lead. Click **Add Step** to add your first one. ### Choose a channel * **Email** — requires a subject, body, and sender configuration ### Set the timing * **Right away** — sends immediately after the previous step (or at enrollment for step 1) * **After a delay** — set a number of minutes, hours, or days to wait * **On a specific date** — pick a date and time; optionally set an end date after which the step is skipped if the lead hasn't reached it yet ### Write the content **For email steps:** * **Subject** — the email subject line **Body** — the email body. Use the rich text editor to format, add links, or insert merge fields (lead name, company, etc.) **Sender** — choose who the email appears to come from: * *Lead owner* — the rep the lead is assigned to in Mobly * *Account owner* — the owner of the lead's associated company * *Specific person* — a fixed name and email you enter ### Use AI to write or improve content Click **AI Generate** to have Mobly draft email copy based on your event context. You can also open the **AI Assistant** chat to refine existing content — ask it to rewrite, shorten, adjust tone, or add a CTA. > **Note:** AI-generated content is a starting point. Review it before saving — especially make sure it doesn't reference internal scoring categories (like "Hot lead") in customer-facing copy. ### Add more steps Repeat for each follow-up in your sequence. A typical post-event sequence might look like: 1. **Step 1** — Email, right away — quick intro / thank you for stopping by 2. **Step 2** — Email, after 2 days — follow-up with a resource or demo link 3. **Step 3** — Email, after 5 days — short nudge if no reply *** ## Step 4: Connect to an Event Sequences don't run on their own — they need to be linked to an event. 1. Go to the event in the hub 2. Open the **Sequences tab** 3. Find your sequence and activate it for this event Once active, leads scanned at that event (or matching your other triggers) will start enrolling automatically. *** ## Step 5: Verifying your sender address Pulse emails go out from a real person's email address — typically the lead's owner — so leads get follow-up from someone they actually recognize. To send from a real address, that person has to prove they own it. Here's what happens: 1. The first time someone is configured as a sender in Pulse, Mobly triggers a verification flow automatically (when the user is added to the event). 2. **They'll receive an email from MailerSend** — Mobly's email delivery provider — asking them to confirm permission to send on their behalf. 3. They click the link in that email to approve. After approval, Pulse can send emails as that user. Until they approve, sequences using that sender are blocked. > **Why MailerSend?** Mobly uses MailerSend as the email-sending infrastructure behind the scenes. We can't fully hide the brand name on the verification email because the customer is granting MailerSend permission to send on their behalf. After approval is granted, the actual emails to leads go out from the user's own address — recipients don't see MailerSend in the From line. If a sender doesn't approve the verification email, the team-lead heads-up is: their sequences won't send until they do. Worth flagging this to your team during onboarding. *** ## Managing Active Sequences ### Pause, edit, or cancel A live sequence can be paused, edited, or canceled at any time. See [Pausing, editing, or canceling a sequence](/help-center/pulse/how-to-pause-or-cancel-a-sequence.md) for the full mechanics — especially if you need to stop a sequence that's already sending. ### Clone a sequence Use the clone option to duplicate a sequence for a new event. Update the name and any event-specific content before activating. ### View performance The Pulse dashboard shows: * **Total Emails Sent** * **Open Rate** * **Click Rate** * **Reply Rate** * **Spam Complaints** * **Activity over time** — email volume vs. bounces by month * **Funnel Conversion** — how many leads moved from sent → opened → clicked → replied *** ## Troubleshooting **Leads aren't enrolling** * Confirm the sequence is linked to the event and the trigger is set correctly * Check that the sequence is not paused **Emails aren't sending** * Check that the sender has completed MailerSend verification * Confirm the sequence is active (not paused) **A lead received a duplicate email** * This shouldn't happen — Mobly deduplicates enrollments. If it did, contact support. **Email shows the wrong sender name** * Check the "Sender" setting on the step — confirm it's set to Lead Owner, Account Owner, or the specific person you intended --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/pulse/setting-up-a-pulse-sequence.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.