Skip to main content
CRM is CyberOS’s sales pipeline, account intelligence, and Vietnamese-market commercial layer. It is built on three primitives — Account, Contact, and Deal — in a Salesforce-flavoured hierarchy, but with Vietnamese commercial realities baked in as protocol features rather than plugin afterthoughts. MST tax code validation runs automatically against the General Department of Taxation (GDT) registry on every account write. VietQR generates a Napas247 payment code with one tap on any deal. hóa đơn (VAT invoices, stored per Decree 123/2020) are emitted automatically on deal close via INV. The CRM is also the upstream half of the CyberOS orchestration spine: when a deal is won, the Account Manager converts it to a PROJ Engagement with the rate card pre-wired, and the full PROJ → TIME → INV → REW chain begins at that single click.
CRM is a P1 module currently in the design phase. This page describes the planned functionality from the user perspective. Refer to the platform roadmap for GA availability details.

Pipeline management

CRM ships four default pipeline shapes. Each pipeline has fully configurable stages and transition rules.

Sales

The standard B2B sales funnel. Default stages: Qualifying → Discovery → Proposal → Negotiation → Closed Won / Closed Lost.

Partner

For channel and referral partnerships. Stages reflect mutual due-diligence and co-selling motions.

Inbound

For web form and inbound lead flows. Deals are pre-scored by CUO before the Account Manager sees them.

Outbound

For account-based outreach. Stages reflect the prospecting and qualification cadence.
You move deals between stages by dragging and dropping on the pipeline board. Stage transitions are validated by the pipeline rules engine before they are committed — if a transition is not allowed (for example, jumping from Qualifying to Closed Won without passing through Proposal), the system rolls back the card and shows you the reason. Workspace admins can add custom stages, rename defaults, and configure per-pipeline transition rules from CRM → Settings → Pipelines.

Vietnamese-specific features

CyberOS CRM treats Vietnamese commercial requirements as first-class features, not integrations to configure.
Every time you create or update an Account that includes a Vietnamese tax code (MST), CRM automatically validates it against the GDT registry. If the MST matches, the account is marked as validated. If the registry returns a canonical name that differs from what you entered, CRM normalises the account name to the GDT value and shows you a warning.Results are cached for seven days, so validations on existing accounts do not hit the GDT registry on every page load. The cache is invalidated automatically if you update the MST field.
On any open deal, click Generate VietQR to produce a Napas247-compliant QR code pre-filled with your bank, account number, amount, and deal reference. Share the QR in an email, a CHAT message, or on a printed invoice. The QR is cached for 24 hours — regenerate it if the deal amount changes.Your tenant’s bank account allow-list governs which bank BINs are available for QR generation. A Member must confirm the bank account on first use.
When you close a deal as Won, CRM automatically assembles a GDT-compliant XML invoice (template based on the account’s legal entity type). The Account Manager must confirm the amount and recipient before the invoice is emitted — this is a tax document and requires an explicit human confirmation step. On confirmation, the hóa đơn is registered in INV and the XML is stored for 10-year retention per Decree 123/2020.
Contact records include a salutation field pre-populated from gender and age signals: Anh (male, peer or senior), Chị (female, peer or senior), Em (junior), or Bạn (neutral). Salutation is used in AI-drafted emails and any outbound communications CyberOS generates on your behalf.

Activity auto-logging

CRM automatically logs activities from EMAIL, CHAT, and Calendar — you never need to manually enter that you sent an email or attended a meeting.

EMAIL

Inbound and outbound emails to and from tracked domains are auto-logged as CRM activities on the matching Contact and Deal. Only tracked domains trigger auto-logging — personal email addresses are never attached.

CHAT

Meeting notes captured in CHAT threads are auto-logged as meeting activities on the relevant Deal or Contact based on context and participant matching.

Calendar

Calendar attendance is auto-logged as a meeting activity. If the meeting is linked to a Deal through its title or participants, it appears in that Deal’s activity timeline.
Activity auto-logging uses idempotency keys derived from the source event ID. If the same email or calendar event is processed more than once (for example, after a retry), CRM deduplicates it automatically — you will never see duplicate activities on a Deal.

AI features

CUO provides four classes of AI assistance in CRM. All AI suggestions are proposals — CUO never auto-progresses a deal or auto-logs an activity without a human action.
Every new Contact is automatically scored (0–100, tiered as hot / warm / cold) using activity recency, engagement size, account vertical, and historical win-rate signals. Scores refresh nightly. The score is a priority signal for your outreach queue — you decide who to contact first.

Deal → Engagement bridge

When you click Convert to Engagement on a won deal, CRM triggers the deal-to-Engagement conversion:
1

Engagement created

A new PROJ Engagement is created with the deal’s contract URL and client account linked automatically.
2

Rate card pre-wired

The rate card is pre-populated from the deal’s pricing page. You choose the billing mode (T&M, fixed-fee, or retainer) — this choice locks once the Engagement is saved.
3

Billable rules applied

PROJ’s billable cascade rules are wired to the Engagement’s roles. Members can begin logging TIME entries immediately.
4

Deal record archived

The closed deal is recorded as a win/loss entry, where it becomes citable context for future deals with the same account or vertical.
Not every won deal should become a PROJ Engagement. For pure resale deals where you are collecting payment without delivering services, skip the conversion. The conversion dialog requires an explicit Account Manager action — there is no automatic Engagement creation.

Auto vs manual operations