Docs
Browse documentation
How it works
Follow the end-to-end flow from a visitor opening the widget to analytics appearing in your dashboard.
What you will learn
- How the widget identifies your business and loads configuration
- What happens when a visitor sends a message
- How conversations are stored and surfaced in analytics
Visitor to widget
The HikariFloww widget is loaded by a script tag on your site. The script resolves the current domain, pulls your business record, and then boots the chat interface.
If no matching business is found, the widget logs a warning so you can fix the domain mapping.
- Script loads from /api/widget
- Domain is normalized and matched to your business profile
- Widget renders as a floating bubble and expandable panel
Response pipeline
Messages are sent to the HikariFloww backend, which builds a system prompt from your business profile, menu, and structured data.
Responses stream back to the widget and are stored alongside the original customer message for analytics.
- Business details set tone and accuracy
- Responses are streamed for faster perceived speed
- Conversation records are stored per business
Analytics feedback loop
Each conversation contributes to analytics, such as volume, popular questions, and engagement patterns. Use those insights to adjust your profile and content.
Expected outcome
- You can describe the data flow from widget to response.
- You understand where analytics data comes from.
Common issues
- Widget cannot find the business because the website domain is missing or formatted incorrectly.
- Script blocked by CSP or ad blockers, preventing the widget from loading.
Related articles
Still stuck?
Contact our team and we will help you troubleshoot or plan the next step.
Contact support