Complete guide: what this setup creates
WebsDocs AI Sales Gateway creates a controlled, public, AI-readable business truth layer. It gives AI search
systems, buyer agents, partners, and visitors one approved place to understand the business, its services,
public offers, official routes, pricing rules, boundaries, and human handoff paths.
The ASG profile is not a private dashboard and it is not a replacement for the client website. It is the
hosted AI-facing layer that points automated visitors toward approved facts while keeping private systems,
customer records, credentials, payment data, and internal operations outside the public surface.
Before you start: public information only
Add only information the business is comfortable publishing. Never enter passwords, OTP codes, dashboard
access codes, payment records, bank details, private customer data, internal notes, API secrets, database
content, confidential contracts, or private staff information into public profile fields.
When a fact is uncertain, leave it blank or use safe wording such as “Contact for confirmation,”
“Availability requires review,” or “Final pricing is confirmed by the business.”
Plan limits and profile quality
Every ASG membership uses the same complete profile structure. The plan controls limits such as domains,
services, offers, FAQ entries, locations, languages, users, analytics history, and monthly AI answer credits.
Do not add filler just to reach a limit. Ten accurate services are better than thirty invented services.
Empty optional fields are acceptable when the business does not publicly provide that information.
1. Open the authorized setup link
Start from the official setup link issued by WebsDocs. The setup code may already be present in the URL.
Otherwise, paste it into the Setup Code field and click Load Setup Session.
One setup code should identify one client setup record. Do not reuse another client’s code, share it publicly,
or create a second workspace when the first setup is already active.
2. Confirm the locked identity anchors
Review the locked company name, website, authorized email, plan, payment mode, assigned slug, included
credits, and setup status returned by the server.
These fields are identity anchors. If the business name, domain, email, plan, or slug is wrong, stop and ask
WebsDocs admin to correct the setup record before continuing. Do not compensate by typing different details
later in the profile.
3. Verify email ownership
Click Send Validation OTP. The code is delivered to the authorized email address attached
to the setup. Enter the received code, confirm the company name, and confirm the website URL.
Use only the real code received by email. Never guess, auto-fill, forward, publish, or store OTP values in
screenshots or public documents. Expired codes should be replaced through the resend action.
4. Review plan, payment, trial, and activation status
The Plan section shows the assigned membership, payment mode, activation state, included monthly AI credits,
quote information where relevant, and the server-defined next action.
A trial is a payment mode, not a separate profile type. A Business trial becomes the same Business workspace
after successful payment. Manual-approved and direct-paid setups follow the server status shown here.
5. Activate the client workspace
After email verification and required activation, click Activate Client Workspace. This
creates or confirms the client slug, private dashboard, dashboard access code, hosted ASG Gateway URL, Pulse
URL, and credit wallet.
Workspace activation does not publish the public profile. The profile remains private until the server draft
is saved, reviewed, approved by final OTP, and successfully published.
6. Write the business identity
Add the public business name, legal name only when needed, official website, industry, timezone, supported
languages, short summary, and complete business description.
Use direct factual language. Explain what the business does, who it helps, how it delivers work, and what
makes its service relevant. Avoid unsupported awards, certifications, partnerships, market leadership claims,
guaranteed outcomes, or invented history.
7. Add approved domains and locations
Add only domains controlled or officially used by the business. Business plans normally use one domain;
Enterprise and Custom limits may allow more. Do not add social profiles or unrelated marketplaces as domains.
For a remote business, a location can be written as “Worldwide Remote Service” or a confirmed service region.
Do not invent a physical address. Add office addresses only when the business publicly operates from them.
8. Add public contact routes
Enter the approved public email, phone, WhatsApp, address, city, country, service area, and operating hours
where available. Leave private or uncertain contact fields blank.
The handoff email may be different from the public sales email, but both must belong to an authorized
business operator. Test links and addresses before publishing.
9. Add services the AI can explain
Each service should include a clear name, useful description, intended customer, delivery method where
relevant, and safe pricing note. Write it so a buyer agent can understand the service without decoding
internal jargon.
Separate genuinely different services. Do not split one service into many near-duplicates merely to fill the
plan allowance. Avoid promises such as guaranteed results, instant delivery, permanent uptime, or bug-free
performance unless the business formally supports them.
10. Add products, packages, or offers only when real
Use Products / Offers for public packages, subscriptions, products, plans, downloadable items, or structured
offers that the business currently provides.
Include a name, description, public starting price or pricing note, official product route, and availability
condition. Leave the section empty when the business sells only custom work. Never invent stock, discounts,
package contents, or checkout availability.
11. Define safe pricing rules
Tell ASG whether it may show fixed prices, starting prices, ranges, estimates, or contact-for-quote wording.
Explain what can change the final price: scope, quantity, location, urgency, customization, third-party costs,
taxes, delivery, support, or human review.
The AI must not create discounts, negotiate contract terms, promise refunds, confirm final totals, or bind
the business unless a deliberately connected workflow authorizes those actions.
12. Add official routes and buyer actions
Add the official contact, quote, booking, support, products, portfolio, payment, and checkout routes that the
business wants AI systems to use.
Routes must be complete HTTPS links and should point to controlled business pages. When checkout is not fully
connected, expose only checkout intent or a human-review route rather than pretending that payment can be
completed automatically.
13. Build the FAQ answer layer
FAQ entries provide fast, consistent, low-cost answers. Add real questions about services, eligibility,
delivery, service area, pricing method, revisions, support, required information, timelines, contact methods,
and human review.
Keep each answer self-contained and factual. Do not copy unrelated template text, expose private policies, or
write answers that conflict with service descriptions and pricing rules.
14. Write the public AI policy
Explain that ASG answers from approved public business facts. State that it may explain services, public
offers, routes, and policies, but it cannot access private dashboards, accounts, customer records, payment
systems, confidential documents, or admin tools.
The policy should also state that uncertain, sensitive, custom, urgent, or transaction-specific matters are
routed to a human.
15. Add blocked topics and prohibited answers
Block private data requests, credentials, payment records, database access, internal admin details, customer
information, security bypass instructions, guarantees, unsupported legal or financial conclusions, and any
topic outside the business’s approved public scope.
Write blocked topics specifically enough for the runtime to recognize them. “Do not reveal private customer
or admin data” is stronger than a vague instruction such as “be safe.”
16. Define human handoff rules
Add the handoff email, preferred contact route, urgency rule, and escalation reasons. Use handoff for custom
quotes, complaints, refunds, account issues, partnerships, legal questions, sensitive requests, urgent
matters, unsupported languages, and anything ASG cannot verify.
A strong gateway knows when to stop. It should not continue improvising after a request reaches a blocked or
uncertain area.
17. Review the ASG badge and website install pack
The install pack can include AI discovery meta tags, ASG badge HTML, robots.txt additions, an llms.txt
starter, company-profile JSON, agent-card links, Pulse routes, and public profile routes.
These elements point AI systems toward the hosted ASG truth layer. They do not grant access to the private
dashboard or expose setup credentials.
18. Save the official server draft
Click Save Draft or Save Profile Draft. The official profile draft is the
version stored by the ASG server and prepared for review.
Browser storage is only a convenience. It is not the authoritative publish record. Save again after important
edits and confirm the server reports success before moving to final approval.
19. Review every public field before approval
Check business identity, domains, locations, contact information, services, offers, pricing wording, routes,
FAQ answers, boundaries, blocked topics, handoff rules, and install snippets.
Ask: “Would the business be comfortable if a customer, search engine, AI assistant, competitor, or partner
read this exact text?” Edit anything unclear, private, exaggerated, outdated, or contradictory.
20. Send and verify the final publish OTP
Click Send Final OTP. The final code proves the authorized email owner approves the exact
public profile being prepared for publication.
Enter the code and type PUBLISH exactly where required. Do not publish after making
unreviewed changes; save and review the updated draft first.
21. Publish the ASG profile
Click Publish ASG Profile only after final approval. Wait for the confirmed server response.
Do not click repeatedly while publishing is in progress.
Successful publication creates or updates the hosted public profile, company JSON, routes, FAQ, Pulse signal,
discovery files, buyer-intent doors, and client-visible proof records allowed by the plan.
22. Confirm the dedicated Success page
After successful publishing, the browser should open the dedicated ASG profile-published Success page. That
page is the clean completion and handover destination, and it can be used as a Google Ads conversion goal.
The Success page must open only after the publish worker confirms success. It must not expose setup codes,
OTP values, dashboard access codes, private receipts, or raw database identifiers in the URL.
23. Save the handover links
Save the dashboard URL, public ASG Gateway URL, Pulse URL, public profile URL, company JSON route, agent card,
llms.txt route, and official client slug.
The dashboard access code is private. Share it only with the authorized operator and never place it in public
page markup, analytics parameters, screenshots, or support messages visible to others.
24. Open and verify the client dashboard
Unlock the dashboard with the authorized access details. Confirm the business name, membership, credit
balance, profile status, public links, activity areas, handoff records, and agreement state.
The dashboard is the management and proof surface. The public ASG profile should never expose dashboard-only
information.
25. Install discovery files on the client website
Add the provided head tags, footer badge, robots.txt lines, llms.txt content, and company-profile JSON where
the client controls the website.
Use the exact official routes generated for that client. Do not reuse WebsDocs demo links or another client’s
slug. Validate the website after installation to ensure the snippets do not break existing markup.
26. Verify every public ASG route
Open the hosted profile, Pulse, routes, company JSON, FAQ, agent card, llms.txt, and public ask endpoint.
Confirm that each route returns the correct business and no private fields.
Also check that official contact, quote, booking, support, product, and checkout links open the intended
client destination.
27. Test realistic AI buyer questions
Ask basic questions such as “What does this business do?”, “Which service fits my need?”, “How does pricing
work?”, “Where can I request a quote?”, and “When is human review required?”
Then test blocked requests. ASG should refuse or hand off questions involving private records, credentials,
unsupported guarantees, account-specific data, or sensitive decisions.
28. Understand static reads and AI credits
Static public discovery routes can normally be read without consuming live AI answer credits. Credits are
used when ASG performs live reasoning, deeper public answers, A2A responses, vector or RAG retrieval, or
buyer-intent routing that requires model work.
Keep FAQ and structured public facts complete so routine questions can be answered efficiently and
consistently.
29. Keep the profile accurate after launch
Update the profile when services, prices, contact routes, domains, locations, hours, policies, staff handoff,
or public offers change. Outdated public data weakens trust even when the original setup was correct.
Review high-impact changes before republishing, especially pricing, legal wording, checkout routes, handoff
recipients, and public claims.
30. Protect access and client security
Protect setup links, dashboard access codes, OTP values, agreement links, billing references, and admin
credentials. Use authorized email accounts and remove access when an operator is no longer responsible.
Report exposed links or suspicious activity to WebsDocs support. Public ASG routes can be shared; private
setup and dashboard credentials cannot.
31. Troubleshooting checklist
When a step fails, read the server status first. Check setup-code expiry, authorized email, OTP expiry,
payment or approval state, workspace activation, saved-draft status, final approval, network connectivity,
and whether the browser sent the request more than once.
Do not create duplicate workspaces to bypass an error. Preserve the first valid setup record and resolve the
actual server or admin issue.
32. Final completion checklist
Confirm: one valid client workspace, correct plan, verified email, accurate public identity, official
domains, approved contact routes, real services and offers, safe pricing, useful FAQ, clear blocked topics,
tested handoff, saved server draft, final OTP approval, successful publish response, dedicated Success page,
working public routes, dashboard access, and installed discovery signals.
A strong ASG profile answers public questions clearly, sends buyers to official routes, records useful
intent, and immediately hands uncertain, private, risky, or sensitive matters to a human.
