CRM CONTACTS
Know the person behind the customer relationship.
Keep contact details, company affiliation, ownership and the next follow-up together, with the activity that explains how the relationship developed.
- [email protected]
- Phone
- +49 30 5550 1234
- Company
- Studio Nord
A name and an email address are only the beginning
A colleague may know the decision maker while another has the latest conversation. A spreadsheet can hold their names, but it rarely explains what the team agreed or who should act next. Tsumira keeps the person’s contact record alongside their company affiliation, responsible owner and recorded activity. The record becomes the starting point for understanding the relationship, rather than another address book to maintain.
Separate the person from the company
A contact can carry a name, email address, phone number, address, department and job title. The company link gives that person an organizational context without treating a business and its employees as the same record. Name readings support Japanese customer records; they do not replace the original written name. Keep the fields you actually know accurate and use the note for relevant context rather than making assumptions about the customer.
- Person-specific contact details
- Company, department and job title
- Notes and Japanese name readings
Make responsibility and the next step explicit
Assign an owner and record the next-action date with a short explanation. This makes a follow-up understandable to someone who did not take the original call. Ownership and a concrete next step answer different questions: who is responsible, and what should happen next? When the customer changes their preferred contact details or the responsible colleague changes, update the record so the next person starts from the same information.
- Responsible owner
- Next-action date and note
- Editable customer information
Keep the relationship close to its evidence
The detail view brings accessible company information, related deals, recorded activity and change events into the customer context. Internal conversation belongs with the record, so a handover can explain both the facts and the discussion behind them. Access is checked for the person reading the record. Linking a company does not mean every colleague can inspect every related object, and a contact link does not replace a separate file-sharing decision.
- Activity and record change events
- Related visible company and deals
- Per-user access checks
A concrete workflow
Create or locate the person
Search for an existing contact before adding another. Check the name and a reliable identifier such as the email address.
Add the working context
Link the appropriate company and record the department, role and communication details that your team needs.
Agree the next action
Set the responsible owner, follow-up date and a useful note about the commitment made.
Continue from the same record
Record the next interaction and review the history before another colleague contacts the customer.
An illustrative working example
Illustrative workflow: a consulting handover
A consultancy speaks with both a project sponsor and a procurement contact at the same company. Each person has a separate contact record, with their own email and role, linked to the company. After a scope discussion, the consultant records the sponsor’s requested revision and a follow-up date. A colleague covering the next call can read that context and continue the conversation without asking the customer to repeat the brief.
Questions about this topic
Are contacts and companies separate?
Yes. A person’s details belong in a contact record, while the company has its own record. A contact can link to a company and carry department and job-title information.
Can I give someone responsibility for a contact?
The contact has an owner field and next-action information. Assigning responsibility is separate from recording what the team intends to do next.
Can every team member read every contact?
No universal access is assumed. CRM reads apply the current person’s record access and permissions; related records are also checked before their information is shown.
Does a linked contact automatically share a file?
No. Customer associations and file access are separate. A file still needs the appropriate viewing or sharing permission.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
HubSpot
Workflow concept: Review exported contact fields before mapping them into the shared customer record.
Gmail
Workflow concept: Prepare a checked email follow-up using the contact’s confirmed address.
Outlook
Workflow concept: Compare a colleague’s contact details before choosing the authoritative record.