顧客一人あたりの連絡先記録。
すでに実行中のアプリが作成します。予約、注文、またはメッセージが連絡先を作成するため、インポートする必要も、同期させる必要もありません。
顧客向けの Contact App
既存のアプリによって構築された、顧客 1 人あたりの 1 レコード。
0
contact-360 詳細ページにあるタブ
0
システムリスト、ゼロ設定
Zero
照合するためのデータインポート
ビジネスと取引したすべての人。1 つの リスト。
名前、メール、電話番号、会社、タグ、ステージ、最後のチャネル、最後のアクティブ日付。任意の列で検索・フィルタリングし、任意の行を完全なレコードに開くことができます。
New, VIP, Repeat, Customer and Prospect are read off the record itself: its age, its loyalty tier, its order count. Nobody maintains a stage, so no stage goes stale.
Whichever of the three an operator happens to remember is the one they type. Filters narrow on any column beside it.
Of the four counts above the table, this is the size of the audience you cannot reach.
一人のオペレーターで 1 回 のすべてのアプリを管理できます。
1 つの顧客に対する 17 のタブ：概要、アクティビティ、タイムライン、AI 要約、リスト、取引、予約、注文、メッセージ、メール、財務、メンバーシップ、サブスクリプション、ロイヤリティ、ノート、プロパティ、ドキュメント。各タブは、そのデータを所有する事業部門から読み取られるため、ここで表示される内容は、それを生成したアプリと矛盾することはありません。
Every interaction in one column, newest first, with the channel it arrived on. A call, an email and a WhatsApp message are one list because they are one person.
current. を常に最新の状態を保つセグメント。
リストはメンバーシップではなく基準を保存するため、3 回目の注文を行う顧客は、次の読み込みで「リピート顧客」に含まれますが、何もスケジュールされていません。
有用なリストは 何でも を構成する前に用意されています。
Orbit は 8 つの顧客リストが既に埋め込まれた状態で開きます。セットアップウィザード、書くべきルール、保存すべきセグメントはありません。
The eight are reserved and undeletable, and they hold no rows of their own. Each runs its criteria against the live contact set every time it is opened, so a customer who places a third order is in Repeat Customers on the next load, with nothing scheduled and nothing to refresh. At Risk is the one to watch: it needs at least one order and then ninety days of silence, so it lists people who bought and stopped, not people who never started.
条件からリストを作成します。メンバーシップは 現在 状態に維持されます。
フィールド、演算子、値を選択して追加します。グループ内の条件はすべて満たす必要がありますが、グループが満たされれば十分です。保存する前に、一致する連絡先の数を表示するリアルタイムのカウントも提供します。これは、Deals でセグメントを作成するのと同じビルダーであり、同じテーブルに書き込むため、どちらのアプリも互いを学習する必要がありません。
Opening it runs the criteria again. Somebody who qualifies tomorrow is in it tomorrow, and somebody who stops qualifying leaves without anyone removing them.
The right shape when the list is a decision rather than a query. The fifty people invited to an opening stay the fifty people invited to an opening.
againを挿入する翻訳が適切でないため修正が必要
3 番目の注文を置く顧客は次のバッチで「リピート顧客」に分類され、90 日間連絡がない顧客は誰かが操作することなく「再獲得リスト」に自動的に表示されます。
人はその半分を占める。残りの半分は、誰のために働くかである。
コンタクトは企業に属します。企業が リレーションシップ を保持します。
企業レコードはそこで働く人々をグループ化し、業界、ウェブサイト、電話番号、都市を連絡先テーブルの上に配置します。直接作成するか、インポート中の企業カラムから解決させることもできます。
| 名前 | メール | タイトル |
|---|---|---|
| Beatriz Almonte | beatriz@almontelaw.do | Managing Partner |
| Rafael Guzmán | rafael@almontelaw.do | Associate |
| Yesenia Pérez | yesenia@almontelaw.do | Office Manager |
| Hector Núñez | hector@almontelaw.do | Paralegal |
A company has its own list, detail and full create, edit and delete. The contact points at that record rather than repeating a name as free text on everyone who works there.
When one contact leaves and another arrives, the relationship with the company survives the change of person.
Of the three counts on the list, the number of companies that actually have people attached tells you how much of it is real.
リストを取得し、その後重複分を <出力> 取得してください。
Import by uploading a CSV (start from the downloadable template): check the column mapping and preview the rows before anything is saved, and people whose email or phone is already on file are skipped when the duplicate check is on. Merge and Fix clusters duplicates by email, falls back to name when there is none, and tells you why each cluster was grouped before you touch it.
Every tag on every duplicate moves onto the primary. The tag is usually the only record of why somebody filed that contact in the first place.
Any static list holding a duplicate has that id swapped for the primary, deduped. Dynamic and system lists re-evaluate and simply find the survivor.
A real delete, not a flag, confirmed first and stated plainly as something that cannot be undone.
レコードは一つのものです。Orbit の顧客がその横に置くものはこれです。
Orbit のお客様が次に追加するもの。次。
4 of these 8 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.
Bookings
The Bookings tab lists the reservations held by this contact, read from the reservations namespace, and a reservation taken against a person is what puts that person in the directory in the first place.
Deals
The Deals tab lists the open and closed deals attached to this contact, filtered on the same contact id the pipeline card carries.
Orderflow
The Orders tab reads order history from the orders namespace, and the same order count decides whether a contact is a Customer, a Repeat Customer or neither.
Registry
The Memberships tab reads the member records tied to the contact, so a membership taken out in Registry is visible on the contact the moment it exists.
Inbox
The Messages tab lists the conversations held with this contact by reading the shared conversation store the messaging engines write to.
The Email tab reads the email events sent to this contact, each with its subject, its delivery state and when it went out.
Ledger
The Financial tab reads the revenue, payments and outstanding balance carried against the contact, in the currency each record was written in.
Payments
A payment taken against a contact is what moves the financial summary on their record, without a reconciliation step in between.
No setup cost. Pay when you start using.
Contact management for teams that talk to customers.
Included with any Interact communication app
Contacts management system.
Recommended for you
Works well together.
Calisto Bookings
Included with Commerce or Ops
Reservations, inventory, contacts, tickets, and scheduling
Learn more →Calisto Deals
Calisto Orderflow
Calisto Registry
Included with Commerce or Ops
Reservations, inventory, contacts, tickets, and scheduling
Learn more →Calisto Inbox
Calisto Mail
Calisto Ledger
Calisto Payments
Everything included in Calisto Orbit.
- Every contact in the account in one searchable table
- Name, email, phone, company, tags, stage, last channel and last activity
- Search across name, email and phone at once
- Filter on any column, fifty rows to a page
- Four counts above the table: total, new this month, with email, missing email
- Lifecycle stage derived from the record: New, VIP, Repeat, Customer, Prospect
- Last channel normalised to Email, Phone, SMS or Mail
- Create a contact, or import, from the header
- A row opens the contact-360 on its activity tab
- Seventeen curated tabs in one pill-tab chrome
- Activity: what has been logged against the contact, newest first
- Timeline: messages, calls and meetings merged into one chronology
- Summary: the relationship in a paragraph, with the next step
- Lists: every list this contact currently belongs to
- Deals: open and closed deals attached to the contact
- Bookings: reservations held by the contact
- Orders: order history
- Messages: conversations across the messaging channels
- Email: emails sent, with subject, state and date
- Financial: revenue, payments and outstanding balance
- Memberships: active and lapsed memberships
- Subscriptions: plan, status, renewal date and amount
- Loyalty: tier, points and rewards, behind the Circle loyalty flag
- Notes: internal notes with author and date
- Properties: custom fields on the contact
- Documents: files filed against the contact, with type and size
- Eight lists present on the first open, with no configuration
- New Customers: added in the last thirty days
- VIP Customers: gold or platinum loyalty tier
- Repeat Customers: three or more orders
- At Risk: has ordered, then silent for ninety days or more
- Recent Interactions: active in the last seven days
- Birthday This Month: birthday falls in the current month
- No Email: missing an email address
- Unsubscribed: opted out of marketing
- Criteria evaluated on every read, never materialised as rows
- Counted by the database where the criteria allow it
- Tested against the active contact set where they do not
- Reserved and undeletable
- Customer Lists hub: system lists and your own lists in one table
- Member count, type and last update on every list row
- Segment builder with a six-field catalog
- Fields: Name / Email, Stage, Role, Lead Source, Created Date, Last Activity
- Conditions AND within a group, groups OR across
- Live preview count and sample contacts before saving
- Dynamic lists store criteria and re-evaluate on read
- Static lists store contact ids and stay frozen
- Smart Lists: the dynamic segments, listed on their own
- Saved Searches: re-runnable contact searches with their results
- Tags: every tag is a filtered view of the contacts carrying it
- A predicate the contact set cannot express is skipped, never faked
- Company records with their own list, detail and full CRUD
- Profile: name, industry, website, phone and city
- A table of the contacts at that company with email and title
- Three counts: total companies, companies with contacts, active deals
- Companies resolve from the company column during import
- Import your existing contacts
- Column set: name, email, phone, company
- Skip-duplicates-by-email toggle on the import
- Duplicate detection clustered by normalised email
- Fallback clustering by normalised full name when there is no email
- A stated reason on every cluster
- Merge unions the tags of every duplicate onto the primary
- Merge rewrites static list membership onto the primary, deduped
- Merge deletes the duplicate records outright
- Dynamic and system lists need no rewrite because they re-evaluate
- A confirmation that states the merge cannot be undone
- An empty merge screen that says the contacts are clean, not a blank table
- Total contacts, new this month, total lists and total companies
- List performance table with members and growth per list
- Contact settings: custom properties, tags and lifecycle stages
- Default country and default currency for new records
- Notification centre with in-app delivery and an unread count
- Mark-one-read and mark-all-read
- Per-person, per-channel notification preferences
- Live stream for new notifications, plus device token registration
- One contact model, shared with every app that touches a person
- Each contact-360 tab reads the namespace that owns that data
- Orbit owns the lists, notes, properties and tags; the rest are windows
- A tab with nothing for this contact renders empty, with no cached fallback
- No connector, no import job, no staging table, no sync delay
- One identity: every person is a user id inside an account
- Every read and write scoped to the account
- The active business unit scopes contacts, companies and lists
- Lists persist in the same table Deals smart lists use
- Criteria persist as a portable filter tree, not a query string
- No intra-account roles, because Calisto has none
- Bookings (reservations on the contact, and contacts created by a booking)
- Deals (the deals attached to the contact)
- Orderflow (order history, and the order count behind Repeat Customers)
- Desk (tickets raised against the contact)
- Registry (memberships)
- Circle (the loyalty tier behind VIP Customers)
- Inbox (conversation history)
- Mail (email activity and engagement)
- Ledger and Payments (the financial summary)
- Depot (documents filed against the contact)
- Campaigns (lists and segments as the audience)
- Automations (list membership as a condition)
- Identity (the verification level on the record)
- Purview (business unit scope)
Questions about Calisto Orbit
プラットフォーム上のすべてのアプリがその人物について知っていること：予約、注文、取引、通話、メッセージ、支払い、会員資格、ファイル。それは、各システムが断片を保持する 16 のシステムではなく、1 つの記録を 16 通りの方法で読み取るものです。
セグメントはクエリなので、常に最新の状態を保ちます。8 つの顧客リストはクエリ実行時に計算されるため、誰もリフレッシュしなくても、先月見たリストは今日も正確です。
Interact コミュニケーションアプリのいずれかとセットで提供されます。Mail、Inbox、Voice、Live、または Equipo をご使用であれば、Orbit もご使用可能です。
はい、Orbit を満たすものの大半はアプリ自体から届きます。インポートは人々を、オペレーションは履歴を与えてくれます。
Included with any Interact communication app rather than sold separately. The pricing section on this page reads the live catalogue and is the authority.
はい、標準形式で、セグメントとその背後にあるインタラクション履歴も含まれます。
