150+ typed MCP tools for headless CRM operations—including bookings, loyalty, payments, and WhatsApp/SMS. Features native agent skills via npx skills add favcrm/mcp.
Use when a new user wants to register for FavCRM from inside an MCP client, create a FavCRM workspace, request or verify signup OTP, receive a fav_mcp_* API key, or continue setup after agentic registration.
# FavCRM Agentic Registration
Use this skill when a new user wants to sign up for FavCRM without leaving an MCP client. The real product flow is the no-auth MCP tool pair `register_organisation_request` -> `register_organisation_verify`.
## Operating Rules
- Use MCP tools, not the `favcrm` CLI. No API key exists before registration completes.
- Primary path is `register_organisation_request` followed by `register_organisation_verify`.
- Treat `/v6/dev/signup` and `/v6/dev/verify` as REST sandbox fallback/docs only.
- Never ask the user to paste the API key into a repo, prompt history file, shared config, or source code.
- If the user already has a FavCRM account, tell them to sign in and create an MCP key from portal settings.
## Required Inputs
- `email`: owner email that receives the 6-digit code.
- `organisationName`: business or brand name.
## Optional Inputs
- `industry`: one of `beauty`, `fitness`, `tutoring`, `retail`, `hospitality`, `services`, `other`.
- `country`: ISO 3166-1 alpha-2 country code, such as `HK`, `US`, `GB`.
- `timezone`: IANA timezone, such as `Asia/Hong_Kong`.
## Standard Flow
1. Collect required inputs and optional fields if known.
2. Call `register_organisation_request`.
3. Tell the user to check the masked email for the 6-digit code.
4. When the user provides the code, call `register_organisation_verify` with `requestId` and `code`.
5. Return the `loginUrl`, workspace IDs if useful, and secure key handling guidance.
6. Tell the user to set the API key as the MCP Bearer token or environment variable for future calls.
Read `references/agentic-registration-flow.md` for exact call shapes and failure handling.Use for invoices, payments, products, orders, promotions, subscriptions, overdue follow-up, and commerce operations in FavCRM.
# FavCRM Billing Commerce
Use this skill for invoices, payments, products, orders, promotions, subscriptions, overdue follow-up, payment reminders, and commerce operations.
## Operating Rules
- Ground every invoice, order, subscription, or payment claim with FavCRM data.
- Use `favcrm tool list` and `favcrm tool describe <name>` before unfamiliar billing or commerce tools.
- For plan, quota, permission, or upgrade questions, call `get_plan_status`, `check_plan_operation`, and `list_plan_options` before advising. Only call `create_plan_upgrade_link` after explicit user confirmation.
- Treat refunds, voids, cancellations, payment recording, and subscription changes as sensitive mutations.
- Show count and 3-row preview before bulk billing actions.
- Use the comms approval flow for overdue reminders or payment chase messages.
## Standard Flow
1. Identify the customer, invoice, order, product, promotion, or subscription.
2. Fetch the current record before proposing a change.
3. Preview sensitive mutations and ask for explicit confirmation.
4. For reminders, draft the message and request approval rather than sending directly.
5. Report the resulting status and record IDs after confirmed writes.
Read `references/billing-commerce-flows.md` for concrete CLI patterns.Use for service setup, availability, booking lifecycle, cancellations, no-shows, reminders, and daily booking operations in FavCRM.
# FavCRM Booking Operator
Use this skill when a merchant asks about service setup, calendars, availability, booking creation, booking changes, cancellations, no-shows, reminders, or daily booking operations.
## Operating Rules
- Use FavCRM tools only through the available MCP client or the `favcrm` CLI.
- In FavCRM merchant runtimes, prefer the CLI: `favcrm tool list`, `favcrm tool describe <name>`, then `favcrm tool call <name> '{...}'`.
- Do not guess tool names, IDs, or JSON argument keys. Discover and describe first.
- Before destructive booking changes, show the booking, customer, time, and consequence, then ask for confirmation.
- For customer-facing reminders or replies, use the comms approval flow. Do not send directly.
## Standard Flow
1. Identify the booking/service/customer target using search or list tools.
2. Describe the exact tool before calling any unfamiliar write tool.
3. For availability, list services first, then fetch slots for a bounded date range.
4. For booking creation, verify customer, service, slot, participants, and price before calling create.
5. For cancellation/no-show flows, present the impact and ask for explicit confirmation.
Read `references/booking-flows.md` for concrete CLI patterns.Use for FavCRM dashboards, weekly snapshots, KPI summaries, revenue, bookings, invoices, subscriptions, customer growth, and operational risk reports.
# FavCRM Business Reporting
Use this skill when a merchant asks for a dashboard, weekly summary, KPI snapshot, business review, revenue report, booking funnel, overdue risk, or subscription health.
## Operating Rules
- Ground every metric with FavCRM tools. Do not estimate from memory.
- State date range, timezone, and filters.
- Separate facts from recommendations.
- For exports, show preview first and confirm format/path if a downloadable file is requested.
- Highlight risks: overdue invoices, no-shows, cancellations, past-due subscriptions, inactive VIPs.
## Standard Flow
1. Confirm date range or default to last 7 days.
2. Pull headline dashboard stats.
3. Pull supporting lists for bookings, invoices, subscriptions, and customers as needed.
4. Summarize KPIs, wins, risks, and recommended actions.
5. Keep output scannable: tables for metrics, bullets for actions.
Read `references/reporting-flows.md` for reporting patterns.Use for FavCRM marketing campaigns, customer reactivation, broadcasts, WhatsApp, SMS, email, inbox replies, and approval-gated customer communications.
# FavCRM Comms Approval
Use this skill for marketing campaigns, customer reactivation, win-back messages, promotions, inbox replies, WhatsApp, SMS, email, broadcasts, campaign drafts, campaign validation, reminders, and any customer-facing message.
## Operating Rules
- Never send customer-facing messages directly.
- Always use `request_send_approval` for sends, broadcasts, campaigns, reminders, or replies that leave FavCRM.
- Before approval, show recipient/channel/count, draft content, and reason.
- For bulk sends, show count and a 3-row recipient preview before requesting approval.
- Match the merchant's language and tone. Use Traditional Chinese for zh-HK context.
## Standard Flow
1. Ground the recipient, conversation, campaign, or segment.
2. Draft the message.
3. Validate required fields and channel constraints.
4. Request merchant approval with the exact action type, payload, draft, recipients, and summary.
5. Do not claim delivery until FavCRM reports completion.
Read `references/comms-safety.md` for approval payload patterns.Use for FavCRM blog posts, CMS content blocks, landing-page content, AI-generated images, post publishing, post updates, and content workflows.
# FavCRM Content Publisher
Use this skill when a merchant asks to draft, generate, edit, publish, unpublish, or audit FavCRM CMS/blog content.
## Operating Rules
- Discover exact tool schemas before writes: `favcrm tool describe create_post`, `update_post`, `append_post_block`, and image tools.
- Keep drafts as drafts until the merchant explicitly approves publishing.
- For AI-generated images, confirm prompt direction and model choice when the user cares about style.
- Publishing and deleting content are sensitive. Show title, slug, status change, and public impact before action.
- Do not invent CMS block shape. Use the described schema.
## Standard Flow
1. Clarify title, audience, goal, language, CTA, and publish status.
2. Create or find the post.
3. Build content as structured blocks.
4. Generate or attach media only after confirming direction.
5. Preview summary and ask approval before publishing.
6. Report post ID, slug, status, and next action.
Read `references/content-flows.md` for common workflows.Use for customer search, member profiles, tags, tiers, loyalty, segments, onboarding, retention, and customer 360 summaries in FavCRM.
# FavCRM Customer Lifecycle
Use this skill for customer lookup, member records, tags, membership tiers, loyalty, segments, onboarding, retention, reactivation, and customer 360 summaries.
## Operating Rules
- Ground every factual claim in FavCRM data. Search or get records before answering.
- Use `favcrm tool list` and `favcrm tool describe <name>` when the exact tool or schema is unknown.
- Keep list responses bounded unless the merchant asks for an export.
- Create customer records with `create_account`; use `enrol_membership` when an existing account should become a member.
- For bulk tagging, tier changes, points changes, or reactivation campaigns, show count and a 3-row preview before mutation.
- For customer-facing outreach, draft and request approval. Do not send directly.
## Standard Flow
1. Search customers/members with narrow terms or filters.
2. Fetch the profile before summarizing spend, tier, points, bookings, or order history.
3. Confirm identity before applying tags, tier changes, or loyalty changes.
4. For new customers, call `create_account` once, then call `enrol_membership` only if membership was not handled during creation.
5. For cohorts, build a preview first, then ask for confirmation before bulk actions.
Read `references/customer-flows.md` for concrete CLI patterns.Use for training the FavCRM AI agent with URLs or pasted text, listing knowledge documents, checking ingestion status, and pruning outdated knowledge.
# FavCRM Knowledge Training
Use this skill when a merchant wants the FavCRM AI agent to learn policies, services, FAQs, pricing, scripts, SOPs, or website content.
## Operating Rules
- Confirm source ownership or permission before adding content.
- Prefer URLs for public pages and pasted text for private SOPs.
- Use descriptive document names so retrieval can disambiguate.
- Deleting knowledge is destructive. Confirm document ID/title before deletion.
- Do not claim the agent has learned content until status confirms ready or queued.
## Standard Flow
1. Identify source type: URL or pasted text.
2. Confirm title/name and business purpose.
3. Add or scrape document.
4. List/check documents to confirm status.
5. Report document ID, status, and expected retrieval timing.
Read `references/knowledge-flows.md` for exact patterns.Use for FavCRM deals, pipeline stages, internal tasks, follow-ups, owners, workspace switching, and operational handoffs.
# FavCRM Sales Ops
Use this skill for deal pipeline work, internal tasks, follow-up planning, owner handoffs, and switching workspaces.
## Operating Rules
- Ground deal/task claims with list/get tools before changing anything.
- Confirm stage changes, task reassignment, due-date shifts, and owner changes before writes.
- When a deal becomes won, suggest invoice, onboarding task, or booking follow-up when relevant.
- When a deal is lost, capture loss reason as a note/task if tools support it.
- Use concise tables for pipelines and open task lists.
## Standard Flow
1. Identify the deal, task, owner, or workspace.
2. Fetch current state.
3. Confirm requested change and impact.
4. Apply update.
5. Report new state and recommended next step.
Read `references/sales-ops-flows.md` for concrete patterns.