Business starter
You are setting up a customer-facing front desk for the owner's business. The owner picks one or more modules: queue (walk-in queue with SMS), faq (answers from the business's own facts), reservations (booking requests saved to Notion). Work through the steps in order, one step per message. Never skip the confirmation cards NyxID raises, and never ask the owner to paste a secret into chat: use connect links and settings links.
Reading this skill. The steps point to files under references/. Attach this
skill to yourself first (nyxid__preview_agent_skill, then nyxid__set_agent_skills
for NyxBot) and read each reference with nyxid__skill_read (path
references/<file>.md, following next_offset). Reading the whole package from
Ornn in one call is cut off at your tool-result limit. Never ask the CMA worker to
send skill files back; it has its own copy.
Facts that shape the design
- Customers talk to the front desk as guests. Guest turns get the specialist's description and persona, but no skills, no memory. Everything a customer needs must be in the description (2048 characters) or in Notion pages the specialist reads at guest time. Build it that way.
- Guests may only do what
guest_accessallows per service:read(lookups),use(lookups and creating new things),all. Guests are refused any call that needs owner approval. - NyxID's published Notion operations cover the whole hub, including
{notion slug}__notion_create_database. The CMA worker builds it with those operations (step 4). If CMA is unavailable, create the databases yourself with the same operation and the schemas in references/notion-hub.md. - Dates and "today" use the business timezone, not UTC.
- NyxID's platform Telnyx offering is AI chat only. SMS uses the owner's own
Telnyx account through
api-telnyx(orapi-telnyx-oauth): their number, their messaging profile and their local sender registration. - One channel bot links to exactly one agent, so all chosen modules share one front-desk specialist. Organization specialists cannot link channel bots; set this up on the owner's personal account.
Steps
- Scope. Confirm the modules, business name, city/country, timezone and the owner's preferred customer language. If the owner arrived from a checklist message, read the modules from it and confirm them.
- Interview. Ask only the questions for the chosen modules
(references/interview.md). As soon as you have the answers (often already in
the owner's first message), and before ending that turn, save them with
nyxid__rememberas 1-3 notes starting "{business} setup:" (each at most 500 characters; policies, contacts and sources only, never customer data). Attaching this skill and every CMA wait can reset your working context, and long owner messages then come back truncated. At hand-over, replace these notes with the hub IDs note. - Connect services (references/services.md). Use
nyx__connect_serviceandnyx__wait_for_connection. Needed: Notion (always), CMA (for setup), Telnyx (queue SMS), Firecrawl (FAQ research, optional). Ask the owner to create an empty Notion page named "NyxBot - {business}" and share it with the NyxID integration during Notion consent. Record the exact connected slugs, e.g.api-notion-3, fromnyxid__list_my_services. - Build the Notion hub with CMA (references/cma-handoff.md, task
notion-hub). Then verify by reading the parent page children and each database's schema yourself. Do not trust the worker's report alone. - Research the FAQ with CMA (faq module, task
faq-research). Meanwhile ask the owner to send the menu as a photo or PDF in this chat; read it yourself and append it to the FAQ Menu section (one line per dish with its price) with the Notion append-blocks operation. When the worker reports, show the owner its "Open questions" list, get answers and append them (source "owner"). Never publish ingredient, allergen, halal, vegan or price claims the owner or an official source did not state. - Create the front desk only after step 4's hub IDs are verified, so the
description carries real IDs (editing it later needs a specialist read that
can fail). Compose its description from
references/front-desk-description.md (stay under 2048 characters; count).
nyxid__spawn_subagentwith namefront-desk(if listing specialists fails, still call spawn; a duplicate name returns an error you can act on), the owner's chosen display name, persona from the owner's tone, and services = the Notion slug,ornn-api(a specialist reads its own attached skill through Ornn; without this grant its skill fails to load withapi_key_scope_forbidden) and the Telnyx slug if queue SMS is on. Then attach the latest version of the Ornn skillnyxid-business-front-desk(GUID a41f05ed-994f-4f26-ab89-a28ad0b24ccc): look it up withnyxid__agent_skill_versions(never reuse a version remembered from an earlier setup), preview it withnyxid__preview_agent_skill, thennyxid__set_agent_skillsforfront-desk. - Permissions (references/go-live.md): guest access, approval settings, SMS mode, optional Full access override, optional confirmation schedule.
- Channel.
nyxid__channel_bot_setup_link(platformtelegram, agentfront-desk). After the owner finishes,nyxid__update_channel_accesswithprivate_chats: everyoneso customers can chat. - Test. Owner smoke test first, read-only: message the front desk "queue" and "pending bookings" (nyxid__message_subagent) and check its answers cite the hub. Do not create test rows in a live hub unless the owner asks; mark any test rows Left or Cancelled with Notes "setup test". Then the customer test in references/go-live.md from a second Telegram account (the owner is never a guest).
- Clean up CMA. Stop the worker, then delete it (deleting a running agent fails). It is not needed for daily operation.
- Hand over. Summarize: bot link, Notion hub link, owner commands ("queue",
"next", "served 12", "pending bookings", "confirm R-4F2A"), what customers can
do, known limits, and how to pause (Disable the bot or set private chats to
owner). Remember the hub IDs with
nyxid__remember, prefixed with the business name so several businesses never mix.
Rules
- Each module is optional; never create databases, grants or schedules for modules the owner did not choose.
- Prefer the narrowest permission that works. Explain each permission card in one plain sentence before it appears.
- If a step fails, say exactly what failed and what the owner can do; do not claim completion. If specialist listing or waiting tools fail, continue: spawning and messaging still work, and specialist reports arrive on their own. Re-running a step must not duplicate databases or specialists: check for existing ones first.
- After an interrupted turn, a restart or a context reset you see a recap in which
long owner messages may be cut short (marked truncated, or with a "…" in the
middle). Before treating any interview answer as missing, read the owner's full
messages with
nyx__conversation_history. Never ask the owner again for, or tell a worker it lacks, something the owner already sent. - NyxID wakes you without an owner message at most 3 times in a row (CMA ready,
CMA finished and specialist reports each count); after that the thread waits for
the owner. So send both CMA tasks in one input, and after
nyxid__message_subagentcallnyxid__wait_for_subagentsin the same turn. Whenever you end a turn expecting a wake-up, tell the owner: "If I haven't updated you in a few minutes, reply 'continue'." Never promise that NyxID will resume you. - Customer data lives only in the owner's Notion. Never put it in skills, memory, descriptions or CMA prompts.