Back to features
Feature deep dive

Contacts CRM

Relationship activity before and beyond the client record

Manage contacts, leads and relationship activity with entity links, tags, notes, events, follow-ups, saved views and CRM context connected to the rest of the workspace.

Ofisync dashboard preview for Contacts CRM
ofisync.app / contacts-crm

CRM pipeline

Follow-up ready

Tagged partner contact
Event scheduled
Notes linked to entity

Live business context

Manage contacts, leads and relationship activity with entity links, tags, notes, events, follow-ups, saved views and CRM context connected to the rest of the workspace.

Tags
Notes
Events

Why it matters

Every relationship keeps its notes, events and entity context.

Contacts CRM in Ofisync gives every important relationship a place to live before it becomes a client, supplier, partner, project contact or other entity connection. Teams can tag contacts, attach notes, schedule events, track follow-ups and connect the relationship to the entities it affects.

Sales teamsPartnership teamsProcurement teamsOperations teams

Give teams one relationship workspace for contacts that do not always start as clients.

Keep notes, events, tags and follow-ups attached to the right person or organization.

Connect CRM activity to the entities that matter, including clients, suppliers, projects and files.

Guided workflow

From setup to daily execution.

1

Create the contact context

Add the contact, classify it with tags and custom fields, then connect it to the relevant entity or relationship category.

2

Record activity

Capture notes, attachments, events, follow-ups and relationship history so the team understands what has happened and what should happen next.

3

Use the CRM view

Filter contacts by tags, saved views, relationship type or linked entity, then use that context for sales, procurement, partnerships or operations.

CRM relationship fit

Built around people, organizations and the entities they touch.

A person may start as a lead, a supplier contact, a partner, a project contact or an internal relationship tied to another entity. The team still needs notes, events, tags, follow-ups and activity history before the relationship becomes operational.

Relationship details get scattered across personal notes, calendars and disconnected spreadsheets.
Teams lose context when a contact is linked to a client, project, file, supplier or another entity but the activity history stays elsewhere.
Follow-ups become unreliable when events, notes and tags are not attached to the contact record.
CRM lists become hard to use when contacts cannot be segmented by tags, relationship type, saved view or linked entity.
User story

How Contacts CRM works in practice.

1

Scenario 1

The contact starts as a relationship, not just a name

A user creates a contact and classifies the relationship. The contact may represent a lead, supplier contact, partner, project contact, internal contact or another person connected to the business.

2

Scenario 2

Entity links place the contact in context

The contact can be associated with entities such as clients, suppliers, projects, files, users or other configured records. This keeps the relationship connected to the business area it affects.

3

Scenario 3

Tags and fields make the CRM list usable

Users can add tags and custom fields to describe the contact. Tags can support grouping by source, priority, campaign, relationship type, department or any structure the team uses.

4

Scenario 4

Notes preserve the conversation trail

A contact can have notes that combine comments and attachments. This lets users capture conversations, decisions, supporting documents and relationship context without scattering that information elsewhere.

5

Scenario 5

Events turn follow-up into scheduled work

Users can associate events with the contact for meetings, reminders, follow-ups or relationship activity. The event gives the CRM record a clear next moment instead of relying on memory.

6

Scenario 6

Saved views help each team work its own list

Sales, procurement, partnerships and operations can create or use saved views so each team sees the contacts that matter to its work.

7

Scenario 7

CRM activity can lead into other modules

When the relationship matures, the contact can connect naturally to clients, projects, files, suppliers, billing or other entities while retaining the earlier CRM activity.

8

Scenario 8

Search and segmentation keep the CRM clean

As contacts grow, users can find and filter records by tags, relationship type, saved view, linked entity and available contact fields.

CRM scenarios

Where relationship context becomes useful fast.

CRM scenario 1

Lead relationship tracking

A sales user can tag a lead, add notes, schedule events and keep follow-up history before the contact becomes a client.

CRM scenario 2

Entity-linked contact history

A contact can be associated with a client, supplier, project, file, user or another entity, keeping relationship activity connected to the right business context.

CRM scenario 3

Tagged CRM segmentation

Teams can use tags, custom fields and saved views to group contacts by campaign, relationship type, priority, source or next action.

Notes can include comments and attachments, so relationship context and supporting files stay together.
Events can be associated with contacts for meetings, follow-ups, reminders and relationship activity.
Contacts can be linked to entities such as clients, suppliers, projects, files, users and other configured records.
Tags, custom fields and saved views help teams segment and work through CRM lists.

Inside the CRM workspace

A relationship view for contacts, activity and follow-up.

The CRM workspace keeps contacts, linked entities, notes, attachments, events, tags, saved views, follow-ups and relationship activity together so teams can understand each relationship without jumping between modules.

Sales

Leads, tags, notes, events, follow-ups and conversion context

Procurement

Supplier contacts, entity links, relationship notes and scheduled follow-ups

Partners

Partner contacts, activity history, tags, events and linked business context

CRM records

What stays attached to each relationship

Contacts, leads, suppliers, partners and relationship people
Linked clients, suppliers, projects, files, users and other entities
Notes with comments, attachments and relationship context
Events, follow-ups, reminders and CRM activity history
Tags, custom fields, saved views, relationship types and source details

Relationship movement

Actions Ofisync can prepare from CRM activity

Surface follow-up notifications when contact events are due
Connect CRM activity to the linked entity when a contact becomes operational
Keep notes, events and tags available when a relationship moves into client or project work
Group contacts through saved views based on tags, fields or linked entities

CRM view

Relationship list

Review contacts by tag, relationship type, linked entity, source, saved view or next follow-up.

CRM view

CRM activity history

Follow notes, attachments, events and relationship activity attached to a contact.

CRM view

Entity connections

See which clients, suppliers, projects, files, users or other records are connected to each contact.

Ready to see it live?

Walk through Contacts CRM with an Ofisync specialist.

We will map the demo around your business workflow, show the connected modules and help you identify the fastest path to rollout.

Request Demo