Guide navigation 5 of 44
What this page helps you accomplish
Maintain a reliable shared view of an organization, people, interactions, and next actions.
Scope and authority
Access to the appropriate authenticated workspace through My Batoi Authority for the records, action, or decision involved
Relationship Management
Maintain a reliable shared view of an organization, people, interactions, and next actions.
Observable business result
Teams can coordinate from one owned relationship context without duplicating unnecessary data.
The same organization or person appears more than once.
Recommended recovery: Stop adding activity, compare the records, use the governed merge workflow where authorized, and preserve the surviving links and history.Who should use this article
This article is for relationship managers who are authorized to complete or review the task in the intended workspace. The person making a consequential operational, commercial, academic, care, access, or compliance decision remains accountable for the result.
Before you begin
- Access to the appropriate authenticated workspace through My Batoi
- Authority for the records, action, or decision involved
- Use a sanitized demonstration record for practice and confirm the intended workspace, role, scope, and responsible owner before changing operational records.
- Do not place passwords, connection secrets, personal data, regulated information, private documents, or payment details in notes, prompts, screenshots, or exports.
Workflow overview
Complete the workflow
- Confirm the workspace and responsibility. Enter the authorized workspace through My Batoi. Confirm the workspace name, your current role, the record or review period, and the person accountable for the result.
- Open the current product area. Open CRM and choose Companies or Contacts. Search before creating a record so the workspace retains one canonical relationship identity.
- Check prerequisites and source records. Make sure the required capability, connection, status, relationship, approval, and safe information boundary are ready. Search before creating a new record.
- Perform the task. Record the minimum useful identity and relationship context, assign an accountable owner, and link authorized opportunities, projects, documents, or communication.
- Review the result. Check duplicate risk, ownership, contact preference, data accuracy, linked work, recent activity, and the next responsible follow-up.
- Verify and retain the outcome. The canonical record is findable, owned, linked to the correct work, and free of unnecessary or duplicate personal information. Record every exception and follow-up with an owner and review date.
Verify the result
- The workspace, role, record, period, and Industry Pack still match the intended scope.
- Teams can coordinate from one owned relationship context without duplicating unnecessary data.
- The visible status, source evidence, owner, exception, and next action agree with the completed work.
- An authorized reviewer can understand the result without relying on hidden assumptions or information outside Flex.
Troubleshooting and recovery
| What you see | What to check | Safe next action |
|---|---|---|
| The same organization or person appears more than once. | Workspace, role, entitlement, source record, status, ownership, required fields, and approval evidence. | Stop adding activity, compare the records, use the governed merge workflow where authorized, and preserve the surviving links and history. |
| The expected page or action is missing. | Current role, team scope, Industry Pack availability, workspace subscription, record state, and prerequisite setup. | Stop and ask an authorized Owner or Admin to review access. Do not use another person’s account or bypass the control. |
| The result conflicts with evidence or another register. | Source ownership, date range, status definitions, duplicate records, latest update, and correction history. | Do not mark the task complete. Return it for correction or escalate it to the accountable owner. |
Safety and governance
Do not copy authenticated page addresses, record identifiers, connection details, browser notifications, account information, or unrelated workspace content into public documentation or external communication.
Use Batoi Intelligence safely
Next step
Continue with the next verified article in this Product Guide, or return to the Batoi Flex Product Guide.