Drip campaigns

NetHunt runs email drip sequences from inside Gmail. A Beam agent watches for a contact entering a stage or list a customer defined, reads the enrollment rule that customer approved, and adds or pauses that contact in the right sequence. It writes the enrollment status onto the record and notes which step last fired. When a reply reads as an objection, a bounce, or anything the rule cannot classify, the agent halts the sequence and hands the thread to a sales rep with the message quoted for context. Clean opt-outs and normal step progressions stay automatic.

Contact records

Every NetHunt contact lives beside the Gmail thread it belongs to. An agent opens the record tied to an incoming email, reads fields like company, owner, and last activity, and applies the update rule the team approved, for example setting a lead source or tagging an industry. Changed values are written back to the same record so the next reply has current context. If two records look like the same person, or a field conflicts with what the email says, the agent leaves the data untouched and asks a human to resolve the duplicate before anything is saved.

Pipeline stages

NetHunt follows deals through pipeline stages a team configures. An agent reads signals on a record, a scheduled call completed or a proposal opened, and moves the deal to the next stage only when the approved criteria are met. It updates the stage, the close date estimate, and any owner field, then notes the reason in the record history. Deals that skip expected steps, stall past a threshold, or carry mismatched amounts are flagged to the deal owner instead of advanced, so a person decides whether the move is real.