Skip to main content
Zyptova Studio
Menu

companies with 20 to 500 people and one to fifty locations

Market it, answer it, book it, sell it. One platform.

ZYP is for running the customer side of a growing business: social publishing and design, an AI agent on every channel, events, appointments and reservations, menus and orders, and the customer record that ties them together. One login, one customer record, one bill.

  • Restaurants & bars
  • Venues & events
  • Salons & studios
  • Clinics & services
  • Real estate
  • Home services

Perspective three · surfaces

Start where people actually are

Pick a surface, the place a customer or a team member meets ZYP, and drill down: the apps on it, the screens and conversations in each app, and the features each one uses. Select a feature to open it in Feature details.

Pick a surface

Surfaces

  • collective

    Shell · mobile and web · 4 apps

    What a guest or client opens: find what's on, book or order, and keep track of it all.

  • collective-provider

    Shell · web and mobile · 8 apps

    Where marketing, front desk, operations and owners do their work. One login, with screens shown by role and plan.

  • collective-agent

    MCP tools · 1 app

    The same features as tools an AI assistant can call, so a customer can ask their assistant to book or order.

  • Website widgetplanned surface

    Embed · your own site · 1 app

    One snippet on the business's website: chat, book, order and see what's on, without leaving the page.

  • Conversationsplanned surface

    Agent · voice, text and DMs · 3 apps

    The AI agent works each channel with the same tools the apps use, and hands to a person when it should.

  • Social & feedsplanned surface

    Outbound · where you're seen · 3 apps

    Surfaces ZYP publishes to: social accounts, review sites and local event feeds.

  • POS terminalplanned surface

    Device · counter and bar · 1 app

    ZYP POS at the counter, reading the same menu and reservations as everything else.

Apps, screens and the features they use

collective

Capability by capability

ZYP 1.0, in 2.0 form

  • Events

    calendar.event · apps/gig-hub events, spas/events/booking, spas/admin/events-mgt

    Already a 2.0 capability: gig-hub's unified events model maps onto it

  • Availability

    calendar.availability · apps/gig-hub venue availability

    Already a 2.0 capability

  • Appointments

    calendar.appointment · virtual-agent Appointments tool, integrations/calendar

    Engage's $10 Appointments pack becomes a grant on these features

  • Reservations

    calendar.reservation · zyp-pos reservations, Engage bookings

    Already a 2.0 capability

  • Talent & vendor bookings

    calendar.booking · apps/gig-hub bookings and holds, spas/events/promoter

    Holds and the steward confirmation carry over as booking states

  • Participation

    calendar.participation · spas/events/fan-hub, gig-hub RSVPs

    Rows exist in zyp-2.0; collective-api has no adapter yet

  • Directory listings

    directory.provider + directory.category · apps/gig-hub venues and entertainers, venue claiming

    Managed and unmanaged venues map onto provider claim

  • Categories

    directory.category · apps/gig-hub venues and entertainers

    Already a 2.0 capability: the categories the directory is browsed by

  • Loan quotes

    finance.loan · new in 2.0

    Scaffolded in 2.0 by zyp domain add for the Collective's loan quote

  • Follows

    interest.follow · gig-hub favorites, spas/events/fan-hub

    Lives in 2.0's interest domain; the page groups it under Customers

  • Saves

    interest.save · gig-hub favorites digest

    Lives in 2.0's interest domain

  • Menus & catalog

    commerce.menu · spas/restaurants/menu-mgmt, POS menus

    Menu Manager's Prisma model (menu, category, item, modifier group, option) is the row set

  • Orders

    commerce.order · virtual-agent Orders tool, integrations/pos orders, pos delivery service

    Google delivery zones stay an adapter concern

  • Payments

    commerce.payment · integrations/payments (Stripe Connect), spas/payments (payee, payor)

    Stripe Connect behind a payments port

  • Point of sale

    commerce.pos · integrations/pos (ZYP POS, Square, Clover), integrations/pos/zyp-pos

    PosAdapter already has the port shape; it moves as-is

  • Message boards

    community.board · spas/communicate/message-board, platform/zyp-community

    Community shell's Message Board

  • Private messages

    community.message · spas/communicate/private-link, apps/user-chat

    Private Link

  • Templates

    content.template · 1.0 estate: design.template (design-studio), apps/design-studio

    Lineage-based templates; poster chrome is a template

  • Brand looks

    content.look · 1.0 estate: design.look (design-studio)

    The brand kit

  • Design components

    content.component · 1.0 estate: design.component (design-studio)

    Design-system pieces

  • Images

    content.image · apps/image-gen, integrations/image-models

    Bedrock image models behind an image port

  • Video shows

    content.show · 1.0 estate: studio.show (video-studio)

    The studio product's key becomes the content domain

  • Video episodes

    content.episode · 1.0 estate: studio.episode (video-studio), apps/video-gen

    Produced, reviewed and published per show

  • Show hosts

    content.persona · 1.0 estate: studio.persona (video-studio)

    Show hosts

  • Show formats

    content.format · 1.0 estate: studio.format (video-studio)

    Show formats

  • Content sources

    content.source · 1.0 estate: studio.source (video-studio)

    Content sources

  • Customer record

    customers.contact · integrations/crm, virtual-agent crm-adapter, spas/admin/zyp-crm

    Twenty, ZYP Customer, Lofty and ERPNext behind a CRM port

  • Contact preferences

    customers.consent · virtual-agent opt-out, comms preferences

    Split out of the customer record: consent is a noun with its own verbs

  • Leads & pipeline

    customers.lead · virtual-agent Leads, integrations/crm leads, pipeline

    Pipeline stages become feature states

  • Segments

    customers.segment · new in 2.0

    No 1.0 source; new in 2.0

  • AI agent

    engagement.agent · apps/virtual-agent (api, tools, text-worker), Engage shell: VA app

    Agent tools call 2.0 features through the same bindings

  • Channels

    engagement.channel · virtual-agent voice-server, text-worker, social, integrations/sms-transport

    Twilio SMS and voice behind a channel port

  • Knowledge

    engagement.knowledge · apps/converse (api, ingestion, scraper), apps/business-knowledge, Intelli-Chat shell

    Converse and Intelli-Chat collapse into one capability and one plan family

  • Website widget

    engagement.widget · Converse widget

    Split out of knowledge: a widget is a noun with its own verbs

  • Inbox

    engagement.inbox · spas/communicate/engage-inbox, virtual-agent ui: Inbox

    Engage Inbox and Amplify Inbox become one

  • Reviews

    engagement.review · virtual-agent review connections

    Google and Yelp behind the integration port

  • Social posts

    publishing.post · apps/social (api, spa), Amplify shell: Social, 1.0 estate: amplify.post (video-studio)

    Meta and TikTok publishing adapters; the 1.0 estate's amplify key becomes a customer term

  • Social accounts

    publishing.account · 1.0 estate: amplify.channel (video-studio)

    Renamed from channel so it is not confused with engagement.channel

  • Campaigns

    publishing.campaign · apps/social campaigns and post presets, Command Center 2.0: amplify.campaign (proposed), events-feed campaigns

    Tenant and operator promotion share one noun; schedule is a verb on it

  • Event feeds

    publishing.feed · 1.0 estate: amplify.run (design-studio), spas/admin/events-feed, BFF weekend-lineup publisher

    A feed run is approved or declined before it publishes

  • Event posters

    publishing.poster · 1.0 estate: amplify.poster (design-studio), spas/admin/poster-studio

    Posters render from content templates