How to Deploy an AI Sales Agent on Your B2B Website: No-Code Setup | Storylane RepX

You already know what an AI sales agent is and why it works. If you need that background, our guide to AI agents for sales covers the definitions, agent types, and where they fit in the B2B funnel. This article skips all of that and gets you live.

What follows is a no-code deployment guide for a B2B marketing or growth professional who wants an AI sales agent running on their homepage and product pages this week, without involving engineering.

Pick the right tool before you touch a single setting

The tool decision locks in what you can configure and how fast you can iterate. Making the wrong call here means rebuilding from scratch later, so spend 30 minutes on this before anything else.

The core question is whether you need a general-purpose conversational builder (flexible but requires more configuration) or a purpose-built website sales agent (faster to deploy, narrower feature set). For most B2B marketing teams deploying on a website, purpose-built wins on time-to-value.

RepX is the tool this guide uses for the step-by-step, because it is designed specifically for the problem: qualify an inbound B2B visitor, deliver a live interactive demo inside the same conversation, route or book directly. If your stack is deeply Salesforce-centric or your primary use case is post-sale support, evaluate Qualified or Intercom first.

Choose Storylane RepX if:

• You want to deploy an AI sales agent on your website without engineering resources: RepX installs via a single script tag and is fully configurable from the UI.
• You need the agent to show interactive product demos as part of the qualification flow: RepX is the only tool in this category that launches a live Storylane demo inside the chat window, so prospects see the product before they book.
• You want out-of-the-box CRM integration and routing without custom dev: native HubSpot and Salesforce OAuth, round-robin assignment, and Slack hot-lead alerts are built in, not add-ons.

If you want a broader view of how agent categories compare (prospecting agents vs. qualification agents vs. demo agents), the AI agents for sales guide covers that decision tree.

What you need before you start

Gather these before you log into any tool. A blocked setup almost always comes from a missing input, not a missing feature.

• Website embed access: the ability to add a script tag to your site (Webflow, WordPress, HubSpot CMS, or similar). No engineer needed for most CMS platforms.
• A knowledge base document: a single Google Doc or PDF containing your product FAQ, pricing logic (even just "pricing starts at X"), core use cases, and the objections your reps hear most. Three to five pages is enough to start.
• Your ICP in writing: company size range, industries you target, job titles that matter, and one or two disqualifying signals (too small, wrong vertical, competitor employee).
• CRM access: HubSpot or Salesforce with permission to create contacts and deals, or at minimum to map fields. You need the API key or OAuth connection.
• A calendar link: a Calendly, Chili Piper, or equivalent link for the first rep who should receive booked meetings. One link is fine to start.
• One success metric: decide now whether you are optimizing for meetings booked, qualified leads captured, or demo engagement rate. Pick one for the first 30 days.

Step 1: Create your RepX agent and connect your knowledge base

Log into Storylane, navigate to RepX, and create a new agent. The first screen asks for a name (internal only) and the pages where the widget will appear. Start with two pages: your homepage and your primary product or pricing page. You can expand later.

Next, connect your knowledge base. RepX accepts URLs (it will crawl your site), uploaded documents (PDF or Google Doc link), and manual FAQ entries. For the first setup, use all three layers:

1. Crawl your website: paste your domain. RepX indexes public pages automatically. This takes 10 to 20 minutes.
2. Upload your knowledge doc: the FAQ and objection-handling document you prepared above. This grounds answers on content your reps actually use.
3. Add three to five manual FAQ entries for questions the crawler will not find: pricing ranges, contract terms, integration support, anything that lives in your reps' heads rather than your public site.

After the crawl completes, run the built-in test chat. Ask it your three hardest product questions. If it invents an answer, add a corrective FAQ entry. If it says "I don't know" where it should know, add that content to the knowledge doc and re-upload.

Step 2: Write your prompt configuration

The system prompt is what separates a generic AI chatbot from an agent that sounds like your brand and qualifies like your best SDR. RepX provides a prompt editor under Agent Settings. Write it in plain English; you do not need prompt engineering expertise.

Use this structure as your starting template and replace the bracketed fields:

Keep the total prompt under 400 words. Longer prompts cause the agent to forget its instructions mid-conversation. Test after every significant change with three to five sample conversations before saving.

Opening message template

The opening message is the first thing the visitor sees. It needs to be short, specific to the page, and not a generic "Hi, how can I help?" Write one per page type:

• Homepage: "Evaluating demo platforms? I can show you how Storylane works, answer questions, or help you figure out if we are a fit. What brings you here today?"
• Pricing page: "Questions about pricing or what is included in each plan? I can walk you through it or get you to the right person if you are ready to talk."
• Product page: "Want to see this in action? I can launch a live demo right now, or answer whatever you need first."

Each opening sets an expectation (this agent is useful, not obstructive) and invites a response without forcing a choice. Do not ask for an email address in the first message.

Step 3: Set your routing and qualification rules

Routing rules are where most teams underinvest, and it is the most direct lever on meetings booked. RepX lets you define routing logic in the Routing section of the agent editor without writing code.

Set up three routing paths at minimum:

Configure the "hot ICP fit" calendar link to point to the rep or round-robin you set up earlier. Set a fallback: if the visitor does not book in the chat window, the agent should capture their email and send the calendar link by email.

For a deeper treatment of how routing fits the broader inbound conversion strategy, including segment-aware routing for enterprise vs. small-market visitors, see the agentic inbound conversion playbook.

Step 4: Wire the CRM integration

Every qualified conversation that does not create a CRM record is a lead you will never follow up on. Set this up before you go live, not after.

In RepX, navigate to Integrations and connect HubSpot or Salesforce using OAuth (one click, no API keys required for these). Then configure field mapping:

1. Contact creation: map the visitor's name and email to Contact fields. Set the lead source to "RepX Website" so you can filter later.
2. Qualification data: map the company size and industry answers the agent collects to Contact or Company properties. If your CRM uses a lead score, set a RepX-qualified tag or score value.
3. Conversation notes: enable transcript sync. RepX can push a conversation summary to the Contact record as a note. This is the context a rep needs to not start cold.
4. Meeting records: if the visitor books, sync the meeting to the Contact record and assign it to the rep whose calendar was used.

For non-native integrations (Pipedrive, Close, Zoho), RepX connects via Zapier or Make. Create a Zap that triggers on "new RepX qualified lead" and creates a contact in your CRM with the field mapping above. Test the Zap with a real conversation before going live.

Set a Slack notification for hot-fit leads. In Integrations, add a Slack webhook that fires when a visitor reaches the "hot ICP fit" routing path. The notification should include name, email, company, and the first three messages of the transcript. Your reps will respond to this faster than to a CRM notification.

Step 5: Embed the widget and go live

Copy the RepX embed script from the Agent Settings page. It is a single script tag, typically four to six lines.

Paste it into the head or before the closing body tag of the pages you selected in Step 1. For common CMS platforms:

• Webflow: Site Settings, then Custom Code, then Head code. Paste the script and republish the site.
• WordPress: use a plugin like Insert Headers and Footers, or add directly to header.php if you have theme access.
• HubSpot CMS: Settings, then Website, then Pages, then Site Header HTML. Paste and save.
• Other platforms: add it to the global header template or use Google Tag Manager with a custom HTML tag firing on the specific page URLs.

After embedding, verify the widget appears within 60 seconds on a hard refresh. Open the browser console and look for any JavaScript errors. If the widget does not appear, check that the script is in the correct section and that no Content Security Policy on your site is blocking it.

Before declaring it live, run the full QA pass:

1. Have a colleague open the page cold and go through the conversation as a hot-fit visitor. Confirm the calendar booking works end to end and creates a CRM record.
2. Go through the conversation as a wrong-fit visitor. Confirm the agent declines gracefully without being dismissive.
3. Ask three questions the agent should not know (off-topic, irrelevant). Confirm it says it does not know and offers to connect a person, rather than inventing an answer.
4. Disconnect your calendar integration temporarily and confirm the agent captures the email anyway as a fallback.

Step 6: Measure the first 30 days

Decide before launch what "working" looks like. Tie your success metric to pipeline, not to conversation volume. Conversation volume measures activity; meetings booked and qualified leads measure value.

Review conversation transcripts weekly for the first month. You are looking for two things: questions the agent answers badly (add to the knowledge base), and qualifying questions that visitors dodge or misunderstand (rewrite the prompt section that triggers them).

Escalation rate is the metric to watch most closely in the first two weeks. If it is above 30%, the agent is under-trained and pushing work to humans it should handle. If it is below 5%, it is probably overreaching on questions it should escalate. Either extreme is a calibration issue, not a product issue.

At 30 days, pull the CRM data and look at the pipeline created from RepX-sourced leads. That is the number that determines whether you expand to more pages, increase the knowledge base depth, or adjust the routing thresholds.

Common setup mistakes and how to avoid them

• Overstuffing the knowledge base with contradictory content. Outdated blog posts and conflicting product docs cause the agent to give inconsistent answers. Audit before uploading. Prune first.
• Writing a vague ICP in the prompt. "Targets mid-market companies" is not actionable. "50 to 500 employees in SaaS, tech, or professional services, job title includes Marketing, Growth, or Sales" is what the agent needs to route correctly.
• Launching without testing the wrong-fit path. Most teams test the happy path and skip the out-of-ICP path. The wrong-fit response is what protects your brand when a poor-fit visitor hits the widget at 2 AM.
• Skipping CRM field mapping and treating the integration as a nice-to-have. If qualified leads do not land in the CRM with context, reps will not follow up and you will have no data to improve the agent.
• Measuring success at 7 days. A new agent needs at least two weeks of data before routing patterns stabilize. Evaluate at 30 days with a real conversation count, not impressions.

What to build next

Once the homepage and product page agents are stable and creating pipeline, expand in this order:

1. Add the pricing page with a variant of the prompt that specifically handles pricing questions and competitive comparisons. This is your highest-intent page and usually the biggest lift.
2. Add a demo-specific agent that launches the interactive demo immediately rather than asking qualifying questions first. Some visitors just want to see the product. Let them.
3. Segment by firmographic data. If you use a visitor identification tool (Clearbit, Demandbase, or similar), feed that data into RepX so the agent personalizes the opening message based on the visitor's company before they type a single word.
4. Expand to email follow-up. RepX can trigger a follow-up email sequence when a visitor engages but does not book. Set this up only after the chat experience is stable.

For the broader implementation strategy, including multi-phase rollout, guardrails, and production deployment discipline, the 10-phase AI agent implementation guide covers the enterprise-grade version of each of these decisions.

FAQ

How long does it take to deploy RepX without an engineer?

A focused marketing or growth person can go from sign-up to a live widget in one to three days. Day one is knowledge base setup and prompt configuration. Day two is CRM wiring and QA. Day three is embed and go-live. The constraint is usually getting the knowledge base document together, not the tool itself.

What CRM platforms does RepX connect to natively?

RepX has native OAuth integrations for HubSpot and Salesforce. For other CRMs, use the Zapier or Make connector, which covers Pipedrive, Close, Zoho, and most others with a standard contact creation flow.

Can I run RepX on a gated landing page, not just my main site?

Yes. The embed script works on any page where you can add a script tag. If your landing pages are on a separate subdomain, you will need to add the embed there separately and configure the agent in RepX to show only on those URLs.

What happens if a visitor asks something the agent does not know?

If you have configured the knowledge constraint in the system prompt correctly, the agent will say it does not know and offer to connect the visitor with a person or capture their email for follow-up. It should never invent an answer. Test this explicitly during QA by asking three questions outside the scope of your knowledge base.

How do I keep the agent on-brand?

The tone instructions in the system prompt are the primary control. After that, read 10 real transcripts a week for the first month. The places where the agent sounds off-brand are the places to add explicit rules or rewrite the tone section of the prompt.

For a real-world look at why teams choose Storylane RepX over alternatives, see why teams choose Storylane and how the conversation compares to traditional rep-led demos in AI sales agents vs. human reps: how buyers actually respond.

Ready to see RepX in action before you set it up? Launch a live demo on the RepX page and watch the agent qualify and book in a single conversation.