A website sales Agent for product questions and consented leads

• A visitor may know the outcome they want but not which product, plan, or variant fits.
• A generic chatbot has no reliable catalog, stock, policy, or eligibility context and can give a confident wrong answer.
• Lead capture is useful only when the seller defines qualification, consent, fields, destination, and follow-up ownership.

The seller owns the data and permissions. Prostir supplies the Agent, approved-tool boundary, publishing, and website delivery.

1. 01
   Define the sales job.

   Choose the questions the Agent may answer, what counts as a useful lead, and what it must not promise.

2. 02
   Connect seller-controlled product data.

   Configure and authorize a compatible connector, API, or custom catalog-search tool; this is not an assumed direct store integration.

3. 03
   Add approved sales knowledge.

   Provide current shipping, returns, warranty, eligibility, and escalation wording, with a safe response for missing data.

4. 04
   Configure CRM capture only if needed.

   Use a compatible connector or owner-provided CRM tool, account authentication, explicit fields, visitor consent, and a clear qualification rule.

5. 05
   Set up and test the website widget.

   Limit allowed origins, test representative and adversarial questions, and verify every external tool call in its owning system.

6. 06
   Publish after review.

   A configured Agent uses its persisted slug at the placeholder pattern https://{slug}.ai.prostir.build and /mcp; this pattern is not a live example, and embed instructions come from the published Agent.

These are illustrative resources and connections, not claims that a particular vendor integration is built in.

• linkcatalog connectionA seller-authorized connector, API, or custom tool that returns current product facts.
• codecrm-lead-actionAn optional owner-configured action with authentication, consent, qualification, and a bounded field list.
• docsales-answers.mdApproved answers for shipping, returns, warranty, eligibility, and what to do when data is missing.
• datawidget.configAllowed website origins, greeting, suggested questions, and presentation settings.

A configuration sketch, not a recording of a live deployment.

• In this example, the Agent compares products only from approved fields and says when current data is unavailable.
• If a visitor qualifies and consents, the optional CRM action can send the selected fields; the seller verifies that record in the CRM.
• The seller remains responsible for product accuracy, permissions, follow-up, failed calls, and measuring whether the Agent improves qualified conversations or sales.