Website chatbot for customer support: widgets, handoff and accessibility

If you already use a helpdesk, start with its widget. Chats land in the same queue as email and social messages, agents reply from one workspace, and the vendor maintains the widget code.

• Zendesk Web Widget (messaging): in Admin Center, go to Channels > Messaging and social > Messaging, open the widget and copy the code from the Installation section. Add it to the source of every page where the widget should appear, and make sure your firewall allows the widget.
• Freshchat web widget (Freshdesk): copy the embed code from the web chat channel settings and add it to every page where the widget should appear. Freshworks also documents installing it on WordPress, Shopify, Squarespace, and in iOS and Android apps.

The handoff is where most website bots fail. A good one moves the customer to a person without making them repeat themselves. Both major helpdesks support this pattern:

• Zendesk: adding an AI agent to a messaging channel replaces the default messaging response with the AI agent's own responses. Zendesk's workflow recipe has the AI agent greet the customer, show a form to collect what agents need, tell the customer the request is going to the team, and then forward the conversation to an agent, who is notified and sees the details on accepting it. The recipe uses a shorter form for logged-in customers, without name and email.
• Freshchat and Freshdesk: bot flows hand over with actions such as Assign to group or Make available for assignment, and Freshdesk's AI agent handover settings include an option to collect customer details before transfer.

Decide what to collect from what your agents ask first. Typical fields are name and email for visitors who aren't logged in, an order or account number, the issue type chosen from buttons, a short description in the customer's own words, and the page they were on.

A widget that promises "an agent will be with you shortly" at 2 a.m. does more harm than no chat at all. Plan what happens when nobody is online:

• Set business hours: Zendesk messaging channels can use a business hours schedule and show different responses during and outside those hours.
• Turn chats into tickets: in Zendesk's recipe, the AI agent escalates to a live agent during business hours, and outside them it collects the customer's details and escalates the request as an email ticket for follow-up.
• Let the bot answer what it can: FAQ answers, order status lookups and help center links work at any hour.
• Say when you'll reply: tell the customer your hours and where the answer will arrive, such as by email.

A chat widget is interactive content layered over your site, so it needs to meet the same accessibility bar as the rest of the page. WCAG 2.2 is the current W3C version, and these success criteria are especially relevant to chat:

For the conversation itself, W3C technique ARIA23 marks the chat history with role="log": new messages are added to the end of the region and screen readers announce them as they appear. With a vendor widget, test your own configuration with a keyboard and a screen reader, since custom colors and bot content can still introduce problems.

TascaLab sets up website chatbots on top of the helpdesk you already use, such as Zendesk or Freshdesk, or connects a custom bot to Jira, Slack or internal tools through APIs, webhooks, and Make or n8n. A Starter Chat Bot ($400) covers one or two channels with FAQs and basic info collection; a Standard Chat Bot ($575) covers three to five channels with more complex conversations and smoother handoffs. Every project includes 30 days of post-launch support and basic documentation, with no hidden fees, and most setups take 1–3 weeks. Start with a free 30-minute Health Check call.