Glossary
Every Zyan term in one alphabetical list — workspace, seats, credits, permission grid, portal kind, research target, dispatch, preflight and the rest.
Zyan uses a fair number of specific words, and several of them mean something narrower than they sound. This page defines them all in one place. Where a term belongs to one area, the definition says which.
Two pairs are worth learning before anything else: plan feature versus permission, and workspace owner versus full access. Most access questions are one of those two.
A
| Term | What it means |
|---|---|
| Account access vs Project access | How the project scope picker labels client portals. Account access is the portal with no project linked; every other portal is labelled with its project's name. |
| Active SEO program | A per-portal flag that shows the SEO program — strategy focus, shipped work, results — inside the client's portal. The website has to be enrolled in the SEO Command Center first. |
| Add-on entitlement | A purchased or granted service attached to a client portal, such as SEO reporting, Visitor ID, Google Ads or blog content. It decides which data surfaces the client sees. |
| Add-on family | A service category clients can request from their portal. Eight families are built in. |
| Agent version | A voice agent's saved configuration, numbered v1, v2 and so on. Versions go draft, then published, then archived. A published version is immutable — to change one you create a new draft. |
| Approval | A project-scoped sign-off you ask a client for, with optional checklist steps. The client answers Approve or Request Changes. |
| Approval link | A private, no-login URL emailed to a client so they can approve, request changes or reject a content post. It expires after a chosen window. |
| Audience | The saved recipient set attached to an outbound sequence. The first attached audience is load-bearing — Lead Manager enrols leads into audience position 1. |
| Audience classification | How you label who a voice campaign calls: internal test, consent backed, B2B counsel approved, or consumer cold. Consumer cold is denied by default with no in-app override. |
| Autopilot | A per-website blog publishing schedule — cadence, topic strategy, article format and publish mode. Found on SEO Command Center → Content → Schedule. |
B
| Term | What it means |
|---|---|
| Backlog item | A proposed strategy decision in the SEO Command Center, graded P0, P1 or P2. A P0 proposal blocks activation until it is reviewed. |
| Binding | Linking a Builder project to a real folder on the machine running the desktop app, so local runs have a working tree. |
| Branding blob | The single shared record holding workspace name, display name, logo, logo text, logo alt text, favicon, brand colour and legal links. The admin portal, sign-in page and client portal all read it. |
| Broadcast | A single marketing email sent once to a list, to leads or to pasted addresses. The Outbound one-time emails family. |
| Bucket | How the Projects page groups a project. Any status containing maint is Maintenance, complete or done is Completed, everything else is Active. |
| Business type (niche) | One of eight workspace categories. Picking one fills in task types, lead tags, delivery steps, an onboarding pack, billing categories and the AI's description of your business. |
C
| Term | What it means |
|---|---|
| Capture token | A secret string shaped <workspace id>.<secret> sent in the body of a POST to the custom lead-capture endpoint. It is what authorises the request for your workspace. |
| Change set | Budget or bid edits staged on the Ad Manager list. They sit unapplied in a bottom bar until you open the review sheet and press Apply. |
| Checkpoint | A client-visible milestone on a project. Completion percentages on cards and in the portal are checkpoint-driven, never derived from the board column. |
| Client | The admin-side record: name, company, email, phone, notes and a status of active, lead or archived. Creating one does not create a login. |
| Client portal | One login for your customer. A client can hold several portal rows — one per project or website, plus optionally one account-level row with no project. |
| Client task | A to-do you assign to a client through their portal, with a title, description, instructions, priority, category and due date. |
| Context pack | A named bundle of approved knowledge sources a voice agent may search during a call. Attached per agent version and, optionally, per campaign. |
| Cost cap | The dollar ceiling for one SEO research run. Blank uses the website default, and the server keeps the lower of your cap and that default. |
| Credits | A pooled workspace balance spent by AI surfaces — research runs, drafting, prospecting, voice minutes. Included credits reset at renewal and never stack; purchased packs sit on top and expire after 60 days. |
| Custom domain | A domain you own that serves the client portal only. Your admin workspace always stays on the platform address. Requires the custom-domains plan feature. |
D
| Term | What it means |
|---|---|
| Deliverability hold | The dispatcher pauses an outbound mailbox automatically at 5 bounces or 2 spam complaints in 7 days, until you mark it investigated. |
| Discovery form | The questionnaire from an onboarding pack. The client fills it during onboarding, or later from their portal. |
| Dispatch | One attempt to write one blog post. Minted by the platform, claimed by a runner, drafted, then published. Its state drives the Latest post badge. |
| Do not contact | A per-lead flag with a reason code that suppresses the lead from outbound sends. |
| Dock | The narrow icon rail on the right of the admin portal. On wide screens the assistant panel docks as a third column and the page reflows beside it. |
| Draft vs Active (strategy) | Research writes a draft strategy. You review it and press Activate draft to make it active. Only one open draft per website at a time. |
| Draft vs variant (content) | A Compose run produces one draft holding one to six variants of the same post. You pick a variant, then save, schedule or publish it. |
E
| Term | What it means |
|---|---|
| Emergency stop | A workspace-level switch that pauses every voice campaign at once and makes any launch fail preflight until it is cleared. |
| Evidence lane | One of three refreshable data streams behind SEO research: site knowledge (a free crawl), search evidence (a paid data pull), and content structure (a paid on-page audit). |
| Execution | One queued send inside an outbound sequence. An execution can be queued, sending, needs review, failed or blocked. |
| External booking | A booking made in a connected third-party scheduler and imported read-only. Availability and changes stay in that tool. |
| External form | A form hosted at another provider whose submissions Zyan receives. Its fields are owned by the provider and are read-only in Zyan. |
F
| Term | What it means |
|---|---|
| Feature key | The internal name of one permission row, such as leads, payroll, builder or messages_client. Used in the grid and quoted in error messages. |
| Fill mode | How business-type defaults are applied: only things you have not already set up are filled in. Nothing you authored is ever overwritten. |
| First-touch SLA | The minutes-from-arrival deadline for someone to make first contact with a new lead. Drives the Attention queue. |
| Full access (admin) | A per-member switch making a teammate owner-equivalent for features, permissions, billing and audit — but not for the workspace subscription, the owner account, or arming autonomous sending. |
G
| Term | What it means |
|---|---|
| Gap segment | Keyword Gap partitions every keyword into five buckets that do not overlap — Shared, Missing, Weak, Strong and Untapped — plus a Unique overlay chip. |
H
| Term | What it means |
|---|---|
| Held before drafting | A queued blog post stopped before any writing happened. It can be re-drafted or removed; nothing was written or published. |
| Honeypot | An invisible field on hosted lead forms. A bot that fills it gets a success-looking response and no lead is created. |
| Hosted lead form | A form you build in Zyan that lives on your own verified domain. It can be linked directly or embedded in another site. |
I
| Term | What it means |
|---|---|
| Intake mode | How new website leads are assigned: manual only, round robin, or least loaded. |
| Intent cluster | A named group of search queries with a business outcome, an owning page and supporting pages. Labelled Intent in the Strategy navigation. |
| Internal portal | A portal whose access email matches no client record. It has no client detail page, so it is managed from the portals workspace instead. |
| Item kind | A row on the task table is a task, a meeting or a content item. The kind decides which extra fields appear. |
K
| Term | What it means |
|---|---|
| KD | Keyword Difficulty, 0 to 100, shown as a band chip or gauge. |
| Knowledge source | A stored document the AI reads — a crawled page, an uploaded file, a transcript, a URL or a note. Sources are chunked and embedded for retrieval. |
L
| Term | What it means |
|---|---|
| Lead Manager | The queue holding every unconverted lead in the workspace. Converted leads leave the queue. |
| Lens | The view switcher on several pages. The content calendar has Month, Week and List; the accounts page has Stats, Feed and Posts. |
| Line | A business phone number that texts send from and inbound texts land on. |
| Live check | The platform re-fetching the guessed public URL of a published post until it resolves. Until then the URL is a guess, not a confirmation. |
| Live fix | A source-level SEO fix — meta, canonical, schema, alt text, internal links — staged as a pull request or applied directly, with a rollback ledger. |
| Living strategy | The strategy object for a website: an active side, optionally a draft side, a version number, a charter, a monthly focus, intent clusters and a backlog. |
| Local vs cold outreach | The origin split in Lead Manager. Local is leads you entered or that arrived through your own inbound channels. Cold is prospected leads and identified website visitors. |
M
| Term | What it means |
|---|---|
| Mailbox daily cap | The per-mailbox ceiling the dispatcher enforces each day, shown as sent today over cap. Warmup can lower the effective cap below the number you typed. |
| Manage link | The private link in every booking confirmation email that lets the visitor reschedule or cancel until the meeting starts. |
| Map Pack tracking | A geographic grid of local-search rank scans around a business listing, configured per website and optionally shown to the client. |
| Market | The country an SEO research target measures in. Country-only by design; each country carries a default language code. |
| Member | A staff teammate whose access is decided entirely by the permission grid on their member page. |
| Memory | Durable notes the Zyan AI assistant keeps, agency-wide or per client. You can add, edit, undo and delete them. |
| Merge returning visitors | A lead-form setting. When on, a submission matching an existing lead by email or phone updates that lead instead of creating a duplicate. |
| Minor units | Money is stored in the currency's smallest unit — cents. Budget and bookkeeping figures are converted for display. |
| Mock runtime | The default voice runtime. Calls are simulated with no telephony egress. Live dialling requires platform gates armed outside the admin portal. |
| Money guard | Frozen safety ceilings on ad-spend edits. A change past them is flagged as failed and excluded from Apply, and the server rejects it even if you force it in. |
O
| Term | What it means |
|---|---|
| Onboarding pack | A reusable bundle: one discovery form, client task templates, delivery checkpoints, content items, and a welcome email subject and message. |
P
| Term | What it means |
|---|---|
| Parked run | A research run paused waiting on you, shown as Needs you. Common reasons are a cap reached, a draft conflict, ungrounded seeds or missing credits. |
| Pay item | A single earning line on a payroll statement — hours, build, service, upsell, project, bonus or custom. |
| Permission grid | The per-member, per-feature matrix of View, Edit, Create and Delete. Turning on Edit, Create or Delete turns View on; turning View off clears the whole row. |
| Pipedream-backed connector | An integration where Pipedream manages the provider's OAuth. You connect at the provider and Zyan stores only a binding, never the provider's tokens. |
| Plan (billing catalog) | A sellable service or bundle on your client price list, with a price, interval, category and status. Not to be confused with your Zyan subscription plan. |
| Plan feature (entitlement) | Whether your Zyan plan sells a capability at all. Separate from permissions — a permission cannot unlock something the plan does not include. |
| Platform address | Your always-on workspace hostname, a *.zyan.ai subdomain. It never goes away, even after you add a custom portal domain. |
| Portal kind | Full portal, Leads, SEO, Backlinks or Ads. Minimal kinds land the client on their product surface and hide agency-workflow navigation. Changing the kind rewrites the section toggles. |
| Post group | A named bundle of related content posts, such as one campaign, that the calendar can be filtered by. |
| Preflight | The deterministic compliance and operational check run before a voice campaign is approved, before it launches, and again before every single dial. Errors block; warnings need a typed acknowledgment. |
| Product (voice) | A separate versioned record holding the offer content an agent may quote — FAQs, objections, pricing and claim rules. A campaign pins one published agent version and one published product version. |
| Proposal | Anything the Zyan AI assistant wants to create or change, shown as a card you approve or deny before it is written. |
| Prospecting session | One conversation with the prospecting assistant. Results, credits and saved state are pinned to that session. |
| Publish advisory | A recorded note about something the platform noticed while publishing a post. Advisories never block a post — only security and configuration problems hold one. |
| Publish mode | How a finished blog post reaches the website repository: review pull request, auto-merge, or direct push. |
| Publishable key | The workspace API key sent as a header on lead-capture calls. Safe to place in a public web page, unlike the capture token. |
| Published graph | The frozen copy of an automation the dispatcher actually runs. Saving a draft never changes live behaviour — only enabling or publishing does. |
| Published version | Publishing a lead form snapshots its current fields. Visitors always see the last published snapshot, never your unsaved draft edits. |
| Punch vs override | A punch is an immutable clock event. Corrections never edit punches — they write a per-day override. |
R
| Term | What it means |
|---|---|
| Radar | The SEO opportunity feed: striking-distance keywords, competitor top-ranking pages, trending news and RSS. Each item can be dismissed, sent to Autopilot or rewritten as a draft. |
| Report keyword set | The opt-in subset of tracked keywords that appear in client reports. Capped, and it never auto-includes brand keywords. |
| Request | A revision or change request. Clients raise them from the portal and you triage them in the Requests inbox. |
| Research brief | The five fields telling research what the business is: niche, target audience, primary services, secondary services and target locations. With the niche and primary services both empty, deep research is blocked. |
| Research run | The staged pipeline that builds a strategy. A full run is ten stages; a monthly adjustment is three. |
| Research target | A domain paired with one country market. All keyword and competitor research is scoped to a target, and each carries its own monthly research ceiling. |
| Runner | The Zyan desktop app, open and signed in with a project folder bound. It claims blog drafts and fix jobs and runs them locally. |
S
| Term | What it means |
|---|---|
| Saved view | The stat tiles on the Tasks board — Overdue, Today, Review, Unassigned — which double as one-click filters. |
| Seat (client portal) | An extra client login on the same portal, up to five beside the primary. Payment methods, personal notifications and account settings stay per-login. |
| Seats (staff) | How many staff members your Zyan plan allows. Pending invitations count. Builder seats are a separate cap and the workspace owner is exempt from it. |
| Sections | Per-portal checkboxes controlling which portal areas a client sees. Unchecked means hidden; an omitted value is treated as enabled. |
| Semi-monthly period | Payroll and timesheets run on half-month ranges — the 1st to the 15th, and the 16th to the end of the month. |
| Send window | The hours and days an outbound mailbox may send. A mailbox with no hours of its own inherits the workspace window. |
| Sending domain | A verified subdomain used as the From address for portal and marketing email. Separate identities exist per purpose and per client. |
| Sequence | A multi-step cold-email cadence sent from a connected mailbox, with waits between steps and a per-sequence approval policy. |
| Setup-surface window | Temporary first-run surfaces — the Getting Started card and the business-type prompt — disappear seven days after the workspace is created, finished or not. |
| Skill | An at-mention shortcut in the Zyan AI composer, such as a website audit or a client report. |
| Statement | A payroll record for one team member for one pay period. It moves draft, then approved, then paid. Creating or approving one never sends money. |
| Storefront | A public product page served from your portal domain, where a purchase creates the client, portal and entitlement automatically. Available only on plans that sell Storefront, and it requires a connected payment account. |
T
| Term | What it means |
|---|---|
| Test mode | A voice campaign flag, on by default, restricting live dialling to allowlisted destination numbers. |
| Triage | The review step visitor leads go through — pending, kept or discarded — before they become CRM leads. |
| Trigger and step | An automation is one trigger, the event that starts it, plus a graph of steps: the actions, conditions and waits that follow. |
V
| Term | What it means |
|---|---|
| Visitor identification | Anonymous website visitors resolved to a person or company by a third-party provider and delivered to Zyan for triage. |
W
| Term | What it means |
|---|---|
| Warmup stage | A ramp raising a new mailbox's effective cap over its first weeks, from manual through three phases to production. |
| Widget | A removable card on the dashboard. Layout, size and visibility are saved per user and per scope. |
| Work item vs shift | Tasks and content items live on the project action list; shifts are a separate entity that appears only on the Work Hub schedule, timesheets and the member dashboard. |
| Workspace (tenant) | Your agency's account. One workspace per Zyan subscription, and each staff user belongs to exactly one workspace. |
| Workspace owner | The single account that owns the subscription. Only this account sees Settings → Plan & Credits and can change the plan. |