How can we help you?

Sales Sequences and Speed To Lead (Revenue Suite)

What It Is

Revenue Suite adds two things to Velaro Messaging (V27) for sales teams: sales sequences, automated follow-up for new leads and prospects, and speed to lead, which makes sure a human reaches every new lead quickly. It is a package. Whether an account has it depends on the plan: tell the admin to see their plan under Billing, Usage Overview. Never quote a price or a limit.

If the account does not have it, say which package is missing (Revenue Suite) and offer the safe fallback: build a normal email campaign with email and text steps.

Sales Sequences

A sales sequence is a campaign that mixes emails and texts with rep actions. The action steps are:

  • Create CRM task: a task, call or meeting on the owner's list, linked to the contact.
  • Assign owner (round robin): the next rep from a team or skill group, in turn. The same rep is kept for the rest of the sequence.
  • Notify the rep: desktop and mobile alert, plus Teams or Slack when connected.
  • Call me now: rings the reps and connects the first one to the lead, using the existing click-to-call setup.
  • Book a meeting: offers the scheduler link to later email and text steps, or books the first open slot.
  • Create deal and Move deal to a stage: open one deal per contact and move it forward only. These need deal automation, also part of Revenue Suite.

Four starter sequences install in one step: Inbound lead follow-up, Outbound prospect outreach, Demo no-show recovery and Quote follow-up. Installing is safe to repeat (same name, same sequence, no duplicate). Reset replaces the steps after saving a snapshot to the audit trail. Starters are installed turned off so the admin can read and edit the messages first. The ones with a booking step ask for the admin's scheduler link, which must be a full https link.

Every starter stops by itself when the contact replies, books a meeting or unsubscribes.

An admin can enroll one contact by hand: pick the sequence and give an email address. Repeating it enrolls once. A sequence that is turned off cannot take contacts.

Speed To Lead

A speed to lead rule covers new leads (all sources unless the admin narrows it) and runs this loop:

1. The lead arrives and a timed lead starts, one per rule and contact.

2. The next rep is picked in turn from the rule's team or skill group and alerted (desktop, mobile, Teams, Slack).

3. A first touch (email, text, completed task, a call a person answered inbound or outbound, or a connected click-to-call) stops the clock and is recorded.

4. If no one reaches out within the escalate time, the lead moves to the next rep, up to the rule's number of escalations.

5. After the last escalation the lead is marked breached and the team is told it is still waiting.

A lead with only a phone number also starts speed to lead (timed and alerted, not enrolled in email sequences). A number on the do-not-contact list never starts a timer.

A rule can also enroll the lead in a sales sequence at the same moment. It needs a team of reps: with one rep there is nobody to escalate to.

The time to first touch report shows leads arrived, touched, pending and breached, the share touched within target, the typical time to first touch and each rep's typical response time. A paged list shows each lead with its owner, escalations, first touch and status (pending, touched, breached).

Native CRM and external CRMs

Tasks and deals can be created in the Velaro CRM or HubSpot (the step has a CRM choice). HubSpot uses the existing HubSpot connection and the contact must already exist in HubSpot. Salesforce, Dynamics, NetSuite, Pipedrive and Monday are not supported yet: a step that picks one is refused with the reason. Say this plainly if an admin asks.

Setup From A Goal

An admin can describe the goal in words. For setup requests use the sales_setup_from_goal skill; for how-fast questions use speed_to_lead_report. Saving from a goal creates a proposal under Automation Drafts. Always call the result a proposal, never live: nothing is created, enrolled or sent until a person approves it.

Common Questions

Why did my sequence stop? The contact replied, booked a meeting or unsubscribed. That is by design.

Why did a lead not start a timer? The rule may be off, its trigger or source may not match, the lead may be below the rule's minimum score, or the same contact already has a timed lead for that rule.

Why did no one get the alert? Check that the rule has a team with reps in it and that the notify channels include a place the rep looks. Teams and Slack alerts also need the new lead alert turned on in those notification settings.

Where do I see how fast my team responds? The time to first touch report. Moshky can read the speed to lead summary for the admin's own account when asked.

Can I do this from the command line or an AI assistant? Yes. The Velaro command line has velaro sales (status, step-types, templates, template-install, enroll, rules, rule-upsert, rule-delete, report, leads) and the Velaro MCP tools cover the same actions. They always act on the signed-in account.

Share: Email

Was this article helpful?