SBuild the Asset
RB2B Visitor Outbound
Identified site visitors get page-specific copy based on where they landed. Map once, runs forever.
RB2BCommon RoomClay
When RB2B identifies a company on the site, the workflow doesn't send generic “saw you on our website” copy. It branches on which page they landed on — pricing, a product page, a blog post, a lead magnet — and enrolls them into the sequence written for that page. You map page to copy once; after that it runs forever. Adding a new page later is just another mapping, and optimizing copy is editing the standing play, not rebuilding the trigger.
The same pattern extends to heavy repeat traffic: when an account keeps coming back, the workflow finds the senior-most marketing leaders at that company, enriches phone numbers, and drops them into a stakeholder sequence — visit intent becomes named people in outreach, without waiting for a form fill.
Site visits stop being a vague intent badge in the CRM and become evergreen, page-aware outbound. Reps inherit ready enrollments instead of research tickets, and marketing can ship a new page and plug it into the map without asking anyone to rebuild the workflow.
No diagram code provided
Goes deeper
Running the Seat — visitor outboundSAlso in this stage