FoundChat is not a Zendesk ticket desk replacement. Use this guide to move on-site FAQ deflection to FoundChat and escalate into Zendesk when humans are needed. Port public help center articles and approved macros; keep Zendesk tickets for complex cases while FoundChat owns repetitive website FAQs first.
Why teams switch
Buying Zendesk primarily for website AI is usually overkill for early products. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Train and embed without a CX ops project. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
How to migrate
01
Point FoundChat at your public Zendesk Guide URLs or export articles as PDFs/markdown. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
02
Create a support agent and verify answers against your top 20 Zendesk macros. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
03
Use Slack/email/webhooks so unresolved chats become tickets or agent alerts. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
04
Swap Zendesk chat on marketing/docs pages for FoundChat; keep Zendesk for agent workspace. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Keep in mind
Do not expect FoundChat to become your SLA system of record. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
Stale Zendesk Guide articles become stale agent answers refresh high-traffic macros before cutover. Review unanswered logs weekly, update training sources when product or policy pages change, and expand scope only after two weeks of measurable improvement on high-intent pages.
FAQ
Usually no. Keep Zendesk for tickets; use FoundChat to reduce how many tickets start.
Use webhooks or Zapier-style automation to open tickets from escalated conversations. Native deep Zendesk agent workspace is not the goal.
Public Guide articles and the top macros that encode policy answers. Leave private internal notes out of training.
Track unanswered questions and ticket volume from website entry points for two weeks before removing Zendesk chat widgets.
Keep exploring
Join founders using FoundChat for support, sales, onboarding, and lead capture.
No credit card required · Live in minutes · Cancel anytime.
