A compact relationship library.
Keep people, organisations, owners and contact preferences easy to scan, with the selected record’s details and next step close by.
SoraCRM · 고객 관계 앱 예정
연락처, 대화와 영업 기회를 한눈에 보이는 작업 공간에 모으세요.
아래의 상세 디자인 콘셉트는 영어로 제공됩니다.
Planned app in Business & collaboration. All sample people, organisations and values are fictional. No customer account, inbox, mailout, enrichment service, project handoff or finance connection is enabled by this preview.
Scan the compact contact library and open the selected person’s details. Keep shared records and personal contacts distinct, using the same navigation and toolbar patterns as SoraSpace’s other capabilities.
| ID | Name | Organisation | Role | Owner | Contact preference |
|---|---|---|---|---|---|
| C-001 | Alex Example | Example Studio | Client lead | Alex | Service updates only |
| C-002 | Blair Example | Harbour Example Co | Coordinator | Robin | Marketing opted in |
| C-003 | Casey Example | North Example Lab | Research lead | Alex | Service updates only |
| C-004 | Drew Example | Example Studio | Designer | Robin | Marketing opted in |
| C-005 | Ellis Example | Harbour Example Co | Editor | Alex | Not subscribed |
| C-006 | Fran Example | North Example Lab | Project contact | Robin | Not subscribed |
| C-007 | Gray Example | Example Studio | Finance contact | Alex | Service updates only |
| C-008 | Harper Example | Harbour Example Co | Client lead | Robin | Marketing opted in |
| C-009 | Indigo Example | North Example Lab | Coordinator | Alex | Not subscribed |
| C-010 | Jules Example | Example Studio | Reviewer | Robin | Service updates only |
| C-011 | Kai Example | Harbour Example Co | Project contact | Alex | Not subscribed |
| C-012 | Lee Example | North Example Lab | Reviewer | Robin | Not subscribed |
Twelve fictional contacts across three organisations. Personal contacts stay separate unless explicitly shared.
Keep people, organisations, owners and contact preferences easy to scan, with the selected record’s details and next step close by.
Keep a shared contact identity across approved CRM, mail and project workflows. Personal contacts and store-specific customers do not become shared automatically.
Plan configurable stages, owners, values, expected dates and history, with both compact lists and accessible board views. Pipeline estimates are not revenue.
Link authorised notes, meetings, follow-ups and selected messages. Preserve the original record’s access rather than copying entire personal inboxes.
Map fields, validate rows, inspect duplicates and retain consent/provenance. Matching an email address alone must not silently merge records or permissions.
Assign a task with a due date and context. Reminders and automation are later, deliberate choices rather than automatic messages on every import.
Retain consent, suppression and source history. Prepare recipients and content for review before any permitted mail merge or marketing send.
Plan reviewed opportunity-to-project and finance handoffs that retain linked contacts, source decisions and their separate permissions.
Bring relationship, follow-up and opportunity summaries into Business & collaboration, with permitted records, periods and freshness made clear.
Connect authorised people, opportunities and projects without flattening their separate privacy and commercial permissions.
Organisation · Example Studio
| 문의 | Relationship |
|---|---|
| Alex Example | Client lead |
| Drew Example | Designer |
| Gray Example | Finance contact |
| Jules Example | Reviewer |
| Opportunity | Stage | Value · AUD |
|---|---|---|
| Coastal catalogue | Proposal | 1200.00 |
| Exhibition kit | Qualified | 2400.00 |
| Project | Current state |
|---|---|
| Coastal catalogue | In progress |
| Exhibition kit | In progress |
Link authorised records by their identity. Matching names or email addresses alone should not merge customers, organisations or shop accounts.
Commercial values and finance records require the appropriate access; a shared organisation does not expose every linked document.
See the owner, stage, organisation and estimated value. Switch to a board when it helps, with the same records behind the view.
| ID | Opportunity | Organisation | Stage | Estimated value · AUD | Owner |
|---|---|---|---|---|---|
| OP-06 | Field study | North Example Lab | Negotiation | 5000.00 | Robin |
| OP-02 | Archive review | North Example Lab | Qualified | 3600.00 | Robin |
| OP-03 | Exhibition kit | Example Studio | Qualified | 2400.00 | Alex |
| OP-04 | Annual report | Harbour Example Co | Qualified | 1800.00 | Robin |
| OP-01 | Coastal catalogue | Example Studio | Proposal | 1200.00 | Alex |
| OP-05 | Print collection | Harbour Example Co | Proposal | 900.00 | Alex |
North Example Lab · AUD 3,600.00
Example Studio · AUD 2,400.00
Harbour Example Co · AUD 1,800.00
Example Studio · AUD 1,200.00
Harbour Example Co · AUD 900.00
North Example Lab · AUD 5,000.00
Open pipeline: AUD 14,900.00 across six fictional opportunities. Estimates are not issued invoices, confirmed sales or received revenue. No deal is moved by this static board.
Record a note, link the authorised source and choose the next task. Prepare messages deliberately rather than treating every record change as a reason to send one.
Example Studio · Coastal catalogue
Alex recorded the scope discussion. Private workgroup note; no message sent.
Robin linked the brief and next decision. Original document keeps its own permissions.
Qualified contact linked to the organisation and project proposal.
| Due · 2027 | Task | Owner | State |
|---|---|---|---|
| 9 Nov | Review catalogue proposal | Alex | Open |
| 10 Nov | Confirm archive scope | Robin | Open |
Planned SoraMail links should show only authorised messages. Personal inbox contents are not copied into group CRM automatically.
Follow-up reminders, mail merge and marketing need explicit setup, reviewed recipients and appropriate consent/suppression checks.
Review contact preferencePrepare follow-upReview mapping, uncertain matches and consent history before changing contacts. Keep a clear provenance trail and protect records in other shops or workspaces.
Import preview · fictional CSV
| Source column | Destination | Review |
|---|---|---|
| Full name | Contact name | Mapped |
| Company | Organisation match | Review identity |
| Labelled contact address | Validate | |
| Opt-in evidence | Consent source | Review evidence |
| Row | Name | Decision to review |
|---|---|---|
| 1 | Alex Example | Possible duplicate · C-001 |
| 2 | Morgan Sample | New record candidate |
| 3 | Alex Example · shop record | Separate scope · do not auto-merge |
Compare organisation, ownership, consent, notes and source history before updating or merging. An email match alone is not an identity or sharing decision.
Uncertain rows should remain reviewable rather than silently alter existing records. A catalogue or shop customer import does not grant CRM access.
Compare recordsKeep separateReview importPlan useful Business & collaboration widgets without revealing private customer, financial or inbox data through the totals.
Fictional snapshot · 8 November 2027 · authorised commercial view
| Action area | Planned control |
|---|---|
| Contact records | View/edit selected shared records |
| Commercial values | Separately authorised value views |
| Imports & exports | Review scope, provenance and recipients |
| Customer messages | Explicit preparation and send permission |
Accepted opportunities can lead to reviewed project and finance handoffs, retaining linked contacts and the decisions behind them. Those connections still need implementation and acceptance.
Widgets should show permitted records, a clear period or snapshot and freshness information. Hidden customer or financial data must not appear through an aggregate.
Explore SoraProjects →No. Contacts, messages, files, project records and finance data keep their own permissions. Workgroup membership alone is not blanket access.
No. Imports should preserve consent and suppression; sending needs a reviewed audience, prepared content and appropriate permission. No messages are sent from these concepts.
No. Opportunity values are estimates. Issued invoices, payments, refunds and settlement require their own authorised finance records and qualified integrations.
No. SoraCRM remains planned. Contact records, sharing, approved mail connections, import recovery and release checks are still in development.
Choose the tools that fit your work as they become available.
Explore SoraProjects →