Automated Profile Visits

Dux Soup can visit LinkedIn profiles on a prospect list automatically, which itself often prompts LinkedIn to notify that person someone viewed their profile. A Beam agent starts a visit run against a list a team has approved, matching a segment definition such as job title or industry, and notes which profiles were visited and when. This surfaces a company to prospects without a rep opening each profile one at a time. Profiles belonging to people who already replied, who asked not to be contacted, or who sit outside the daily visit limit LinkedIn allows, are skipped rather than visited.

Connection Request Campaigns

A campaign in Dux Soup sends a connection request with a note to each profile on a list, following a schedule set to stay within LinkedIn's limits. A Beam agent adds a prospect to the campaign once it matches criteria a team has approved, such as a title or company size from a lead list, and reports back which requests went out and which were accepted. This keeps outreach steady without a rep clicking connect one profile at a time. Prospects who decline, report the account, or belong to an excluded company are pulled from the campaign instead of getting a follow up request.

Prospect Tagging and Follow-up Sequences

Once a prospect accepts a connection or replies to a message, Dux Soup can apply a tag and move that profile into a follow up sequence, such as a scheduled message a few days later. A Beam agent reads the tag Dux Soup applied, checks it against a team's approved sequence rules, and queues the corresponding follow up message for that prospect. This keeps a reply from sitting untouched while a rep works through other accounts. Replies that mention pricing, a complaint, or a request to stop contact are pulled out of any sequence and handed to a rep to answer directly.