The intelligence powering PulseOS.
Office knowledge, language models and connected tools, brought into one considered workflow. Follow how an enquiry becomes a draft with supporting sources and a decision your team controls.
ContextBegin with the context that matters.
Begin with the context that matters.
An enquiry belongs to a conversation, a person and an office. Bring those connections into the request, within the accounts and information the user is allowed to access.
Inside this stage
The selected account, conversation history and office guidance shape the request. Knowledge searches carry organisation and user scope.
Search for meaning. Keep the specifics.
Semantic search finds related ideas. Keyword search preserves exact terms. The Pulse Engine combines both to retrieve candidate passages from your office’s knowledge.
Inside this stage
Hybrid retrieval brings semantic and keyword matches into one candidate pool. The passage is the starting point; surrounding document context can come with it.
Give the most relevant evidence more room.
Retrieved content is filtered, deduplicated and reranked against the enquiry. Document-depth selection balances useful detail with a spread of sources where available.
Inside this stage
Relevance ranking, duplicate reduction and document selection shape the context passed to generation. The diagram illustrates ordering, not measured confidence scores.
Write with sources your team can inspect.
Combine selected passages with the conversation and your office’s tone guidance. Prepare an editable draft with citation markers that connect the wording to its supporting material.
Inside this stage
Citations remain available while a draft is saved and reviewed. Your team checks the material, refines the wording and decides whether it is ready.
Thank you for getting in touch.
We can help you identify the appropriate support pathway.
We have included the context from your earlier correspondence.
Available support and referral pathways.
Keep authority with the right person.
Preparation and permission are separate. Shared-account sending requires an authorised approver; personal-account sending belongs to the account owner. Connected external writes require confirmation.
Inside this stage
Tool permissions combine office policy with user settings. A user can make access more restrictive, while approval-required actions retain their confirmation boundary.
Powerful assistance. Accountable decisions.
Clear boundaries, throughout the work.
The engine works within office permissions, with source visibility and approval controls. Your team remains responsible for checking the response and deciding what happens next.