ARTICLE · Delhi NCR

Workflow Teardown: A Make + SalesRobot Lead-Follow-Up Sequence

A practical reference design for turning new enquiries and LinkedIn conversations into a consent-aware, human-reviewed follow-up rhythm using Make, SalesRobot, and CRM context.

The short answer: this is a reference workflow for service businesses that want leads to receive timely, relevant follow-up without losing human judgment. It is not a client-results claim or a plug-and-play outreach promise.

The situation: a coach, consultant, trainer, or service-business owner often receives interest from more than one place—an enquiry form, a LinkedIn conversation, a referral, or a discovery call. The lead context then lives across messages, notes, and memory. Follow-up becomes uneven because no one can see the whole hand-off.

The bottleneck: the first reply may happen, but the next useful action is not clear. A lead who asks a specific question can receive a generic follow-up. A team member may not know which conversation already happened. A qualified person can wait because a manual reminder was missed.

The operating design: Make receives an approved lead event, normalises source and contact data, records the current stage, and creates the next owner task. SalesRobot is used only inside an approved LinkedIn outreach or response sequence, with message rules that fit the relationship and platform policy. The CRM remains the context record, not an afterthought.

Stage one is capture. A form, referral, or approved LinkedIn response creates a lead record with source, consent status, stated need, and the correct owner. Leads without usable consent or context do not enter automated outreach.

Stage two is classification. Make checks simple routing criteria such as business type, topic, requested service, and conversation stage. It can attach a relevant field note or booking invitation, but it does not decide whether a person is qualified without a human-defined rule.

Stage three is the LinkedIn or email follow-up. SalesRobot can support the approved action sequence while Make records the message stage and timing. The point is not more messages; it is a more coherent next message. Every sequence needs frequency limits, a stop condition, and an escalation rule when a person replies.

Stage four is the human hand-off. A reply, booking signal, objection, or high-value enquiry creates a task with the conversation context attached. The owner reviews what was sent, the original need, and the next best action before the relationship moves forward.

What stays human: offer fit, pricing, nuanced replies, client confidence, and the decision to continue or stop a conversation. Automation should make those decisions easier to make well; it should not impersonate judgment.

Who this is useful for: coaches, consultants, trainers, and service businesses with recurring lead conversations but inconsistent follow-up. It is not suited to teams that have no clear consent policy, no agreed service offer, or no owner for reply handling.

The practical question to ask is not whether Make or SalesRobot can send the next action. It is whether your prospect receives the right context, at the right time, from the right person. That is the operating rhythm worth designing.