SyncOnAI360

Pages and Meeting Notes

Salesforce documentation that lives beside the work.

Requirements, runbooks, solution write-ups and meeting notes in one workspace with your orgs and projects, searchable by your team and your AI alike.

Start freeBook a demo

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

In one paragraph

SyncOnAI 360 Pages hold a workspace's notes and documents: requirements, runbooks, solution write-ups and meeting notes. Meetings recorded in the browser are transcribed into pages, any chat answer can be saved as a page, and everything is searchable from the Knowledge Hub and the chat alongside the org itself.

Ways to create a page: new, from chat, from a meeting
3Ways to create a page: new, from chat, from a meeting
Transcription while the call runs
LiveTranscription while the call runs
Search across pages, the org and Salesforce docs
1Search across pages, the org and Salesforce docs
Deleted pages restorable
TrashDeleted pages restorable

01The problem

Why Salesforce documentation is always out of date

Documentation lives in a different tool from the org it describes. Decisions are made in calls and never written down, and the AI on your team cannot read any of it.

  1. 01

    Separate from the org

    Runbooks in a wiki, the org in Salesforce, and nothing connecting them.

  2. 02

    Decisions in calls

    Why a change was made is agreed in a meeting and lost by the next sprint.

  3. 03

    Great answers lost

    A useful explanation in chat is never seen again.

  4. 04

    Invisible to AI

    The assistant answering questions about the org has never read the team's own notes.

02pages

How do you keep Salesforce documentation with the work?

Pages hold notes and documents for the workspace: requirements, runbooks, solution write-ups and anything saved from the chat. Projects also have their own wiki, so project documents sit with the board and the releases.

Create a page with New page, or under any chat answer with Save as page, so a good explanation becomes documentation in one click.

  • Requirements, runbooks and write-ups
  • Project wikis beside the board
  • Save any chat answer as a page

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

03meetings

How do Salesforce meeting notes get captured?

Press the microphone beside New page, pick the browser tab with the call, and its audio is transcribed as you go. When you stop, the transcript is saved as a page, ready to search, summarise or turn into work.

The recorder runs on OpenAI's speech model, so it needs an OpenAI key in the workspace on every plan for now.

  • Record any call in a browser tab
  • Transcribed as you go
  • Saved as a page
  • Needs an OpenAI key for now

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

05files

What happens to files and deleted pages?

Files attached to conversations stay with them, and the document library keeps uploaded and generated documents together. Deleting a page moves it to Trash, where it can be restored or deleted for good.

A page deleted for good cannot be recovered, and the product says so before you do it.

  • Files kept with conversations
  • A document library
  • Restorable trash

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

06handover

How do pages help with Salesforce handover?

A handover usually means a folder of documents nobody reads. With pages beside the org, the runbooks, decisions and meeting transcripts sit with the metadata they describe, and the next team can search them, or ask the chat, from the first day.

Because pages appear as cited sources in chat answers, a question such as why a validation rule exists can be answered from the team's own notes as well as from the org itself.

  • Documents beside the metadata
  • Searchable from day one
  • Answers cite your own notes

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

07transcripts

How are meeting transcripts turned into work?

A transcript saved as a page can be searched, summarised or turned into work like any other page. Ask the chat to pull out the decisions and actions, then save the answer as a new page or use it to plan the next sprint.

Because the recorder runs in the browser and saves straight to the workspace, there is no separate note-taking tool to manage and no export step between the call and the documentation.

  • Decisions and actions from a transcript
  • No separate note-taking tool

Knowledge Hub

Documentation, patterns, your orgs and pages

  • [1] Salesforce documentationFault connectors and error handling in Flows
  • [2] Your orgCase_Intake_Route: 2 elements without a fault path
  • [3] DependenciesEscalate_High_Priority runs after it on save
  • [4] PagesRunbook: Service automation standards

08How it works

From meeting to documentation

Decisions captured where the work happens.

  1. 01

    Record

    Transcribe the call into a page.

  2. 02

    Write

    Add requirements and runbooks, or save chat answers.

  3. 03

    Link

    Keep pages with projects and orgs.

  4. 04

    Find

    Search them from the hub and the chat.

09Before and after

Documentation, scattered versus connected

Without

With SyncOnAI 360

A wiki nobody connects to the org

Pages beside the orgs and projects

Decisions lost after the call

Transcripts saved as pages

Good answers disappear

Save any chat answer as a page

AI that never read your notes

Pages searched and cited by the AI

10Who uses it

Who uses pages

ConsultanciesRecord discovery calls into transcripts, keep requirements beside the client's org and project, and hand over runbooks at the end of an engagement from one place.Salesforce adminsWrite runbooks next to the org they describe and save the chat's best explanations as pages, so the next admin finds the answer instead of asking.Salesforce architectsKeep design decisions and solution write-ups searchable alongside the org, so the AI cites your own standards when it answers a question about the design.
Delivery leadsKeep each project's documents in its wiki beside the board and releases, so decisions made in meetings reach the sprint that implements them.

11Questions

Frequently asked questions

The workspace's notes and documents: requirements, runbooks, solution write-ups, meeting notes and saved chat answers.

Yes. Record a call from a browser tab and the transcript is saved as a page. It needs an OpenAI key in the workspace for now.

Yes. Pages are searchable from the Knowledge Hub and chat, and appear as cited sources in answers.

Yes. Press Save as page under any answer.

They move to Trash, where they can be restored or deleted for good.

Yes. Each project has a wiki for its documents.

No. Pages belong to your workspace and are isolated from every other customer.

Yes. Every plan includes every feature.

Any call that plays in a browser tab: pick the tab when you start, and its audio is transcribed as you go.

12Keep exploring

Related

Knowledge HubDocs, patterns and your org in one searchProjectsDelivery linked to what shippedDeliveryProjects, pages and engagementsAI AgentOrg-aware chat and specialist agentsIn-house Salesforce teamsOne shared org contextPricingEvery feature on every plan

Start in 5 minutes. No card required.

Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.

Start free, connect my orgBook a demo with SyncOnAI
  • Anthropic
  • OpenAI