Where the work gets stuck
Your website should remain easy to use after you add a messaging assistant. Keep service information and contact options clear, and add the chat widget where it will help. Test it on mobile devices and with accessibility tools. Set up Heyy to support your existing enquiry process.
What to prepare
- Permission to update the site and a plan to undo the change if needed
- The person responsible for the page and enquiry process
- Approved answers, an alternative contact option, and a few test questions
Follow these steps
- Follow the provider’s current website integration process on a test page.
- Check that the widget does not obscure contact controls or important page content.
- Test opening and closing the chat, typing a message, and using the alternative contact option on phones and desktop screens.
- Add the widget to the chosen page and review the first real conversations with the person responsible.
An example from everyday work
A mobile applicant should still be able to read the programme fee and reach the application process while the widget is closed. A customer who requests a person should receive a usable next step instead of being sent back through the same AI questions.
When your team should take over
Only authorised site maintainers should add scripts. If a security setting blocks the widget, have the maintainer resolve it deliberately rather than disabling the setting broadly.
How to check the results
- How easy the widget is to use and whether it covers page content
- Whether requests reach staff or another contact option successfully
- Questions that reveal missing page information
Your next step
Use chat logs to improve the page itself. An answer needed repeatedly may belong in the main page information too.