A customer support AI agent answers from your sources, takes an allowed action, and hands off with context. The label is not the capability. Plenty of “agents” are still FAQ bubbles. Voice is a channel, not a fifth step.
Guzli sells this install path and wrote the page. It is not an independent implementation study. Chatbase, Intercom Fin, and Zendesk AI are real alternatives with different meters and desks. Definitions: chatbot vs AI agent. Context: AI in customer service. Buy criteria: AI chatbot buyer’s guide.
Method: desk research plus Guzli’s published plans and named tools, 19 September 2026 — not a click-through of your workspace.
Verdict
Build when the top intents repeat and the help content is true. Write escalation before go-live. Do not turn on a write (refund, cancel, password reset) until you have watched it fail safely.
Who this is for
Teams that want website live chat — and later inbound call/SMS — on one brain, plus ticket create in Salesforce, Zendesk, or Guzli’s help desk. Shopify order lookup or Stripe status as the first action is the usual start.
Who this is not for
No maintained help center. No human to read logs. You need IT service management (ServiceNow or Jira Service Management) as the product, not a front line.
What “done” means
- Same answer from the article the agent used last week
- Action either completes or explains why it stopped
- Human request always works
- Leftovers land in the desk you already run
Guzli surfaces, when you enable them: website live chat, Slack, WhatsApp, Facebook Messenger, Instagram, Telegram, Discord, inbound call, SMS, email (agent inbox). Voice and SMS need Standard or Pro. See current plans and pricing. Hobby $49/mo chat-only (1,000 credits). Standard $149 + 16¢/min. Pro $499 + 14¢/min.
Five steps
1) Train the brain — knowledge first
Connect the live help center, the two policy pages your top intents need, and (when you can) solved tickets from Salesforce, Zendesk, or HubSpot. Site crawl + files are fine; tickets add the words customers type.
Gate: 20 real questions from last week’s queue. If three of the top five intents are wrong, do not expand sources. Fix the article.
2) One action — hands, not “superpowers”
Pick the action that deletes tickets without moving money:
- Shopify order lookup (email or order number → status + next step)
- Stripe subscription / invoice status (identity first)
- Calendly or Cal.com book a callback
Confirm which objects this workspace can write. Lookup ≠ refund. Chatbase’s service-desk post and Intercom’s Fin chatbot page (both opened 19 September 2026) describe action and procedure patterns on their own builders. Do not paste another vendor’s builder into this install.
Gate: ten staged conversations. Identity failure and tool timeout must hand off, not invent a tracking number.
3) Connect only the desk you will use
Integrations that do not fire in the pilot are noise. For Guzli, that usually means: the storefront widget, one ticket sink (Salesforce, Zendesk, or Guzli’s desk), and the one commerce tool from step 2. Slack or WhatsApp can wait until chat on the site is boringly correct.
Gate: a handoff ticket shows summary, channel, and customer identifier. If the agent has to re-ask “what was the order number?” the integration is not done.
4) Go live on one surface
Publish one page or one widget placement. Turn on “talk to a person.” Do not announce voice until Standard or Pro is paid and a test call on “where is my order?” plus “human please” works.
Gate: 48 hours, owner on transcripts. If users cannot reach a human in one turn, pull the widget.
5) Weekly review
Look at unanswered questions, escalation reasons, action success/fail, and (if you collect them) leads that were actually sales moments. Turn unanswered clusters into articles the same week.
Measure with your volumes: AI chatbot ROI and the ROI calculator. Do not use a stock “deflection” screenshot as proof.
After the first action is stable
Add the second workflow. Scheduling inside chat is the usual conversion add-on for demo-led sites. Keep it off the order-status widget if that page is not a sales page.
Pricing, only as a constraint
Hobby is enough to prove chat knowledge + lookup. It is not the store number. Voice minutes are a second meter on Standard/Pro. Compare Chatbase credits and Fin outcomes on Chatbase pricing vs Intercom Fin vs Guzli if you are still choosing a vendor — this page assumes you already picked Guzli.
FAQs
What should the first workflow be?
Highest volume, lowest write-risk. Shopify order lookup, Stripe subscription or invoice status, or booking a callback. Confirm identity before any customer-specific read. Do not start with refund, cancel, or password reset.
How do I keep answers accurate?
Connect the live help center and the two policy pages those intents need. Run twenty real questions from last week’s queue before you expand sources. One source of truth; resync when policy changes; treat misses as content work the same week.
Should the agent replace the helpdesk?
No. Guzli sits in front and opens a ticket in Salesforce, Zendesk, or Guzli’s help desk. Write the escalation path — including identity failure and tool timeout — before go-live. A human request must work in one turn.