2. What it is
Widget Installation is the deployment layer for publishing your configured assistant on website surfaces with framework-specific embed options.
Widget Installation
Deploy your assistant where customers already ask for help
Install the widget with your workspace key, choose your framework path, and roll out with quality controls.
Standard embed script
Install the Receiveo widget by adding your workspace public key and a lightweight loader script before the closing body tag. The embed works with any website architecture, whether static HTML, server-rendered, or single-page apps. No build step is required, so you can go live in minutes.
Simple script-based install
Copy a single script snippet into your HTML and the widget loads automatically on every page where it is included.
Workspace-specific public key
Each workspace gets a unique public key that connects the widget to the correct assistant, knowledge base, and configuration.
Works with static and server-rendered sites
The loader script is framework-agnostic, so it runs correctly on static sites, SSR pages, and traditional server-rendered applications.
Framework-specific guides
For teams using modern frameworks, Receiveo provides tailored installation guides that follow each platform's best practices. Whether you use Next.js script strategies, WordPress plugin patterns, or Google Tag Manager custom HTML tags, there is a documented path to production. Each guide covers the recommended approach and common gotchas.
Next.js script strategy examples
Use the Next.js Script component with the correct loading strategy to ensure the widget initializes without blocking page rendering.
WordPress install paths
Add the widget through your theme's footer template or a lightweight plugin, keeping the installation clean and update-safe.
GTM custom HTML tag flow
Deploy the widget via Google Tag Manager using a custom HTML tag triggered on all pages, ideal for teams that manage scripts centrally.
Operational rollout control
Before going live across your entire site, validate that your assistant behaves correctly and your knowledge base covers the topics visitors will ask about. Receiveo supports staged rollout so you can deploy to a single page or section first, monitor results, and expand coverage with confidence once quality meets your standards.
Assistant behavior pre-checks
Test your assistant's tone, accuracy, and escalation behavior in a controlled environment before exposing it to production traffic.
Knowledge source readiness review
Verify that synced documentation and crawled pages cover the questions your visitors are likely to ask before launch.
Safe rollout from single site section to full site
Start with a limited deployment on one page or section, review performance data, then scale to your full site when ready.
3. When to use it
- After assistant and knowledge setup is complete.
- When launching self-serve support on key product pages.
- When testing support automation in a limited site segment.
4. When not to use it
- Before validating knowledge source readiness.
- Before defining handoff behavior for low-confidence scenarios.
- As a substitute for assistant behavior and context setup.
5. Setup steps in app
- Open Widget in the app and copy your install snippet.
- Choose standard script, Next.js, WordPress, or GTM path.
- Add your workspace public key and loader script.
- Validate appearance and behavior in staging.
- Roll out to production pages and monitor outcomes.
6. Best use cases
- Product docs and help center surfaces.
- Pricing and feature-comparison pages for pre-sales support.
- Account areas where escalation to support is expected.
7. Common pitfalls and how to avoid them
- Pitfall: deploying before content quality checks. Avoid with a launch checklist and scenario tests.
- Pitfall: wrong workspace key in production. Avoid with environment-specific configuration review.
- Pitfall: visual mismatch with site brand. Avoid by finalizing assistant theme settings pre-launch.
8. Success metrics to track
- Conversation starts on widget-enabled pages.
- Resolution rate and handoff rate after deployment.
- Knowledge-gap rate for launched surfaces.
9. Related capabilities
- AI Assistant for behavior and appearance configuration.
- Knowledge Sources for coverage readiness before launch.
- Human Handoff for escalation continuity.
- Analytics for post-launch monitoring and optimization.
FAQ
10. Widget installation FAQs
What is required to install the widget?
A workspace public key and the Receiveo loader script are required for installation. Learn more
Can I install through Google Tag Manager?
Yes. GTM installation is supported using a custom HTML tag and page-view trigger. Learn more
What should we validate before go-live?
Validate assistant behavior, knowledge coverage, and handoff flow in staging or a limited production section first. Learn more
Launch a conversation layer your whole GTM team can use.
Unify grounded AI, web and WhatsApp coverage, human handoff, and conversation analytics without stitching together separate tools.