Vicket Sells Per-Site Support, Not Per-Agent Zendesk Tax

Zendesk bills per agent; your eng team builds a Notion + Gmail support stack instead of the product. Vicket sells white-label, multi-tenant customer support you embed: one dashboard, per-site isolation, visual workflows, ticket scoring—"Live in 2 minutes" via SDK scaffold (vicket.app). Judge it on invoice math vs Zendesk at your agent count, not .app TLD naming pillars.

ICP: SaaS portfolios and agencies

Two buyers repeated on the homepage:

SaaS founders running multiple products—each product gets branded portal, ticket queue, KB; data isolated per tenant.

Agencies serving many clients—each client gets own portal/skin; agency sees all from one login with visibility rules (scope tags like agency-a → site 1 only).

Embed thesis: users click Help inside your app—not a foreign Zendesk subdomain breaking immersion.

Product mechanics

| Feature | Function | Why it monetizes | | --- | --- | --- | | Embeddable UI | Your colors/domain/components | White-label on all plans including free | | Workflow builder | Event/time triggers: assign, escalate, follow-up | Replaces eng-built cron jobs | | Ticket scoring | Priority from form answers pre-read | SLA risk reduction | | Knowledge base | Self-service | Deflect tickets | | Multi-tenant control plane | Switch sites without logout | Agency ops |

Setup (site terminal block):

npx @vicket/create-support --framework next
# creates app/support pages + API route + VICKET_API_KEY in .env.local

No self-host per FAQ—data on Vicket infrastructure (trade-off vs 2-minute promise).

Business model: site-based tiers, not seats

Homepage promises free plan, white label on every plan, 14-day Growth trial without card (vicket.app). Public pricing table (marketing site, verify before purchase):

| Plan | Price (published) | Agents | Sites | | --- | --- | --- | --- | | Starter | Free | 2 | 2 | | Growth | €29/mo | 5 | 3 | | Business | €79/mo | 15 | 5 | | Enterprise | €199/mo | 50 | 10 |

No per-agent fees—adding support headcount doesn't auto-trigger Zendesk-style jumps. Caps on sites matter more for serial founders (testimonials cite managing three products).

Early quotes: Thomas B. replaced Notion+email; Julien C. avoided "facture Zendesk à 200€ par mois"; Rémi P. unified three products.

Revenue aligns with EU bootstrapped SaaS (euro pricing)—agencies upgrading when client count exceeds site caps.

Competitors

| | Vicket | Zendesk | Intercom | Freshdesk | DIY Notion | | --- | --- | --- | --- | --- | --- | | Core bet | Embedded white-label multi-tenant | Enterprise ITSM | Product tours + inbox | SMB helpdesk | Free, fragile | | Pricing axis | Per site | Per agent | Seats + usage | Per agent | Time cost | | Embed | First-class SDK | iframe awkward | Messenger | Limited | None | | Sweet spot | Multi-product SaaS, agencies | Large support orgs | PLG messaging | Budget tickets | Solo founders |

Workflow examples and agency operations

Sample workflow on site logic: Ticket created → assign by category → if no first reply in 4h escalate → if waiting 7 days send follow-up. Agencies run parallel scopes (core sees all sites; agency-a sees client A only)—preventing ticket leakage between clients without separate logins. Ticket scoring from form answers ("billing urgent" vs "docs question") automates triage where Zendesk would need paid AI add-ons.

Embed components mean support CSS matches product—reducing "am I still in the app?" distrust. Limitations: no self-host blocks regulated finance/health unless DPA acceptable; 10-site Enterprise cap forces upgrade conversation or churn to Zendesk when portfolios scale. Testimonials cite Friday afternoon migrations from Notion—implementation speed is the sales weapon, not feature checklist depth.

Pricing math vs Zendesk

At 10 agents, Zendesk Suite commonly exceeds €800–1000/month in EU list pricing; Vicket Business €79 with 15 agents and 5 sites inverts the curve until you need >50 agents or >10 sites—then Enterprise €199 caps force Zendesk conversation. Per-site not per-agent helps agencies adding junior support staff without invoice spikes.

14-day Growth trial, no card reduces eval friction; white label on free Starter (2 agents, 2 sites) lets solo founders embed before revenue—generous land, expand when second product ships. Missing today: Slack bi-directional, SOC2 badge, self-host—enterprise checklist gaps.

Embed SDK vs iframe help widgets

Vicket's npx @vicket/create-support --framework next scaffolds first-party routes (/support, API handlers)—not a third-party iframe that breaks CSP and styling. That architectural choice matters for PLG SaaS where support should feel native: same fonts, dark mode, auth session. Zendesk embeds often look like a support portal detour; Vicket sells invoice alignment when you operate 2–5 products under one eng team.

Multi-tenant visibility rules (agency-a scope) prevent ticket bleed between clients without separate logins—agency margin lives in headcount efficiency, not per-agent SaaS tax. Knowledge base deflection reduces ticket volume before workflow triggers fire—important when Growth plan caps 5 agents but agency hires sixth intern.

Gap analysis for enterprise buyers: no marketed WeChat/钉钉 channels, no SOC2 badge on homepage, FAQ confirms no self-host. Vicket wins EU bootstrapped SaaS replacing Notion+Gmail; loses Fortune 500 ITSM needing SAML depth and China omnichannel.

China context

Vicket is EU-hosted SaaS with euro billing—natural for 法国/欧盟 agencies (Julien C. testimonial). Mainland 出海 SaaS may embed for global users; PIPL requires DPAs for Chinese user tickets—Vicket isn't a replacement for 网易七鱼/智齿 on domestic consumer apps. WeChat support integrations not marketed—expect email/web portal only.

Migration story: Notion + Gmail to embedded support

Homepage testimonials emphasize Friday-afternoon migrations—Thomas B. from Notion+email, Julien C. avoiding €200/month Zendesk, Rémi P. unifying three products. That ICP is EU bootstrapped SaaS with 2–15 support agents, not 200-seat call centers. Vicket wins when support volume is moderate but brand immersion matters—users shouldn't feel teleported to zendesk.com.

Knowledge base + ticket scoring + workflows form a deflection triangle: KB answers L1, scoring routes L2 urgency, workflows enforce SLAs without Zapier glue. Caps on sites (2/3/5/10) align pricing with serial founders and agencies, not headcount—inverse of Zendesk's per-agent ladder.

Future enterprise checklist gaps (SOC2, self-host, Slack bi-directional, WeChat) define ceiling. Until closed, Vicket is best-fit embed helpdesk for multi-product EU SaaS under ~50 agents—honest positioning beats feature parity claims against Zendesk Enterprise.

Verify before SDK commit

Site cap math. Count products/clients vs plan sites.
Self-host requirement. FAQ says no—confirm compliance accepts SaaS processor.
Integration list. Slack/Discord depth vs Zendesk marketplace.
Migration. Export path if you outgrow 50 agents / 10 sites.
Live 2-minute claim. Time your team restyling components—SDK is fast; brand polish isn't.

Vicket's edge is economic alignment for multi-tenant embeds: white-label everywhere, site-metered pricing, npx onboarding. Not feature parity with Zendesk Enterprise. Win when €79 beats €800 and support looks native; lose when you need SOC2-heavy ITSM or China-local omnichannel.