The CRM that fills itself in.

Platform & customization

Model your business. Not someone else's.

Objects, fields, layouts and rules — configured, not coded.

• Objects

  Custom objects, standard rules

  Create an object with its own fields, layout, permissions and icon. Standard objects are defined in exactly the same metadata, so a custom object behaves like a native one everywhere — list views, search, reports, API, AI.

• Fields

  18 field types, real constraints

  Text, currency, percent, date-time, picklist, multi-select, lookup, master-detail, formula, roll-up summary, auto-number and more — with required, unique, external-ID, PII and history-tracked flags.

• Layouts

  Drag-and-drop page layouts

  Build the record page in sections with related lists, and assign it per profile and record type. Translate every label per language. Deleting a field is recoverable for 15 days and shows its dependencies first.

Activities & automatic capture

The CRM fills itself in.

Email, calendar and calls land on the record without anyone typing them up.

• Sync

  Gmail and Microsoft 365

  Connect a mailbox and calendar with OAuth. Emails and meetings with known contacts and leads are captured automatically — with per-user privacy exclusions by domain or label, because not every email belongs to the company.

• Timeline

  One timeline per record

  Tasks, meetings, emails, calls, notes and field changes in a single chronological view on every record — built to carry chat and voice interactions when those channels come online.

• Follow-up

  Nothing falls through

  Tasks with due dates and priorities, reminders, @mentions and real-time in-app notifications. Send email from the CRM using templates with merge fields; replies thread back onto the record.

Omnichannel engagement

Every channel your customers use. One conversation.

Voice, chat, WhatsApp, LINE, Zalo, Messenger, email, SMS and social — normalized into one model.

Phase 2–3 · in build

• Channels

  The apps your region actually uses

  WhatsApp, LINE and Zalo alongside voice, web chat, email, SMS and social — not as add-ons but as the same interaction model, so routing, reporting and AI never special-case a channel.

• Routing

  Skills, capacity and presence

  One routing engine for every channel: queues with business hours and overflow, skills with levels, per-channel capacity weights, and stickiness to the agent the customer spoke to last.

• Console

  One screen for the agent

  Concurrent conversations on the left, the conversation in the middle, the customer's account, cases and history on the right — with suggested replies, knowledge suggestions and an AI wrap-up summary at the end.

Marketing & journeys

Reach people on the channel they answer.

Segments, journeys and consent — built on the same records, not a copy of them.

Phase 3 · in build

• Segments

  Built from live records

  Segments are queries over the CRM itself — no export, no nightly sync, no second definition of “active customer” drifting away from the first.

• Journeys

  Multi-step, multi-channel

  Sequences that send email, WhatsApp template messages or SMS, wait for a response or a record change, branch on it, and create work for a human when a person needs to step in.

• Consent

  Consent as a first-class field

  Communication consent is tracked per contact and per channel and enforced at send time, with the regulatory reality of each region in mind.

Iris · AI throughout

An assistant that can only see what you can see.

It cites its sources, proposes instead of writing, and leaves an audit trail.

• Ask

  A copilot on every page

  Ask about the record in front of you or about your data generally — what happened with this account in the last 90 days, which deals slipped this quarter — and get an answer with the records it used linked underneath.

• Act

  Proposals, not surprises

  Drafted emails, suggested next steps, proposed field updates from a captured meeting — each shown as accept, edit or dismiss. Auto-apply is per action type, admin-enabled, labelled in the timeline and undoable. Deletes and bulk operations are never automatic.

• Govern

  Under the same permission model

  The AI calls the platform as you, so it can never read a record or a field you cannot. PII fields are redacted before a model sees them, restricted fields never leave, and a tenant's requests never route outside its region.