01
Overview
Widgo is designed to go live quickly, but a fast install is not the same thing as a good sales setup. The useful workflow is to treat the first deployment as a controlled experiment: give the agent clean source material, define who counts as qualified, connect only the systems it needs, then inspect real conversations before expanding it across the site.
02
1. Create the workspace and let Widgo scan the site
Widgo’s current onboarding starts with a company website. The product scans the site and drafts a knowledge base from the content it finds. The company says setup can be completed in minutes and that installation ultimately requires adding a single script to the site.
Before accepting the generated knowledge base, review it. Pricing pages, outdated docs, legal disclaimers and old product pages can all create bad answers if they remain in the source set.
03
2. Add approved knowledge sources
Widgo can use the website plus additional material such as documentation pages, help-center content and PDFs. The product is positioned around source-grounded answers: it should respond from approved material and surface the source behind a response.
A good initial source set is narrower rather than broader. Start with current pricing, product documentation, security/compliance FAQs, onboarding material and the specific pages prospects regularly ask about.
Avoid uploading internal material that the visitor should never see. A retrieval system can only be as safe as the source boundaries you give it.
04
3. Test unsupported questions
Widgo’s makers say the agent should admit when it does not know something rather than invent an answer, then hand the conversation to a human.
Test this explicitly before launch. Ask about nonexistent features, unsupported integrations, made-up prices and edge-case legal/security questions. Confirm that the response is cautious and that the handoff carries the conversation context.
05
4. Define qualification criteria
Widgo scores visitors from 0 to 100 based on fit and intent. The score is only useful if the team has a clear definition of a qualified lead.
Define attributes such as company type, company size, geography, budget fit, use case, urgency and decision-maker status. Also define disqualifiers. Widgo’s makers have said the product is intended to back off rather than push a meeting when the visitor is clearly not a fit.
Review early lead-score explanations manually. A 90/100 score that sales would reject is more useful feedback than a high conversion count because it tells you the qualification logic needs work.
06
5. Connect the calendar
Widgo can offer real calendar slots inside the chat and book a meeting without sending the visitor to another page.
For the first test, connect a calendar with limited availability rather than the entire sales team. Confirm timezone behavior, buffer rules, invite details and what happens if two people try to book the same slot.
The goal is to make the booking experience easier without creating calendar chaos.
07
6. Connect the CRM and notifications
Widgo’s site currently lists HubSpot, Attio and Close CRM support, along with Slack and Microsoft Teams notifications.
Start with one CRM and one internal alert channel. Check that the record contains the information your sales team actually needs: visitor/company context, lead score, reason, transcript, booked time and source page.
Do not assume every integration field is mapped the way your existing pipeline expects. Test duplicate handling and whether an existing contact is updated or a new record is created.
08
7. Install the website script
Widgo describes installation as one line of code. In practice, teams should still control where it loads and verify performance impact.
Use a tag manager or site integration method that can be rolled back quickly. Test desktop and mobile behavior, consent/cookie interactions, content-security-policy compatibility and whether the widget affects Core Web Vitals.
Around launch week, users specifically asked for better page-level allow/block rules. If you only want the agent on /pricing, /enterprise or high-intent solution pages, verify whether those controls are available in the current dashboard. Otherwise implement page-path logic in your own tag manager or site code.
09
8. Launch on high-intent pages first
Do not put a sales agent everywhere on day one. Start where visitor intent is already commercial: pricing, enterprise, product, integrations and comparison pages.
Keep it off documentation or editorial pages if the widget would distract from the user’s job. This also gives cleaner early data because you are testing against visitors who are more likely to have buying questions.
10
9. Review conversations and unanswered questions
Widgo logs conversations and, according to its makers, unanswered questions can expose gaps in the website itself.
Review the first 50–100 sessions. Look for incorrect answers, weak qualification, repeated objections, common integration questions and visitors who should have been handed to a human sooner.
Use those findings to improve both the knowledge base and the website copy. If ten prospects ask the same security question, the website probably needs that answer in a visible place.
11
10. Measure the right outcomes
Do not evaluate Widgo only by the number of chats. Track qualified meetings, show rate, sales acceptance, opportunity creation and revenue influence. Also track bad outcomes: false-positive qualification, duplicate CRM records, inaccurate answers and unnecessary human escalations.
Widgo’s own website includes marketing claims about conversion and response speed, but those are not independent benchmarks. Your own funnel is the useful benchmark.
12
Free-plan testing
Widgo’s terms say the free plan is metered by unique visitors per calendar month, with bots/crawlers it identifies excluded. Its public pages describe 500 visitors per month on Free.
The terms also say that when the allowance is exceeded the widget can continue answering, while conversations/leads beyond the limit may appear blurred in the dashboard until reset or upgrade. Staging/test installations count toward usage.
That makes it worth keeping QA traffic controlled during setup.
13
Safety and regulated-use caveat
The free plan is not intended for sites directed at children or for regulated medical, legal, financial or insurance advice where answers could affect health, safety, legal rights or finances.
If your business is regulated, confirm the paid-plan contract, data-processing terms and any required BAA/DPA before deployment.
14
A practical launch checklist
Before expanding site-wide, confirm: approved source set is current; hallucination/unknown-answer tests pass; qualification rules match sales judgment; calendar booking works across timezones; CRM mappings do not create duplicates; Slack/Teams alerts are actionable; page placement is intentional; consent/security controls are compatible; and early transcripts have been manually reviewed.
Widgo is easiest to understand as a sales workflow, not a widget. The script is the last step. The real setup is defining what the agent is allowed to know, who it should qualify, and what should happen when a visitor is ready to buy.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.